The devs doing these kinds projects no longer think of the code as maintainable, but disposable. It's quite the 180 for a community obsessed with reusable npm packages and not reinventing the wheel. Last year Cursor bragged about ditching their CMS in 3 days: https://x.com/leerob/status/1999513884382597485
Comments
It really isn't. No-one wants to maintain these things, they'll be back on an out-sourced provider within 5 years, if they survive that long.
The devs doing these kinds projects no longer think of the code as maintainable, but disposable. It's quite the 180 for a community obsessed with reusable npm packages and not reinventing the wheel. Last year Cursor bragged about ditching their CMS in 3 days: https://x.com/leerob/status/1999513884382597485
It’s not a 180
It’s measuring time to iterate/ship, cost reduction and independence, which is really all that matters
Reusable was great because it used to be the fastest. The fastest now is vibe/slop > iterate > iterate > iterate > ship > iterate > ship etc…
Why maintain it?
Make a new one from scratch if needed.