News for hackers. Stuff that matters.
Re:The sad state of sysadmin in the age of containers (2015) by apta on Monday December 09, 2019 @10:01AM (#21743181)
> I've had project where we needed all of 7,8,9 and 10 [0] for the data stack: Hadoop, Scala, Spark, HDFS, zookeeper, pyspark.

I suspect that a big reason was due to using Scala, which is notorious for not maintaining binary backward compatibility across minor releases.

Re:The sad state of sysadmin in the age of containers (2015) by lmm on Monday December 09, 2019 @06:49PM (#21748032)
Scala breaks binary compatibility approximately every 2-3 years, which is fast by JVM standards but slow compared to most programming languages (e.g. Python releases an incompatible version every 1-2 years). You can blame Scala for at most one incompatibility in that long list; older versions of Scala are incompatible with Java 9+ (this is true for many JVM frameworks too, as Java 9 made breaking changes).
Re:The sad state of sysadmin in the age of containers (2015) by raquo on Monday December 09, 2019 @05:56PM (#21747568)
Scala's version is epoch.major.minor, not major.minor.patch. I though 2.12.(x+1) is generally binary compatible with 2.12.x. Or at least I personally never ran into that issue with Scala itself.
Re:The sad state of sysadmin in the age of containers (2015) by paulddraper on Monday December 09, 2019 @05:25PM (#21747320)
To be fair, most languages don't maintain backward binary compatibility.

In fact, this is so common that some package managers don't even bother distributing binaries: go modules, cargo, conan, etc.