kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 5 days agoJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.comexternal-linkmessage-square117linkfedilinkarrow-up1100arrow-down15
arrow-up195arrow-down1external-linkJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.comkirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 5 days agomessage-square117linkfedilink
minus-square1rre@discuss.tchncs.delinkfedilinkEnglisharrow-up2·5 days agoThe difference is people still write Java, regardless of whether it’s a dated pos or not, so the use cases have evolved Then there’s the use of the JVM/JRE which have evolved even more due to Scala, Clojure & Kotlin
minus-square_NetNomad@fedia.iolinkfedilinkarrow-up1·5 days agoCOBOL is still being updated because, believe it or not, people are still writing COBOL
minus-squaremagic_lobster_party@fedia.iolinkfedilinkarrow-up3·5 days agoPeople aren’t writing new projects in COBOL. It’s mostly to maintain 40+ year old systems. Unless you’re working in the bank sector, it’s unlikely you will write a program in COBOL.
minus-squareSirQuack@feddit.nllinkfedilinkEnglisharrow-up2·5 days agoDon’t forget this small sector called government. Loads of Cobol there.
The difference is people still write Java, regardless of whether it’s a dated pos or not, so the use cases have evolved
Then there’s the use of the JVM/JRE which have evolved even more due to Scala, Clojure & Kotlin
COBOL is still being updated because, believe it or not, people are still writing COBOL
People aren’t writing new projects in COBOL. It’s mostly to maintain 40+ year old systems. Unless you’re working in the bank sector, it’s unlikely you will write a program in COBOL.
Don’t forget this small sector called government. Loads of Cobol there.