Re:The Controversial State of JavaScript Tooling
by ethbro on Tuesday February 02, 2016 @11:15PM
(#11024700)
I think that's an interesting observation about Microsoft re: the period where they had an enterprise OS (NT) and a consumer OS (3.1x/9x). I think those two tensions and philosophies came through clearly.
Re:The Controversial State of JavaScript Tooling
by soft_dev_person on Wednesday February 03, 2016 @03:27AM
(#11025392)
It's a bit ironic to praise Microsoft for stability in this context, when they probably have had a major role of causing instability in the web front-end world for more than a decade.
Re:The Controversial State of JavaScript Tooling
by chc on Wednesday February 03, 2016 @04:31AM
(#11025572)
I thought most people's complaint was that Microsoft caused stagnation, not instability. Explorer was too stable for most developers' tastes.
Re:The Controversial State of JavaScript Tooling
by d215 on Wednesday February 03, 2016 @05:36AM
(#11025764)
Most people's complaint was Microsoft was trying to push their own proprietary standards (Activex anyone?) upon the www at large. Also their adherence to Web standards at the time IE6 came out was so bad, that it caused almost unsurmountable instability.
It's interesting to compare the dominance of Microsoft in the enterprise world where IT runs the show was established largely due to stability. IT is run by managers who can get fired if instability costs the company money.
In the front-end world managers can't keep up with the changing landscape and therefore cannot make stability based decisions (in terms of software stability). Instead, in my experience, they make decisions based on how easy it is to hire (as cheap as possible) developers.
So, as a proxy, popularity drives the front-end because developers who have the time to keep up with the latest trends (IE mostly young 20-somethings) because they're the ones who get hired.