I’ve been a dev for a few years so definitely not as experienced as some of you.<p>I switched companies sometime ago. The first place was a rails shop and I loved rails. But then I switched to a shop that uses hasura + netlify and I just can’t see a reason why to never use this pair for CRUD apps.<p>I imagine we will see more frameworks based around east deployment of serverless functions and edge compute for backend tasks. I think the frontend side is being to mature and react/others are here to stay for a long while. But I’d like to hear thoughts from more experienced people.
The next wave of web frameworks is going to be all about keeping stuff at home. No more lambdas, no more serverless, no more CDNs, no more vendoring. It's all a cycle.<p>Monolithic apps. No frameworks, no package managers. Everything is provided by the house.<p>Monolithic apps. Monolithic frameworks. Libraries via package managers. Almost everything is provided by the house, but now we rely on a bunch of dependencies.<p>Microservices. Different frameworks for each part (frontend, backend, databases). We still keep stuff on our domain. No serverless yet, but we start to keep stuff out of the house. Dependencies on CDNs.<p>Microservices. Serverless, lambdas. We start to put everything on the hands of others.<p>Here. We go back to point 1.
New things come along, developers get excited, proclaim we finally have the ultimate language, framework, tool, architecture. Rinse, repeat. All of the code developed in last week’s or last year’s big thing is still out there, now dismissed as legacy, full of technical debt. Programming is like fashion that way.<p>Lots of decades-old COBOL code still runs enterprise businesses. Something like 75% of all public web sites were written in PHP, dismissed as obsolete for years. So in a sense everything developers use at all is here to stay for a long while, because the cost and risk of replacing it every few months is too high, and programmers hate maintaining legacy code.<p>After enough time in the development business you figure out that we mostly reinvent the same flat tire over and over.
> But then I switched to a shop that uses hasura + netlify and I just can’t see a reason why to never use this pair for CRUD apps<p>That's a pretty big statement. You seriously haven't ran across any drawbacks/limitations whatsoever? None? I'd be a bit more suspicious if I were you.
Personally I like the JAM stack. I refuse to learn things like React as I don't consider myself a pro, and React is a pro-tool. It's like bringing a gun to a knife fight IMHO.