3 ms·
chrome, the IE6 of today! sacarms aside, nobody realize the similarity? defining standards by releasing first? all the cool prototypes at my company are done i
by gcb0 13y ago
chrome, the IE6 of today!
sacarms aside, nobody realize the similarity? defining standards by releasing first? all the cool prototypes at my company are done in chrome and only tested in chrome, before they become internal tools... which will require chrome 32 from 5 years on sice they will probably move to some other prototype while someone in the sales team base his team workflow on that tool...
the pattern is almost the same.
- hayksaakian 13y agothe nice thing is that chrome auto updates, so most of the version specific chrome "things" either break fast or are not version specific. the other nice thing is that chromium is open source, so if they do something truly novel, there is a publicly visible source repo.
- gcb0 13y agountil it updates to something that break that prototype that is now used by the sales team. Do you really think IE6 is here because people don't want to upgrade to IE7,8,9,10? It is there because the lame code fail on anything but IE6. Just like 10yrs from now several applications will fail on anything but chrome32 or something.
- nathancahill 13y agoI had the same thought, but a different conclusion. In my opinion, it's Chrome vs other browsers instead of Chrome 32 vs Chrome xx. A lot of cutting edge apps rely on interesting features of Chrome... features that other browsers may or may not implement. Sometimes it's not even browser features, it's the Javascript engine speed (although the last couple versions of Firefox have hugely improved in that regard).
- gcb0 13y ago> rely on interesting features of Chrome... features that other browsers may or may not implement or chrome 36 may implement differently.
- hrktb 13y agoIt's balanced by prototypes running only on iOS devices. At least there's no monopoly on frustration!