James Gosling Grades Oracle's Handling of Sun's Tech 223
snydeq writes "With the four-year anniversary of Oracle's Sun Microsystems acquisition looming, InfoWorld reached out to Java founder James Gosling to rate how Oracle has done in shepherding Sun technology. Gosling gives Oracle eyebrow-raising grades, lauding Oracle's handling of Java, despite his past acrimony toward Oracle over Java (remember those T-shirts?), and giving Oracle a flat-out failing grade on what has become of Solaris OS."
That James Gosling fella is of no consequence... (Score:5, Interesting)
While I applaud James for his contribution to Java, I am afraid he's of no consequence to its direction now.
It would have been better if he proposed some kind of direction Oracle should have taken with Java.
VirtualBox? (Score:5, Interesting)
Re:VirtualBox? (Score:3, Interesting)
I'd agree. I'm a huge fan of Virtual Box and it's kept improving, all the time, no matter which company "owned" it, Innotek, Sun, Oracle. A really great job by everyone involved. I've hardly used VMWare Workstation ever, and as far as I can see, whatever lead that had over Virtual Box years ago, has vanished, in terms of features and compatibility. Virtual Box is certainly smaller than VMWare Workstation.
Re:Java in the server, in the client, in the brows (Score:3, Interesting)
Sometimes reliability is more important then having a pretty UI.
Re:No mention of SPARC? (Score:4, Interesting)
He did grade SPARC. He said that it was tough to tell, since SPARC was floundering well before Oracle took over.
SPARC is interesting, but for the OpenSPARC/sparc.org consortium. I don't see how Oracle gains squat by promoting SPARC: the only reason SPARC is alive is Fujitsu SPARC64. Otherwise, SPARC would have been EOLed, just like the SPARCstations.
I think SPARC has a limited market, since routers are now MIPS and maybe ARM, consoles were MIPS & Power and moving to AMD, servers are x64 and later maybe ARM64.
Re:An F- for the handling of Solaris (Score:5, Interesting)
I completely agree. Solaris "was" a great OS. With some very notable monster issues. Oracle has effectively killed Solaris. I simple can't use it anymore. The licensing costs of it and the software that runs on it are more than my total IT budget. Despite it's fantastic attributes I can no longer afford to put this in my Datacenter. With on demand virtualisation I can not afford to have to worry about things like. "Am I going to violate my license conditions if I spin up X more?"
I had an Oracle sale rep try to sell my that ridiculous Oracle stack in a box Exadata/logic. I was almost crying in laughter by the end of the sales presentation. 2/3 of the way through I stood up and wrote on the white board "Tell me how this isn't vendor lock in?". I called time at the 1 hour mark. I ended the meeting with the simple statement. Everything you have shown me is all about "vendor lock in" every word out of your mouths just re-enforced this concept. I had one question for you the entire meeting and you simple could not in any way respond to it.
So I priced everything I might need on Amazon. Using free and commercial AMI's with the odd vendor SW package tossed in. My first year spend was 1/25th of the Exadata discounted opening price. Nothing on the EC2 list had anything to do with Solaris. This is how you kill something. Make it financially ridiculous.
Issues with Solaris. That should have been addressed in the Oracle years.
- Package manager was brain dead. apt, yum are far better. ( Sorry Solaris 11 was too late. Too much legacy out there. )
- Patching made no sense. You have no idea what packages are patched with a patch. Patches were just binary disk vomit that spewed crud all over the system. Impossible in the real world to build any sort of verification around them. ( Sorry Solaris 11 was too late. Too much legacy out there. )
- Zones: Are a nightmare of security and privilege. I don't care what any says a zone is just a change root jail. Which means you will only every be as up-to-date as the host system. And it means you must be compatible and tested against the host system. Which is really no different than not having zones. Zones are a horrible horrible mess.
- No dependable only repository of packages that is robust or up to date. Far to much package hunting still required to locate software for solaris. Most packages are months to years behind there linux counterparts.
- Java performs better on x64 than Solaris/SPARC. This has boggled me for years. Only recent sparc architectures let java and other highly threaded applications stacks really perform well. Why do I even have to know about processor binding for processes?
Re:Java in the server, in the client, in the brows (Score:4, Interesting)
An outdated hack? That sounds mean... SWT was great at the time when it was needed. It is the reason why Eclipse never felt like a bloated, slow memory hog, in comparison to other Java applications of similar scope, like Netbeans. With SWT you had native, memory efficient UI components, whereas AWT/Swing duplicated everything into inefficient Java heap memory with slow Java2D rendering. It is true that now, with all the performance improvements Java and Swing have received, you barely notice a difference, so SWT isn't as essential as it used to be, but I still think it has the nicer API. Today I would probably use JavaFX
Re:Oracle's JAVA (Score:2, Interesting)
Just to be clear, you're upset that Google's attempt to take over the web doesn't play well with competing technologies? I do hope you're not surprised by this. You're helping Google shit on the web.
Re:Oracle's JAVA (Score:4, Interesting)
as many people do - get a copy of an app inspector - I recommend Addons Detector - and use it to see what dev tools were used for build the apps on your phone. You'll be surprised to see just how many were built with the NDK. All the fast and responsive games are at least.