Can I use lists Safari as not supporting WebRTC. I thought that was part of the spec. http://caniuse.com/#search=webrtc
Not the ES spec; one is JavaScript the language, the other (WebRTC) is part of the browser ecosystem.
Safari Technology Preview supports 100% of the ES2015/16/17 features
31–40 of 126 posts
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#32Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.
Chrome looks really ugly, like it was designed by a programmer.
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#33Earlier quoted context omitted.
Im guessing for a large number, its the same reason people still use Microsoft's browser. It's the default and it's good enough.
You're guessing wrong. I am using Safari because I like Safari the most.
I didn't say every Safari user, how does your comment prove my comment wrong?
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#34At the same time, right now it's relly backwards[1]. Luckily the shelf-life of Safari is much shorter than others, so we'll be able to use fetch() natively without polyfills soon-ish if you target modern browsers. [1] http://caniuse.com/#feat=fetch
This is the important list. I don't care about ES2015 or more—we'll always use Babel. I care about Service Workers and WebRTC more.
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#35Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.
I used Chrome before but gave Safari another go about a year and a half ago, haven't looked back since and now Safari is my main browser on macOS. I only open Chrome when I need to test something, or come across a site that puts up a screen saying nothing but Chrome is supported (regardless of whether or not it works.)
My main reason for switching is efficiency. Safari is blazing fast, and reasonably memory efficient as far as browsers go even with 100+ tabs. Chrome would deplete my memory even with only a moderate amount of tabs open.
Also Safari seems much more power efficient.
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#36Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.
Nicer looking, faster (feeling, at least), iCloud Keychain.
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#37Now add WebRTC and it will be fine :)
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#38If only it supported WebRTC like even Edge does. I'm running a WebRTC startup and its killing me that Safari and Mobile Safari don't support it at all.
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#39Post like these bother me because they lack context. Sure, the claim in the title is true, (and will remain true, unless something goes terribly wrong at Apple) but by the very nature of the linked resource, at some point it won't tell you whether or not the claim is valid.
Re: Safari Technology Preview supports 100% of the ES2015/16/17 features
#40At the same time, right now it's relly backwards[1]. Luckily the shelf-life of Safari is much shorter than others, so we'll be able to use fetch() natively without polyfills soon-ish if you target modern browsers. [1] http://caniuse.com/#feat=fetch
This is the important list. I don't care about ES2015 or more—we'll always use Babel. I care about Service Workers and WebRTC more.
Even if you use Babel your users will still benefit from less polyfill.