donbrae

HTML, JS and CSS all have great backwards compatiblity. I have sites that I built in 1997 that still render fine in browsers today. Features are really only ever added; very few are deprecated.

If anything, modern tooling raises the barrier considerably for new devs. Getting started with a simple HTML page, including some CSS and JavaScript, then running it in the browser is — by contrast — easy.

Those things are all great and probably far better optimised than your average should-be-static site serving bloat.

Ah, thanks. Didn’t realise that.

Netlify doesn't seem to have a consent banner but sites hosted on it don't set cookies, despite using Cloudflare (at least that's my experience hosting a blog on it).

Getting redirects too. The page on the Wayback Machine: http://web.archive.org/web/20201103140506/https://blog.leave...

In my admittedly limited testing I cannot fault the Figma web app in terms of responsiveness. Maybe it struggles with larger projects?

I think the web generally has these kind of use cases covered, although it would be nice to have the other things you mention (file system/iCloud integration, better accessibility [based on my understanding of Canvas' limitations in this area] etc.).

On the other hand, applications like Logic or Final Cut would be pretty much impossible to build in the browser.

AMP?

I use instant.page and it doesn't appear to work in Safari (at least in desktop version 13.1.2): I can't see any transfers in the Network tab on hover.

Doesn't bandwidth usage have an environmental impact? The effect of pre-fetching HTML would be negligible, however.

Great project!