kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 23 days agoJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.comexternal-linkmessage-square99fedilinkarrow-up1316arrow-down113
arrow-up1303arrow-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 · 23 days agomessage-square99fedilink
minus-square1rre@discuss.tchncs.delinkfedilinkEnglisharrow-up11·23 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-up4·23 days agoCOBOL is still being updated because, believe it or not, people are still writing COBOL
minus-squaremagic_lobster_party@fedia.iolinkfedilinkarrow-up11arrow-down1·23 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.
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.