5 ms·
You can write unmaintained applications in any language or stack. An unmaintained system is not the language's fault, it's the maintainer's fault.
by hugi 4y ago
You can write unmaintained applications in any language or stack. An unmaintained system is not the language's fault, it's the maintainer's fault.
- nailer 4y agoSure it’s a culture thing, not a technical thing, but programming languages are technology with their own culture around them. Parent poster was advocating for ’write it and you’re done’ which was the nineties / early 2000s mentality. Because of the time Java was released it’s still common to think this way. Not a slight on Java, there’s things we’ll believe in 2040 that 2023 people won’t quite feel the same way about.
- hugi 4y agoI didn't understand the parent poster as advocating for "write it and you're done". To me "long term stability" and "things that will last over a year" simply mean it excels at creating maintainable software. Sure, the mentality you mention has always existed, regardless of language or environment. But I believe that by it's verbose, static nature, Java's maintainability is a great tool to fight against it.
- nailer 4y agoInteresting. I don’t see any additional value using Java over any other language for long term software that is actually maintained - supporting eg old versions of the compiler / runtime is an indication the parent is in the (still very common in some companies) ‘make it and it’s done’ approach. Oracle is appealing to the same companies that want to run Operating Systems till the end of life.