4 ms·
I mostly agree regarding Intel... A lot of this is all pretty shady, I will make one exception to your comment about MS eating IE's costs. When MS started incl
by tracker1 12y ago
I mostly agree regarding Intel... A lot of this is all pretty shady, I will make one exception to your comment about MS eating IE's costs.
When MS started including IE with windows, every other graphical OS included a browser (OS/2 Warp, and early Linux distros). I think the irritation was how deeply they embedded the browser, which does make some sense as it allowed them to create the CHM help files, which is a pretty nice format. As well as some of the push desktop stuff early one, which I kind of liked. The down side is that support for newer browsers on older OS versions was effectively made into a cliff for IE.
I'm glad that Chrome and Firefox carry as much weight as they do. Seeing a roughly 1:1:1 split among the top three is best for the larger community. The down side being how long it takes for an IE version to ship (still), which means that IE while ahead at launch quickly falls behind and becomes our least common denominator for public websites for years.
In particular, while I don't mind using JS transpilers like Babel/6to5 to get new features today, the fact that I can't use these without such tools for the next 4-5 years is kind of sad. As an aside, I really wish there was a common background worker abstraction that worked in both node and the browser... I know I can fork/cluster in node and use webworkers where available, it would still be nice to see a common interface for this stuff.