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.
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.