3 ms·
this is bad. remember when Microsoft was the first to ship a browser shipped by default and dictated the standards by releasing it as they saw fit in that mono
by gcb0 11y ago
this is bad.
remember when Microsoft was the first to ship a browser shipped by default and dictated the standards by releasing it as they saw fit in that monopolistic browser? (for the kids of today, devs from that day loved ie just like you love chrome today. IE invented the developer panel and ajax request, both things you live by today)
well, Google (the irony) sued and won. Microsoft had to remove IE from Windows, and browser vendors agreed to not force standards themselves. that is the only reason we have prefixes. it send the message "we think it's cool, but wait for everyone to agree on the best way to implement this".
without prefixes, Google, having the browser monopoly (since Android is the new windows) can dictate the direction as it see fits. just like Microsoft when they sued them.
- miketaylr 11y ago...what. I don't think you understand how prefixes are used in the wild. Vendor prefixes re-inforce monoculture, they don't prevent it.
- cpeterso 11y agoThe modern "no prefixes" approach is to hide the new features behind a runtime flag or in a pre-release beta channel. Web developers can test the feature but not use it in production websites until browser vendors standardize it.
- magicalist 11y ago> well, Google (the irony) sued and won. Microsoft had to remove IE from Windows, and browser vendors agreed to not force standards themselves. What on earth are you talking about? This is not a thing that ever happened.
- gcb0 11y agoare you too young to remember the browser wars and how Google sued ms for giving internet explorer for free with msn as the honepage?