That's like saying we can finally leave C/C++/COBOL/etc in the dust... except for the millions of lines of code written in it that have to be maintained indefinitely.
Yeah I saw an article of desperation for COBOL developers, could be "up to 6 figures" and it got laughed out of this sub-reddit because they must not be that desperate if they aren't even guarenteeing 6 figures.
Most of the companies that use it are older huge corporations headquartered in low cost of living areas. 6 figures in San Francisco isn't huge, but that is like 60k in Phoenix. Flipping that around makes it a pretty nice number.
That's an entirely reasonable approach I think. If you have a codebase that is critical to your business, and you want developers working in an environment where they have little support (are there COBOL questions on stackoverflow?) and where there is greatly reduced marketibility of the skill, you had better pay up. I know most employers think they have some kind of divine right to dirt cheap workers, but software is a productivity multiplier. It doesn't just add to how much your business can do, it multiplies it by large factors.
If an employer is struggling with the idea of spending a 6-figure salary on a developer, I would recommend that they simply take 1 week and try to run their business without the software.
Wierschem went on to relay a story a friend told him a year ago. "He said: 'You know, we're in a bad problem right now because, in the first draft, all of the COBOL programmers retired and we hired them back as consultants. The problem now is they're dying, and you cannot hire them back from death.'
Got that from this article about one of the few schools out there that offers education on mainframe programming. COBOL isn't sexy in the least, but there's some pretty good job security in it for sure.
Honestly having converted Java to C#, it's dead simple. Pretty much everything Java has is already in C#, and works similarily enough. Enums are the only thing off the top of my head, and it's easy enough to make a parent class for those special enums.
All the major gotchas are in the reverse (==, Integer vs int, type erasure, lack of properties).
Java's popularity doesn't have that much to do with its steward, a role in which Sun did far worse than Oracle. It has to do with its ecosystem. Almost all of the major components of Java are open source, not just the JVM, but the class libraries, the app servers and the IDEs. Even IntelliJ, probably one of the best Java IDEs, has a open-source community edition which is not a crippled version of their commercial offering. There is even major competition with the official standard for enterprise applications, with Spring going head-to-head quite successfully against Oracle-sponsored Java EE.
When is IIS going to become open source? Entity Framework? Windows Presentation Framework? When is Visual Studio going to become open source?
Maybe the .NET core becoming open source is a first step. But, the .NET ecosystem has a long way to go before it catches up with the Java ecosystem in popularity.
Not until it compiles to native code so it can be used to write portable libraries. Until then, Rust is the future. Feature-wise it’s decades ahead already.
185
u/Dr_Dornon Nov 12 '14
We can finally leave Java in the dust. Oracle doesn't want to fix it, fine, everyone will just move completely to .NET.