3 ms·
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
by sdevonoes 5y ago
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.
Monolithic apps. No frameworks, no package managers. Everything is provided by the house.
Monolithic apps. Monolithic frameworks. Libraries via package managers. Almost everything is provided by the house, but now we rely on a bunch of dependencies.
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.
Microservices. Serverless, lambdas. We start to put everything on the hands of others.
Here. We go back to point 1.
- kindofajsdev 5y agoI think I have to disagree with this one. I agree programming is cyclical. But I don’t think we will get rid of CDN’s. I don’t see js going anywhere and with that, I think package managers and bundlers are here with it. I can’t see people going back to vanilla js (even if someone made a more modern jquery alt). Why do you think start ups would go back to writing their own deps if the ecosystem is mature and said dependency wasn’t part of the core business?