I love the ideas you talked about with the solutions we are building for clients. I’ve also noticed the world of NPM and NodeJS over complicate websites we are building to the point at which if you build a website for a client using that tech, it will be out of date within 6 months to the point where source code is an entire rewrite to update functionality.
One way to solve this problem is build everything yourself. Not sure how practical that is for most businesses, but is the only way to guarantee the future of what you are building.
I feel like building for scratch is a solid option for teams building stuff for the long term, but if you want to hand your code after the service is over, this has some problems... But anywho, do you see any middle ground between this rapid cycle of npm packages and having to build everything from scratch, Joshua?
Strategy is different for every company. That’s why tools like WP are so widely used. To solve the problem you’re talking about, you need a platform to build on that delivers the abstraction you’re looking for. Headless CMSs seem to be middle compromise. It really depends on how much you want to build yourself.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I love the ideas you talked about with the solutions we are building for clients. I’ve also noticed the world of NPM and NodeJS over complicate websites we are building to the point at which if you build a website for a client using that tech, it will be out of date within 6 months to the point where source code is an entire rewrite to update functionality.
One way to solve this problem is build everything yourself. Not sure how practical that is for most businesses, but is the only way to guarantee the future of what you are building.
The npm fatigue is true hahaha
I feel like building for scratch is a solid option for teams building stuff for the long term, but if you want to hand your code after the service is over, this has some problems... But anywho, do you see any middle ground between this rapid cycle of npm packages and having to build everything from scratch, Joshua?
Strategy is different for every company. That’s why tools like WP are so widely used. To solve the problem you’re talking about, you need a platform to build on that delivers the abstraction you’re looking for. Headless CMSs seem to be middle compromise. It really depends on how much you want to build yourself.