2 ms·

Two highly correlated reasons. 1) It speeds up the pace of innovation and change as these companies can now receive rapid feedback and see what works and what d

by twunde 10y ago

Two highly correlated reasons. 1) It speeds up the pace of innovation and change as these companies can now receive rapid feedback and see what works and what doesn't. 2) It heavily reduces the maintenance requirements as Apple is only supporting a relatively small number of platforms. By reducing the number of platforms supported, the companies can then reallocate those resources that would have been doing bug fixes on adding brand new features to the latest version. These all allow the marketing arms of these companies to crow about the new features they've added. Think about it this way. Chrome's major innovation was being the first browser to rapidly update itself. That allowed it to quickly leapfrog over IE and Mozilla since they could push out many more changes over the same period of time AND those changes would be more likely to be stable. It also eliminated the need to support old versions like IE 6 with security fixes

pfranz 10y ago
Unfortunately, that's not always good for the user. There are things I do like once a year; update my drivers license online, for example. If the web site is "good enough" and never updated, then great, I know how long it will take and what steps to take--I may even have automated most of it. If they change the website every 6 months with wiz-bang features I have to relearn it, I have no idea how long it'll take, and it may not even work. A web service is kind of a bad example since it require managing a backend. To my parents, opening a spreadsheet or listening to music is the same. They lack the lexicon to discover newer interface trends like the hamburger icon, or ribbon interface. Many people used IE6 because there was a huge investment in it. I agree it was terrible to support and write against, but I don't see any problem with using a payroll system that was written 10 years ago and dependant on IE6 if your needs haven't changed. It seems silly to constantly update or completely rewrite something that's working just fine if needs haven't changed. It just sucks that they would use the same browser for payroll as they do for browsing the Internet.
flukus 10y ago
> 1) It speeds up the pace of innovation and change as these companies can now receive rapid feedback and see what works and what doesn't. This is exactly the sort of thing most users don't want.

by twunde 10y ago

pfranz 10y ago

Unfortunately, that's not always good for the user. There are things I do like once a year; update my drivers license online, for example. If the web site is "good enough" and never updated, then great, I know how long it will take and what steps to take--I may even have automated most of it. If they change the website every 6 months with wiz-bang features I have to relearn it, I have no idea how long it'll take, and it may not even work. A web service is kind of a bad example since it require managing a backend. To my parents, opening a spreadsheet or listening to music is the same. They lack the lexicon to discover newer interface trends like the hamburger icon, or ribbon interface. Many people used IE6 because there was a huge investment in it. I agree it was terrible to support and write against, but I don't see any problem with using a payroll system that was written 10 years ago and dependant on IE6 if your needs haven't changed. It seems silly to constantly update or completely rewrite something that's working just fine if needs haven't changed. It just sucks that they would use the same browser for payroll as they do for browsing the Internet.

flukus 10y ago

> 1) It speeds up the pace of innovation and change as these companies can now receive rapid feedback and see what works and what doesn't. This is exactly the sort of thing most users don't want.