Stanley Ho is Insane

Stanley Ho shows up for another meeting of the JSR 277 Java Modules Specification with a brand new versioning scheme
Stanley Ho shows up for another meeting of the JSR 277 Java Modules Specification

Dear god, why are we subjected to such hubris?
Stanley Ho, working on the Java Module System (formerly known as JSR 277) has decided that Sun is so smart that they need to invent yet another versioning system. Now, maybe Stanley Ho really is a super smart dude who makes me look like I was a fifth rate, multiple generation inbred dufus from the white trash mountains of Virginny (many, many people have actually pointed that I actually am a fifth rate, multiple generation inbred dufus from the white trash mountains of Virginny, but I digress), but it seems to me that it is self evident that versioning is what we in the business know as a HARD PROBLEMtm. And to think that someone even as super intelligent as those people at Sun are known to be will come up with a scheme that doesn’t have any unintended consequences that were not foreseen by even their Spicetm enhanced brains is simply something that I think you’ll find many in this industry simply can’t conceive.
There will be bugs in what Stanley has designed. There will be unintended consequences. It will only be after years of serious use and abuse by many hundreds of thousands of developers in real world situations that even the Spicetm enhanced mind of Stanley Ho hasn’t dreamed of will the full extent of his hubris become clear.
One might ask the question: “Why, Stanley, didn’t you use the OSGi versioning scheme?”.
<crickets chirping>
This shit is hard. This path is fraught with peril. In the 21st century, we simply don’t go around inventing shit for the hell of it simply because we can. We reuse existing things even though they might not be the correct shade of purple we were dying to have. Simply because the corners are a bit worn.
The absolute last thing we need from Sun in the Java Modules is Yet Another Brilliant Sun Shiny Invention that we’ll have to suffer though for years until all the bullshit is extracted from the hubris that went into creating.
Geebus. Please. Dear God. Please.
Stop the madness. Someone please hold an intervention with these people. The industry simply cannot stand to have this crap thrown at them, especially in something as fundamental and as far reaching as the frickin’ base Java module system.
See Peter Krien’s rant on the hubris that is Stanley Ho.
Sometimes a turd is just a turd

4 thoughts on “Stanley Ho is Insane

  1. Right on, Hal. Sun is the company that brought us the Java Bean, (Session and Entity) Enterprise Java Bean, and Message Bean madness, and also the Java / JavaScript madness. There were so many ways to slice and dice that packaging, and Sun promoted the worst one possible, one which has created 10+ years of confusion.
    Its amazing that company universally reviled for its software products holds so much sway in the software business.

  2. As far as I can tell, sun made three major changes to the OSGi scheme:
    1. 4, instead of 3, numbers. From the need to pander to companies that will just incessantly whine that ‘3 just isn’t enough’, this seems to make some sense. I’m sure sun agrees that you can make do with 3, but this way leads to more uptake and less with the whines. That’s a good thing – and this is pretty inconsequential in the big picture. A friend of mine is miffed that they didn’t just allow an infinite amount of numbers. I’d even consider that inconsequential. As long as the definitions of the first batch of X numbers are clear about what they mean (backwards compatible or not, etcetera), then, eh. It looks like sun decided to go with 2 numbers for minor, instead of OSGi’s one, and isn’t too obvious about the distinction. Big whoop.
    2. Replaced . with – for the textual addendum, and defined addendums to be less ‘high’ than an addendum-free counterpart, and unsorted, instead of OSGi’s addendums are higher, and are sorted bit. Frankly, OSGi’s addendum strategy is dumb as a bag of nails, and this makes far more sense. Enough sense to break with tradition? Not by itself, but combined with #1, probably. I was thoroughly swayed by Stanley’s passionate argument that OSGi’s addendums aren’t good. Can you name me a realistic situation where OSGi’s addendums will work better / have less unintended consequences than Sun’s? This entire blog post is more a random heaping of praise on OSGi and then by extension blaming Sun for not adopting such sheer genius, without defining any of the genius.
    3. More ways to specify version bounds. I’m tempted to like this one as well; Many java users (incorrectly, but it’s not for a JSR to change everyone’s mind or piss all over them if they don’t wanna) don’t want to deal with new versions and just want a single one, so having a single version really bind you to that one particular version instead of doing random ‘you probably intended this’ magic the way OSGi does, is good. However, that means you need an easy way to specify that you’ll take the latest v1.1, and 1.1.* is easier to write, and easier to read, and slightly easier to understand, then [1.1, 1.2). Also, this seems inconsequential in the big picture.
    Sun being less arrogant than the main competition? I thought I’d never see the day. This isn’t the only blog post with the central theme that OSGi evangelists out-arrogant Sun while whining about Sun’s arrogance. Is that irony? For someone officially On The Fence, you’re doing a bang up job of proving that Sun’s got their head screwed on a lot better than the OSGi gang + evangelists. May I kindly suggest you get into actual arguments about why Sun’s versioning system isn’t enough of an improvement to warrant breaking compatibility? I’d listen to those. Heck, until the OSGi-sphere’s reaction to Stanley Ho, I was on OSGi’s side. Any team that reacts with universal ridicule to a proposal that doesn’t on the surface look so different from your own gets my ‘arrogant asshats that need to be tossed off their pillar’ detector going.

  3. ny team that reacts with universal ridicule to a proposal that doesn’t on the surface look so different from your own gets my ‘arrogant asshats that need to be tossed off their pillar’ detector going.
    Concern trolls give me much the same reaction, I’m afraid. But in any case, thanks for your concern. Duly noted. Have a wonderful day.

  4. Yo no pienso que OSGi sea la solución como decimos si Stanly Ho puede tener errores por que no OSGI, esto lo podemos ver en eclipse donde el sistema de módulos y plugins es vulgar y malo es engorroso para un novato poder instalar un plugin por lo mínimo que sea. OSGi no es el Dios si no una opción y OSGi no tiene soporte por parte del JVM como si lo tendrá JSR 277 pienso que el sistema de versiones esta bien y se puede ver que este sistema sirve del lado de .Net donde se utilizan cuatro dígitos y nadie se pone a pelear por estupideces en ves de decir que OSGi es mejor cuando OSGi es un conjunto de librerías que me dan modularización pero que no están tan bien integradas en su totalidad con la JVM.

Comments are closed.