1. oxc (oxlint)
2. vercel
3. fly.io
probably more! and more every day
Though when I asked they said it was like a long flight trip to aroynd the globe. While I don't believe that, I do believe that they are much more effective than they were 10+ years ago. Also I wouldn't have got my stomach surgery without my first one.
Also it's very hard to follow up bugs or other errors if users are often offline. I giess you can queue up errors being sent and so on but still. Syncing means that you probably have to have a complicated logic, especially if the data you are seeing can be modified by others. How do you solve merge conflicts?
I really like offline first web apps, but it is way harder and more expensive to build I think. For a startup it means more time before you can deploy your app and where I live there is pretty much fast internet everywhere so it kinda is solving an issue that very few customers will face.
Sadly the Ember team made some strange decisions in the beginning and it wasn't easily grokable compared to regular JavaScript (most of that has been fixed now, though).
This is all to say that whether or not it's JavaScript doesn't really matter, compared to the stability of the API.
My personal problem with JavaScript is that things keep changing too much.
So easy to setup and performs very well.
Other sectors that people today find is boring will have an upswing.