Biggest deal here (for me) is the HTML 5 download attribute. Without that you cannot name or provide an extension for files that are triggered for download.
Safari 10.1
141–150 of 169 posts
Re: Safari 10.1
#142I'm always pleasantly surprised when Apple graces us with Safari updates. They tend to come with fairly cutting edge features when they actually ship. The opportunity they have at the moment is the super long gap between releases, which is even more apparent on iOS. I wish Safari could switch to a more Chrome-like model of shipping smaller updates more frequently, perhaps in an evergreen model. I guess there's only s…
Every WebView in a macOS or iOS app is backed by WebKit—it's not just a browser; it's an extremely important system software component on over a billion devices.
I think Safari Tech Preview and WebKit Nightlies are a good tradeoff—I'd rather that than frequent instability on my Mac or iPhone just for the appearance of being an evergreen browser.
You can see what's being developed and what's being considered for WebKit just like you can for Chrome and Firefox: https://webkit.org/status/
Re: Safari 10.1
#143still no WebRTC?
Re: Safari 10.1
#144I really wish I could have a bookmarks bar with just favicons showing in safari, it's something that's a key part of my workflow in Firefox and I actually really like safari and other than that and the annoying wide tabs thing which I'd probably get used to if use it more often.
Re: Safari 10.1
#145Earlier quoted context omitted.
WebRTC is the main killer for me
https://news.ycombinator.com/item?id=13466306
Re: Safari 10.1
#146Earlier quoted context omitted.
Like that super readable Chrome tab bar when you have lots of tabs open? http://imgur.com/a/MZ2dI
There is no solution to that many tabs. Not getting it right with 5-6 open seems hard even if you try.
https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
Re: Safari 10.1
#147Earlier quoted context omitted.
I don't think it is fair to discount battery life, memory usage, and performance so heavily. Looking at the http://caniuse.com list there are plenty of features supported by Safari and not supported by Chrome including Audio Tracks, Video Tracks, ES6 modules, SVG Fonts, Animated PNG, CSS regions. Safari is actually the first to 100% ES6 compliance; Chrome sits at 89%. I would also remind everyone that Google chose to…
That's only the newest version of Safari, before that it was pretty shit (on par with IE). Can't expect the mind share to change overnight, especially when it has lagged for years.
Safari has always been ahead of Chrome for design & user experience. I'm not sure what the benefits of Chrome are?
Re: Safari 10.1
#148Earlier quoted context omitted.
Does this mean Safari is no longer the new IE? https://news.ycombinator.com/item?id=9804533
Without WebRTC and Service Workers, I'm still holding my breath. http://iswebrtcreadyyet.com/
Re: Safari 10.1
#149Safari is a great browser and I'm sometimes surprised at how huge Chrome's mindshare among developers is. Every time I try Chrome out on my Mac I end up running screaming back to Safari. Safari doesn't choke on tons of tabs, it doesn't eat battery and memory for breakfast, it's never started autoplaying videos when I open a tab in the background, it's got support for picture in picture video which is my most used new…
Also, IMO Safari until recently was very buggy and lagging extremely behind other browsers in features. Not sure if Apple ever got their act together on that.
Re: Safari 10.1
#150Safari is a great browser and I'm sometimes surprised at how huge Chrome's mindshare among developers is. Every time I try Chrome out on my Mac I end up running screaming back to Safari. Safari doesn't choke on tons of tabs, it doesn't eat battery and memory for breakfast, it's never started autoplaying videos when I open a tab in the background, it's got support for picture in picture video which is my most used new…
My main complaint is that tabs are slower to open, switch, and close, all things I do very frequently and while impatient. I'm going to guess that these are largely fixed costs and aren't noticeable on a newer system (mine is from 2011).
The lack of favicons is a big productivity hit when I have many tabs open and need to find specific tabs. But, I haven't yet given "Show all tabs" a good-faith shot, maybe it is a viable alternative.
A smaller productivity hit is that quick search for websites doesn't lock in or provide visual cues, so you need to pause after typing your query to make sure it didn't switch to searching Google.
Performance seems to be generally better than Chrome, but occasionally much worse. I'm not sure if I prefer Safari's better average-case performance or Chrome's better worst-case performance.
I think I would prefer Safari if just the tab performance matched Chrome's.