Re:Anders Hejlsberg – What brought about the birth of the CL...
by shawnb576 on Sunday May 03, 2015 @05:31PM
(#9483158)
The idea was that a converged, single, multi-language runtime and framework was the way to go. This is the way the culture works in Redmond - that's considered "strategic thinking", which is only exists in that bubble. It wasn't that the plan was bad, it's that it was unrealistic to think that the users of a very mature, very scenario-focused product would be happy with a V1 generalized product that was sorta-kinda the same thing. This was obviously false, and I actually fought against the porting tool because I didn't think it would work (it didn't), and just piss people off (it did). To keep VB6 alive until VB.net matured is anthetical to the way the place runs. Newer is _always_ better, even if it's not, and there lacked any incentive in the comp system for people to take care of the existing userbase. So, that's what happened.
[ Parent
| on HN ]
Re:Anders Hejlsberg – What brought about the birth of the CL...
by pron on Monday May 04, 2015 @03:13AM
(#9484746)
> there lacked any incentive in the comp system for people to take care of the existing userbase
Can you explain that? Are there incentives to do other stuff?
Re:Anders Hejlsberg – What brought about the birth of the CL...
by shawnb576 on Monday May 04, 2015 @06:23PM
(#9489637)
The basic system - no. As of 2012 when I left, comp was about what your management was interested in. Maybe "take care of existing users" is on your review commitments, but what's really on there if you want to get ahead is: ship features, drive future business, etc. As such people wanted to work on the next new thing, it was relatively bad for careers to be on existing old things. Massive variations between groups, but basically that was the culture.