Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Safari Technology Preview supports 100% of the ES2015/16/17 features

kangax.github.io

Post reply on HN
Print view View original

61–70 of 126 posts

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#61

Post by cpmsmith »

eridius wrote: post #29
petemill wrote: post #20

Earlier quoted context omitted.

FYI chrome on macOS supports handoff too

Huh, I didn't realize that. Of course, I rarely use Chrome (usually only when I need Flash, which is thankfully almost never). I assume when going iOS -> macOS it hands the URL to your default web browser?

Unfortunately not, I believe because when handing off web links, you have to demonstrate to Apple that you own a domain to be allowed to link to it.

What that practically means is if I'm on ycombinator.com, iOS won't let Chrome, a 3rd-party app, claim to be representative of any page on that domain without proof hosted on the domain.

https://developer.apple.com/library/content/documentation/Us...

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#64

Post by Klathmon »

JasonSage wrote: post #55
Klathmon wrote: post #24

Earlier quoted context omitted.

Chrome has been doing that for a long time and more. If you hunt around you'll find that chrome is even doing things like speculative DNS queries, opening TCP channels to endpoints that are often opened on pages that you might be trying to load, in some very limited cases even pre-downloading and executing a page "hidden" only to swap it in like you changed tabs once you "hit enter". [0][1] If you tend to be pretty "…

I don't know why, but when using a local development server only Safari manages to generate requests while typing the URL for me—Chrome does not. It's possible I've put more work into my Chrome privacy settings.

Chrome disables just about all of this when you have the developer tools open, so that might be what you are running into.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#65

Post by ttepasse »

ggregoire wrote: post #5

Honnest 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 don't like the chrome of Chrome.

Safari looks like it belongs here. Chrome does not. Also:

• The resources thing. I often use Safari windows with 100+ open tabs.

• I like Safari's tabs implementation better: new tabs go to the far right. In the past all browsers with tabs did that, now Safari seems to be the last holdout while the others seem to put new tabs to the right of the opening tab. I can understand the logic there but I find it unusable without a tree-like visualization like some Firefox extensions. If there is a browser which had this natively I'd be tempted. I still miss OmniWeb.

Safari's ⌘W-behavior for the new tab now jumps back to the tab which opened the newly closed tab. I really hope that isn't a hint of bad days to come.

Why this heavy focus on tabs? I basically use my default browser window as a LIFO stack of tabs to read. It works great for me, thirteen years and counting. I don't want that to change.

• When Safari went through its bad time, the WebKit2 area, I was tempted. Another detail which held me at the time: Safaris Pinch to Zoom on the trackpad was superior to everything else elsewhere. It still is but Firefox and Chrome at least but a little bit work into it.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#66

Post by johnhenry »

coldtea wrote: post #43
johnhenry wrote: post #39

Post 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.

> but by the very nature of the linked resource, at some point it won't tell you whether or not the claim is valid. What are you talking about? The linked resource is a JS feature matrix that shows how each browser does against those 2015/16/17 features, and it shows exactly what Safari tip passes.

When other browsers/engines reach compliance, it will be impossible to tell that Safari was "first".

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#67

Post by johnhenry »

cooper12 wrote: post #50
johnhenry wrote: post #39

Post 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.

I mean the title is the whole context. If you're worried about the table not being static, one can ideally refer to an archive [0] (just saved it) or since this is an open source project that is version controlled, the specific revision [1] displayed. [0]: https://web.archive.org/web/20161208203812/http://kangax.git... [1]: https://github.com/kangax/compat-table/blob/559825d41e7b8773...

I wouldn't say that I'm "worried", but the title states a fact that will likely, at some point, not be supported by the given link.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#68

Post by [deleted] »

cooper12 wrote: post #50
johnhenry wrote: post #39

Post 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.

I mean the title is the whole context. If you're worried about the table not being static, one can ideally refer to an archive [0] (just saved it) or since this is an open source project that is version controlled, the specific revision [1] displayed. [0]: https://web.archive.org/web/20161208203812/http://kangax.git... [1]: https://github.com/kangax/compat-table/blob/559825d41e7b8773...

[deleted]

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#69

Post by JasonSage »

Klathmon wrote: post #64
JasonSage wrote: post #55

Earlier quoted context omitted.

I don't know why, but when using a local development server only Safari manages to generate requests while typing the URL for me—Chrome does not. It's possible I've put more work into my Chrome privacy settings.

Chrome disables just about all of this when you have the developer tools open, so that might be what you are running into.

Thanks for the info, I'll keep an eye out for this sometime in the future!

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#70

Post by untog »

TheAceOfHearts wrote: post #52
sotojuan wrote: post #34

Earlier quoted context omitted.

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.

We'll use babel for builds. Most development will be happening on modern browsers, so being able to reduce compilation requirements improves your iteration cycle and it makes it much easier to debug. Source maps have lots of issues. Compare debugging async/await usage between the compiled and native version. If you're working on a larger project, compilation times start becoming a huge pain. Cutting down on the numbe…

Of course, all of this is true. It makes the life of a developer marginally easier. Unless there are edge cases where Babel and browser-native functionality differs.

Either way, WebRTC and Service Workers would allow us to expose totally new functionality to users. Huge difference.

Post reply on HN