I always wonder why Hacker News is such a magnet for comments trashing product announcements while also knowing almost nothing about the product being announced.

In the long run the approach Svelte takes seems very promising so I've kept an eye on it for a while now. I took umbrage at the snooty messaging towards a browser in a tool pitched as a way to "build production-grade websites".

Sure but the "snooty messaging" you're commenting on is from their tutorial, which is used to conveniently learn the framework in the browser.

This has nothing to do with Sveltekit itself. You can download a demo repo, enter "npm run dev" and see that it works on Safari without any issues. Hell, I've deployed ecommerce sites using Sveltekit used by 500k people/month where 60% of visitors are on mobile Safari without any issues.

So when a product is posted that you are unfamiliar with, maybe try giving it more that 30 seconds of consideration before dismissing it due to something completely unrelated to the product itself.

That's the tutorial - which uses WebContainers, which are indeed an experimental technology. It has nothing to do with the production readiness of SvelteKit the framework.

That's for the interactive tutorial, not for the apps your build with Svelte/Kit.

Every website should display this message until apple either fixes the browser or lets you install chrome.

Safari is the new IE.

Wish it is but it's crazy fast with M1

Any browser is fast with the last CPU node. Safari is becoming compatibility nightmare.

The tutorial used Web Containers which... aren't a standard and are very specifically Chrome-only. And it undoubtedly relies on a bunch of Chrome-only non-standards, too.

> Web Containers which... aren't a standard

The implementation doesn't use chrome specific API AFAIK, and it works on firefox.

> are very specifically Chrome-only. And it undoubtedly relies on a bunch of Chrome-only non-standards, too.

It does support all majors browers, except safari.

The reason why it doesn't work on Safari is even listed:

> Safari recently shipped support for SharedArrayBuffer and cross-origin isolation in a somewhat buggy state. In addition to this, it is still lacking a few other features which prevents us from shipping a working environment such as:

> Atomics.waitAsync > Lookbehind in regular expressions

> Note that none of above can be pollyfilled.

These are not "Chrome-only non-standards" and are parts of the officials JS/HTTP specs

I stand corrected.

The reason for my comment is that far too often these complaints are about some things that Chrome ships at neck-breaking speed.

The standards do adds features too fast for the other browsers to catch up, that's true.

It's worse than that, sadly. A lot of what is perceived as standards (that is they have an official sounding spec on w3c somewhere) are actually not, and are just Chrome releasing stuff.

If you go to MDN and click on multiple experimental APIs you'll find they do have a spec. And they are shipped in Chrome. And then you start reading the spec and it says "It is not a W3C Standard nor is it on the W3C Standards Track.": https://developer.mozilla.org/en-US/docs/Web/API

We had to support ie.