[flimsypremise]

15 years ago a frontend build was not a thing. You managed what few javascript and CSS dependencies you had via the order of the script and style tags in the header. Now a frontend build is a baked in requirement of any user-facing application, so whatever you end up doing in whatever language, you already have that one build to manage. If you choose to build your application in anything other than JS/TS, you are effectively adding an additional build to the project, with all of the associate overhead. If you stick with one language and one build, you are eliminating large swaths of unnecessary complexity right off the bat. Not to mention that you don't have to hire for the additional language for the dev team.

Unless there is a legacy system driving the requirements in a different direction, my default application architecture is always going to be server-side React at this point.

[breckenedge]

> Not to mention that you don't have to hire for the additional language for the dev team.

Or maybe hire people who can code in more than one framework.

[flimsypremise]

You could, but I doubt anyone with budget responsibilities is going to appreciate you making hiring more difficult and expensive.

[ricardobeat]

I hope you realize how depressing this statement is. “Coding in more than one framework” is an extremely low bar to hire for.

[bakuninsbart]

User facing in what way? There seem to still be a ton of new RoR or Django projects without react/ or angular out there.

[flimsypremise]

Using facing meaning they have a UI. Even the simplest of which has some degree of CSS and generally a bit of JS. Unless you want to go back to the jquery and vanilla CSS days, which I can promise you none of the your developers will thank you for, you need a frontend build of some kind.

[ecshafer]

I want to go back to the Jquery days. It’s more than sufficient for 95% of websites.