3 ms·

> What stack do I pick today that will still be running in 30 years? This is such a backward mindset, though. Software evolves. Ecosystems evolve. Perhaps most

by pc86 4y ago

> What stack do I pick today that will still be running in 30 years? This is such a backward mindset, though. Software evolves. Ecosystems evolve. Perhaps most importantly, security risks and surface areas evolve (which in part necessitates the prior points). There is no good reason for systems to stagnate over three decades. Software isn't construction, it's gardening, and it requires constant maintenance and attention.

ElectricalUnion 4y ago
> Software isn't construction, it's gardening, and it requires constant maintenance and attention. Software is like construction, you don't demolish everything and start from scratch just because it's a little, or very old. Discarding everything and rewriting in another language is a expensive and error prone process. To cite the excellent Joel blog: > the single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch. https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...
- pc86 4y ago
  Where did I suggest rewriting things from scratch?