Java's Backup Plan If Oracle Fumbles
GMGruman writes "In an InfoWorld blog, Paul Krill suggests that those concerned that Java might get lost in Oracle's tangle of acquired technologies should relax a little: Java's future isn't wholly in Oracle's hands, so if Oracle screws up or lets Java languish, the popular language has other forces to move it forward nonetheless."
If you weigh more than 400lbs and have Aspergers and you can't get laid and the only job you can get is cleaning out Supermarket trash then you are a java programmer. Meanwhile winners use C#.net Professional.
Which is pretty much Visual Basic with Java syntax. I find Java source code a tad easier to read and Javadoc make C#'s cumbersome "compiled comments" look silly. Does Java still have checked exceptions in common use? In that case I envy you guys. Scratching my head over which exceptions can spew out of a library is annoying, even if checked exceptions can be annoying at times too.
There have been many discussion about multi-core processing being the way forward as we have already, more or less, reached the limit of what can be done with a single processor. Multi-core and multi-processor methods are expected to transition to multiple cores. At the moment, we have the core OS managing processor time on multiple processors but that's not the efficiency that has been imagined even it if it helpful and yields good results. So what about Java? The language itself is of the classical variety. The "interpreter/VM" of Java is what runs the code, but I haven't seen or heard anything in the way of it advancing to take advantage of multi-processor platforms.
Is Java doomed to get stuck behind in the single processor world or will it actually pave the way forward by running its VM across multiple cores?