News for hackers. Stuff that matters.
Re:Safari no longer supported by Spotify by mschuster91 on Sunday September 17, 2017 @10:11AM (#15269672)
position:relative and percentage values in top combined, for example, are broken - and the devtools are massively behind Chrome. Not to mention the UX that it does not show you the full URL in the address bar.

Guess the only thing keeping people on Safari is that it is deeply integrated into OS X and has battery life advantages over Chrome/FF.

Re:Safari no longer supported by Spotify by fauigerzigerk on Sunday September 17, 2017 @10:17AM (#15269690)
What keeps me on Safari is that it is by far the most resource efficient browser. It keeps CPU and memory usage way way below all other browsers available on the Mac.

In a couple of days Safari will start blocking autoplay videos, which is yet another reason for me to use it as my main browser.

Re:Safari no longer supported by Spotify by RubberSoul on Sunday September 17, 2017 @10:25AM (#15269733)
Showing the full URL is a checkbox away in the preferences. It's listed under "Advanced" as "Show full website address".
Re:Safari no longer supported by Spotify by laveur on Sunday September 17, 2017 @11:14AM (#15269976)
Thanks I didn't even realize I could change this. And I would add that most people outside of developers (of any kind) probably don't care.
Re:Safari no longer supported by Spotify by mschuster91 on Sunday September 17, 2017 @01:01PM (#15270526)
> And I would add that most people outside of developers (of any kind) probably don't care.

Showing the full URL can save you from phishing attempts, though - when you see cryptic crap, <script> or similar stuff in a page URL, you know something is fishy.

Re:Safari no longer supported by Spotify by kitsunesoba on Sunday September 17, 2017 @01:27PM (#15270677)
For me, Safari's engine level blocking is huge. Safari ad blockers aren't just a mile long list of CSS rules (which can bog things down as much or more than add), they're JSON rule files that are compiled to byte code via LLVM and then applied to the list of resources that are allowed to be loaded BEFORE the page has loaded. Result: blocked elements aren't even requested and blocking has a near-zero performance impact. These extensions, being nothing but JSON, also can't track anyone or do anything malicious, giving you a 100% guarantee that it can't be highjacked and updated to do something malicious.

Aside from that, Apple's design decisions tend towards giving the user more control over their experience while Google seems mostly interested in wooing developers, regardless of cost (who cares about resource consumption or what the user wants?). Apple's approach aligns with me better.

Re:Safari no longer supported by Spotify by mschuster91 on Sunday September 17, 2017 @01:59PM (#15270825)
> Aside from that, Apple's design decisions tend towards giving the user more control over their experience

What? Users in control at Apple? No. Apple tries to keep users out of control and inside their walled garden. Only reason I have a Mac is because even with Chrome its battery life is way better than any Windows laptop I ever had, and because it offers a proper Unix shell with actual Unix behavior (e.g. select stuff with the mouse and it ends up in clipboard).

Re:Safari no longer supported by Spotify by coldtea on Sunday September 17, 2017 @12:12PM (#15270278)
>Not to mention the UX that it does not show you the full URL in the address bar

That's something that Chrome has been experimenting with in beta versions on and off for ages, and will use by default at some point.