The reason is probably not because those 10 products are simply nightmarish from a security perspective and expose the lions share of the vulnerabilities in their own code paths, it's because of unchecked dependencies. Somewhere I saw a statistic that says over 90% of container images in the wild contain unpatched CVE vulnerabilities and (searching.) here's an article that shows just how bad the problem is, according to this article in just the top 10 docker images, there are over 8000 known vulnerable paths. I don't know about that, I think that is still a strong selling point for Go, even in a containerized environment. standalone executables with no need for a runtime environment). > If anything, easy containerization negates one of Go's strongest selling points (i.e. I've seen zero actual encroachment into anything that earns me money for the past 10 years now, and at this point I'll probably be retired before I have to worry about it. But they never really gain serious traction beyond a non-Java niche area, and/or devolve into endless arguments about generics or whatever. The next major downturn will be interesting to watch.Īnd JavaScript is the only JVM-alternative to take seriously at all. Hell, most of that crowd has never had the experience of working for a company that turns a profit. But most of that crowd doesn't understand what the terms "EAI" or "ETL" even mean. JavaScript webdevs writing their own REST endpoints to fetch user settings from the database). Node might pick away at some of the lowest-hanging fruit (e.g. Particularly with pieces requiring heavily distributed design. Java's bread and butter is EAI, ETL, and server-side business application development. Webassembly? Really? That's a client-side tech, and 99.999% of Java devs ceded the browser battleground pre-9/11.
It's hard for me to take all the "Java is dying" threads seriously when they don't even seem to understand where Java plays. I'm glad I saw the writing on the wall and switched, but the problem is that Java is still being taught a lot at schools, and school programs especially universities are hard to adapt and only change every 4-5 years or so. It's clear at this stage that they bought Sun in order to slowly turn Java proprietary, and charge billions to the companies that are now fully Java-based for the next few decades. Oracle did not take a note from the Microsoft book and is really behaving that an evil corporate overlord. When I used to do Java, I always found that Spring was a much better framework than Java EE, and have used it in most projects I've worked. I have the impression that a lot of the mindshare has switched to the Node and Javascript ecosystem, especially the frontend devs, via the Typescript / Angular path, which is a natural path to Java developers due to the comfort given by familiar concepts like static types, classes, etc. The Java ecosystem has been slowly dying for years, it's already the new Cobol at this stage.
0 kommentar(er)
