I'd like to get into the nuance of Frontend vs. Backend vs. Full-stack, given all the buzz around Laravel and the JS ecosystem. My take is that w

The “full-stack framework” fallacy

submited by

Style Pass

2024-06-07 05:30:05

I'd like to get into the nuance of Frontend vs. Backend vs. Full-stack, given all the buzz around Laravel and the JS ecosystem.

My take is that when people want the JS ecosystem to have a Ruby on Rails type of full-stack offering, what they really want is an opinionated backend ecosystem that interoperates seamlessly with their frontends in a way that empowers full-stack developers to easily build apps that can scale.

Not having these in a consistent package is a huge pain point surfaced by this whole discussion, and highlights the fragmentation of the JS ecosystem. Beyond decision fatigue, or wiring together a constellation of frameworks, libraries and services, it’s cumbersome today for an ecosystem to develop. It’s not easy to:

However, I’ll posit that this backend doesn't need to tightly couple with html rendering or your client-specific logic.

However, this doesn't need to be the same framework as your backend (and probably shouldn't if you care about multi-platform support).