31–40 of 57 posts
Safari is the new Internet Explorer. That was my experience trying to grapple with its weird, non-standards-compliant implementation of HTML5 required fields.
With the caveat that it's basically only on iOS and OS X.
For anyone wondering why anybody uses Safari these days, the simple answer (for me, at least) is that it consumes much less CPU and energy on my MacBook Pro than Chrome and Firefox. It can mean an hour or more of battery life when unplugged, and greatly reduced testicle-cooking when plugged. I still use Chrome for development but Safari is my "daily driver" for email, surfing, reading, etc.
an even simpler answer would be because it is the default browser..
For anyone wondering why anybody uses Safari these days, the simple answer (for me, at least) is that it consumes much less CPU and energy on my MacBook Pro than Chrome and Firefox. It can mean an hour or more of battery life when unplugged, and greatly reduced testicle-cooking when plugged. I still use Chrome for development but Safari is my "daily driver" for email, surfing, reading, etc.
I'd love a Safari with a Chromium rendering engine, though. Except that Webkit is probably quite important to keep Chrome moving as fast as it does.
Earlier quoted context omitted.
You sound almost happy about the fact we have a new IE6 in our midst.
You sorely misremember IE6.
I also remember many years passing when IE6 stuck around like an unwelcome fart and we all hoped and prayed that it would die so we could move on. Rapid silent updates are the best thing that happened to the web for both the user and for developers. Chrome has many serious issues but it's update cycle isn't one of them.
I guess gesture events on OS X will be quite useful for online maps (openstreetmap, google maps)
Earlier quoted context omitted.
I think it will remain relevant anyway as long as people keep using it.
Or as long as Apple keeps enforcing the "Safari Engine Only" rules on iOS. I think a lot of people would consider switching if Chrome for iOS was legitimate Chrome (rather than a Chrome UI with a Safari engine).
A point release every n months is utterly useless for on-the-ground web developers. Safari needs to move to the Firefox/Chrome deployment model if it wants to remain at all relevant.
Please no. I really love Safari for being just a really good browser. No 'sneaky OS' like Chrome (I don't need Chromes User management, thank you, and I'd much rather have my OS's context menus and font aliasing), and speedier, if you will, 'snappier' than Firefox, with its custom animations for every button and overall not very 'native' look and feel. No, I want a browser that does what a browser should do; let me e…
Except it isn't. Because it's non standard different way of handling things means it's a lot more work for Web developers to give the same experience they give in chrome to safari users. You get a dumbed down experience on safari as a result.
A point release every n months is utterly useless for on-the-ground web developers. Safari needs to move to the Firefox/Chrome deployment model if it wants to remain at all relevant.
Please no. I really love Safari for being just a really good browser. No 'sneaky OS' like Chrome (I don't need Chromes User management, thank you, and I'd much rather have my OS's context menus and font aliasing), and speedier, if you will, 'snappier' than Firefox, with its custom animations for every button and overall not very 'native' look and feel. No, I want a browser that does what a browser should do; let me e…
https://developer.apple.com/library/mac/releasenotes/General...
CSS variables are a great way to do theming and cross-scoped styling for Custom Elements and shadow DOM. Polymer's had a shim for this for a while, but native support is much faster and more flexible.