News for hackers. Stuff that matters.
Re:Microsoft does away with stack ranking by Pxtl on Tuesday November 12, 2013 @03:10PM (#6720595)
From the outside as a developer, you can feel the effect of such a drama-driven system as Stack Rank. MS's obsession with perfect backwards compatibility means they can't make mistakes, because those mistakes are forever.

So why embrace a process that seems to celebrate daring? A move-fast-and-break-things approach to projects? You'd think MS would be an analysis-paralysis company, because every MS product needs to integrate with hundreds of other MS products and be supported on oodles of platforms for like a decade.

But instead? We see this crazy wasteful churn of APIs and packages and MSDN Magazine-driven fashions.

I mean, how long will MS be stuck supporting Silverlight? Or Linq2SQL? Or ClickOnce installers? Or the zillion different SKUs of SQL Server and Access?

Re:Microsoft does away with stack ranking by bskap on Tuesday November 12, 2013 @05:25PM (#6721741)
From an inside perspective, stack ranking was actually hurting backwards compatibility. "I made this cool new feature" gets you a lot more recognition come review time than "I made sure that Sim City kept working in the new version of Windows". That's why no one really takes the time to fix things like the console host, preferring instead to write the fancy new PowerShell ISE.
Re:Microsoft does away with stack ranking by Pxtl on Wednesday November 13, 2013 @12:05AM (#6723465)
Still, it felt like BC was always a priority at MS, even if things often slipped by... it just felt like they were trying to maintain backwards compatibility on so many APIs and products in cases where things really did need breaking fixes. But instead of breaking fixes, we get a Whole New Product that is totally better than the old one, but has its own learning curve and its own problems and none of those will get fixed either.

Also, the new powershell ISE is slick (reminds me of Python), but at the same time the near-total lack of integration between Powershell and Visual Studio is pretty surprising. I generally find Powershell a bit disappointing... it feels kind of messy next to C# or Python or plain command-line. I'd probably rather just have a C# REPL with good intellisense. I'm sure one exists.