I didn't like working with it much personally (using Express). Typescript always feels very clunky to me, and if doing it in Javascript you lose type safety obv

I didn't like working with it much personally (using Express). Typescript always feels very clunky to me, and if doing it in Javascript you lose type safety obviously. The package ecosystem I didn't like very much, too many changes to stay up to date with things for limited benefit. Currently work in Go and Flask depending on what the service is, much easier to work with than Node. The most productive I've ever felt was with Django + REST Framework, mainly because so much is built in and it has a good package ecosystem around it. If working with a database the migration support is amazing. I've heard Rails is similar but never tried it personally. But with all this, I usually say to people to stick to what they know or what the hiring market can support. There's no point learning for e.g. Elixir if you can't find devs to work on it without upskilling them.