Tired of Safari
41–50 of 125 posts
Re: Tired of Safari
#42Earlier quoted context omitted.
As that comment pointed out, once Apple decides that your device is "obsolete", it stops getting updates, so there are plenty of still-used iOS devices that will never have their Webkit versions updated. Personally, I suspect this lack of updates has less to do with actual obsoleteness and more to do with ensuring that you always buy the latest device. (Note that this isn't a problem unique to Apple -- many companies…
This can be turned around and say that it is actually the progress of the web which is obsoleting the devices. Device manufacturers can not update the devices forever, although they could keep them updated a while longer.
Re: Tired of Safari
#43It has good battery life on a Mac, but tends to crash frequently for me.
The thing I hate the most though is this: On the favorites bar, click a folder to drop it down, now click another folder while the first is still dropped down -- nothing! I'm not even asking to be able to drag my pointer to the next folder and have it expand, but that would be even better.
Re: Tired of Safari
#44Earlier quoted context omitted.
It's obvious that Apple slowed down innovating the web since the core of their business is iOS and apps 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 i…
> ... the objections you've raised do not support your view at all. 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…
Re: Tired of Safari
#45 If you want to help, please star _this_ issue in the Chromium bug tracker and make some noise
* https://code.google.com/p/chromium/issues/detail?id=162757Re: Tired of Safari
#46Earlier quoted context omitted.
It's obvious that Apple slowed down innovating the web since the core of their business is iOS and apps 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 i…
> ... the objections you've raised do not support your view at all. 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…
> No reason to get emotional.
No reason to project tone onto text that made a simple statement.
Re: Tired of Safari
#47It's obvious that Apple slowed down innovating the web since the core of their business is iOS and apps. They shouldn't have any interest in a fast innovating web that gets on par with native apps which is their main lock-in for iOS, just like Microsoft 15 years ago. They only speed up their rendering engine and JS core but don't try to help on standards improving the web experience. BUT: I doubt this pointer event t…
>CSS Flexbox is the best positioning standard I encountered, every vendor supports it, only Apple still prefixes it with -webkit. Flexbox has been unprefixed in WebKit r173579[1][2]. Presumably, it will be available when Apple release the next version of Safari. Reading the Bugzilla, the reason of not unprefixing the feature seems to be lack of contributors on WebKit's part than anything. [1]: http://trac.webkit.org/…
How do you know? It's was unprefixed already ~3 months ago, so why should it happen with the next release? And when does the next release come? And why do their release cycles are not as short as those from Chrome or Firefox?
Because it's not their core business.
> ... to be lack of contributors on WebKit's part than anything.
Exactly what I wrote: Apple is focussing on other stuff than the web because—again—it's not their core business. They have two browsers, mobile Safari and desktop Safari and none of them got this important upgrade yet. A fast innovating web isn't in Apple's favor.
Re: Tired of Safari
#48Another example: they ignored IndexedDB for a couple years after every other major browser implemented it. Then they finally got around to releasing a version of Safari with IndexedDB support... and it's just hilariously broken in so many ways http://www.raymondcamden.com/2014/09/25/IndexedDB-on-iOS-8-B... I literally cannot fathom how such a horribly buggy release could be made in good faith. It's like nobody even t…
It came late and it was buggy. That rarely means malice. That usually means overstretched engineers.
There are plenty of pre-written tests used by the other browser vendors that would have shown them it's shit before they released it. Or they could have just tried using some websites that use IndexedDB and noticed that basically all of them broke in their browser.
That means malice, horrible incompetence, or horrible management. I doubt it's incompetence. It could be horrible management. But it's just so bad that you can't help but think about malice...
Re: Tired of Safari
#49Meanwhile Chrome and IE still don't support MathML. Now that is annoying.
Recently I wrote a small tool that enables me to write LaTeX code directly in HTML and the tool then renders the LaTeX code in PDF, converts it to SVG and places an appropriate img-tag with the reference to the generated SVG. I was under the assumption that most people do it kind of that way.
Or let me ask another way: Is there a reason to prefer MathML over using SVGs created with the LaTeX rendering engine?
Re: Tired of Safari
#50It's obvious that Apple slowed down innovating the web since the core of their business is iOS and apps. They shouldn't have any interest in a fast innovating web that gets on par with native apps which is their main lock-in for iOS, just like Microsoft 15 years ago. They only speed up their rendering engine and JS core but don't try to help on standards improving the web experience. BUT: I doubt this pointer event t…