Are those APIs supported by all major browsers or is it Chrome(-ium) only? Even if those are supported, it will mean the users may need to update their browser to use the site (but maybe the support is implemented long ago and that’s not much of an issue)
I see you answer that question for most of proposed APIs, but for some of them support is fragmented and/or present since 2025 and even 2026 for one. But at least it’s not a single browser vendor lock
Was a bit embarrassed when showing a prototype using Temporal last month and the provided computer’s Chrome turned out not recent enough to support it, so for this one API I’ll wait for one more year before considering it ready.
Check against Can I Use, all of the APIs, except for the following are supported by major browsers:
- Synchronous Clipboard API only Safari has full support, the rest have partial
- Temporal only currently supported in Chrome and Firefox
I mean, it’s good, but what needs to be replaced is javascript.
I’m intrigued, what would you replace it with?
Anything else, basically. There’s not a lot of languages that are currently used and much worse.
My preference would lean towards something like Nim, probably, but I’m definitely not the best one to answer that. But javascript and its whole ecosystem is rotten (I mean, that’s sort of the reason the article exists here) and it is just not fit to make anything. The fact that people even bring javascript as the backend is a bit crazy to me.
The fact that people even bring javascript as the backend is a bit crazy to me.
To clarify do you mean replacing JavaScript just on the backend? This article is about using JavaScript on the front end.
I mean both. But while I understand that there is for now not a lot of alternatives for web scripting, there is a lot of backend languages which makes backend javascript even worse.
