One could argue that the browser has matured to a point where, technically, they slowed down the innovation of Safari on all platforms. If you look at the amount of features introduced in every new version of the last few years, it is less. iOS7 Safari is a notable exception but Safari has not kept up with innovation that they once had.
prefixing CSS standards which aren't actually finished is exactly what prefixing is for.
Pedantic is Apple purposely lagging behind over said unfinished standards when the rest of the industry has moved on. Vendor prefixes are tedious for web developers to keep up with and tools such as Autoprefixer were forced to be developed b/c of them. Webkit has been unprefixed for ~6 months now and Safari and iOS have both seen updates since then without this change. This should be unacceptable and if there are still reasons to include it Apple needs to be way more transparent.
I'm not anti-Apple by any means, sitting here writing this on my MacBook Pro, but pressure on Apple to get their act together is absolutely warranted and needed to promote standards based design and development which will make a better User Experience for all.
Apple's finite is larger than every other company out there (to quote an article from earlier this week). I'm pretty sure that any issues Safari is encountering is not due to Apple reaching a "finite" limit of any kind.
EDIT: Many of your responses posit Apple as some kind of underdog, struggling to make it in this industry. Given Apple's size and talent, this viewpoint is all but indefensible.
If having an industry leading browser it was a priority for Apple, it would get done. That it's not getting done indicates either that the developers are incompetent, or that the developers' efforts are genuine but being sabotaged due to politics. I'm inclined to believe the latter.
This is demonstrated by making certain features of application development on their devices only accessible by writing native software.
The simple workaround would be to write your own browser and put it on their platform. That is expressly verboten or else I'd already be using an iPhone running Firefox, instead I use and android that runs firefox and which has extensions since it's what it's users want vs what the payers of the browsers developers salaries want.
So the strategy MS used to buy years of revenue for win+office was to bundle a default browser to control the web platform and strategically hinder it whenever it threatened their core income centers. The default opt-out required momentum plus the fact that netscape did themselves no favors led to a dark age of web platform innovation as MS corruptly controlled the space and acted as negligent stewards.
What is totally insane to me is that a large portion of the Microsoft anti-trust trial revolved around them simply providing a default browser, it is hard to imagine even they would have blocked netscape software from running on their platform outright.
And yet here we are 15 years later and the iOS platform is doing just that, Apple is embracing this Microsoft strategy and extending it to a whole new level by flat out banning 3rd party browsers and so we all run the risk of having this great renaissance in browser application innovation extinguished into a second dark age.
Well, this is expected from a business perspective. Apple can't profit from the web as much as they do from the App Store, the only way to "convince Apple" is either by dropping their sales, or by regulation.
While they have money, their pay scale isn't famous for being extravagant. People work there mostly for prestige, but you can get money and prestige working for a startup.
Cook has said publicly that their biggest challenge is talent retention. They're obviously short-handed on OS releases, and willing to reallocate when necessary. So it is not surprising to me at all (but deeply disappointing) that Safari improvements would take a backseat.
Need more developers? Hire more.
Payscale problems? Pay your developers what they are worth to you. Of course, if they aren't worth much to you, then this point is moot.
Retention problems? Addressed by both points one and two.
That they do not use their resources to solve these problems says more than the fact that they have these problems.
They're aiming to increase their total number of Cupertino employees from 16k to over 24k in 2016. For any organisation, absorbing another 7k+ employess is no mean feat.
Apple is experiencing unprecedented success and fantastic growth. But sure, that's trivial to manage. You could do it in your sleep. Maybe you should drop Tim Cook an email.
How do you even find 8000 people who would want to live in Cupertino… I mean have you even visited that place?
No reason to get emotional.
> That's a really pedantic objection —
Pedantic? Positioning elements is the most important feature of a layout system and CSS is totally broken in this regards, just try to vertical center something. Flexbox is godsend and finalized—every vendor removed the prefix. Wondering who is pedantic.
> Apple could easily just not have released WKWebView
The pressure they got for five years that they offer just the 10x slower UIWebview and give Safari the WKWebkit was the main reason and maybe they just released WKWebview to make the impression that they play along. This one bug makes WKWebview utterly useless.
However, would love to keep the tone in this discussion on a friendly level.
> No reason to get emotional.
No reason to project tone onto text that made a simple statement.
The reason why many browsers rush to unprefix CSS3 is not that it's perfect, but because of the lazy web developers who only prefix stuff for WebKit. This may or may not bite the community in the future.
People only initially prefixed for Webkit because webkit was the only browser that had a lot of these properties. The problem was that nobody went back and updated their prefixes, which really only further illustrates one of the big problems with the whole idea of vendor prefixes.
But not with divs which are more common
Flexbox is awesome and has been available to use in Safari for years. Prefixing is not an impediment to the adoption of web standards.
This one bug makes WKWebview utterly useless.
No it doesn't – it does harm PhoneGap/Cordova or whatever, but there are known workarounds, and this bug is likely to be fixed soon in any case (see http://trac.webkit.org/changeset/174029/trunk for the actual commit that adds the required support)
No, it's not at all obvious, and the objections you've raised do not support your view at all.
CSS Flexbox is the best positioning standard I encountered, every vendor supports it, only Apple still prefixes it with -webkit
That's a really pedantic objection — prefixing CSS standards which aren't actually finished is exactly what prefixing is for. It's hardly an anti-web move to keep it prefixed, and anybody who wants to use it can already do so with minimal additional effort.
Another example is their reluctance to make WKWebview fully workable
I find that argument very suspect, since Apple could easily just not have released WKWebView in the first place if they wanted to prevent it's use.