Ruby is not targeting those kind of developers though.

It's C/C++ developers that typically prefer a no-fluff approach.

As polyglot developer, I am also for a no-fluff approach and vanilajs for the win.

One of the reasons Next.js is attractive to me, is exactly they have rediscovered why so many of us have stayed with SSR.

> no-fluff … Next.js

Hmm. We can agree to disagree on the definition of fluff.

	▲	pjmlp 13 hours ago \| parent [-]
		Sure, if you ignore the SSR and SSG part, which sadly most nodejs stuff lacks. Additionally, Next.js should only be used when SaaS product vendor doesn't allow for any other option, which sadly is the case when making themselves sellable to magpie developers, while riding VC money until the IPO takes off. I rather deliver, than do yak shaving, but at least can deliver only HTML and CSS if I chose to.