News for hackers. Stuff that matters.
Re:Writing secure Go code by kaba0 on Monday November 04, 2024 @05:57PM (#42046941)
> It's so bad that there are companies promising JDK8

Come on, that's absolutely not the reason behind. That just means that there are banks and such that still run goddamn windows XP completely firewalled off from the internet just because. Similarly, for some companies not touching that ancient codebase and just having it safely run worth the hassle and the money.

Java is the most backwards compatible language and it is not even a close competition.

Re:Writing secure Go code by cyberax on Monday November 04, 2024 @08:34PM (#42047860)
> Similarly, for some companies not touching that ancient codebase and just having it safely run worth the hassle and the money. > Java is the most backwards compatible language and it is not even a close competition.

It's amazing to have two contradicting sentences right next to each other.

Re:Writing secure Go code by Yasuraka on Tuesday November 05, 2024 @03:18AM (#42049623)
> Java is the most backwards compatible language and it is not even a close competition.

In competitions consisting of Java, PHP and Python, I presume?

Re:Writing secure Go code by kaba0 on Tuesday November 05, 2024 @07:25AM (#42050969)
In competitions of real world code in a language that has been in use for close to 30 years, and I can find a java 1.1 program that will both compile as source on the latest version, AND the original compiled version itself will run on a modern JDK as is.
Re:Writing secure Go code by Yasuraka on Wednesday November 06, 2024 @05:54PM (#42070842)
And I assume this mythical 1.1 program does of course do a lot more than System.out.println and the reason that it took until recently, in part thanks to the Log4J fiasco, for 8 (almost 11 years old) to no longer be the most widely used version, was just superstition?