Shilling a bit but maybe check out wasp.sh, we are conceptually very similar to "Rails for JS"! Just don't tell Claude to completely copy us hehe (pls)

Nothing personal and I wish you the best of luck with wasp.sh, but the constant churn of new libraries that will revolutionize JS development, but are never quite finished and are eventually abandoned in a semi functional state is exhausting and exactly the main issue I have with the JS ecosystem in general.

At this point, I'm convinced there's a secret global conspiracy to prank JS developers. For example 1 person maintaining 3 similar-but-distinct decimal libraries for Javascript, or the top 3 PDF processing libraries silently producing blank outputs.

I came at this from the opposite direction in that I had zero coding experience and started learning ~7-8 months ago. I picked Rails specifically because everyone kept saying "it's dead" but every actual builder I talked to said "it just works." They were right. Rails gave me sensible defaults for everything I needed; auth, background jobs, file storage, payments...without me having to evaluate 30 competing npm packages for each concern. I shipped a production app with real Stripe payments as a solo dev with no CS degree. I genuinely don't understand how someone starting from scratch today navigates the JS ecosystem without losing months just to decision fatigue on tooling.