Tag Archives: java

JavaScript is the new Perl

Still don’t believe that JavaScript is the new Perl? jQuery and NodeJS modules, likened to a very distributed collection of Perl modules, are the glue that holds together the JavaScript ecosystem, provides browser compatibility, and it admittedly does a pretty good job; however, sooner or later, the lack of language constructs like truly enforceable namespace boundaries, and the general mess created when teams get a little bit bigger is going to set in. This is seen over and over as the new wave of developers comes into corporate life: Larger companies try out new technologies all the time, then decide it’s costing measurably, and switch back to a stack that is resilient enough to withstand sloppy code.
more on ocpsoft.org

Luckily I don’t have to worry about the mythical “enterprise” beast anymore. While JavaScript is sure to evolve and I am in fact looking forward to features similar to introduced by TypeScript, I don’t see it being replaced by something like Java anytime soon. That would be a regression.

Java creator James Gosling: ‘Google totally slimed Sun’

In his testimony last week, Schwartz explained his “grit our teeth” strategy after Android had its public debut as an incompatible variant of Sun’s Java. “We saw a handset bypass our brand and licensing restrictions…we decided to grit our teeth and support it so anyone supporting it would see us as part of the value chain,” he said. Apparently, continuing to seek a way to work with Google — to turn lemons into lemonade, as Gosling wrote — was preferable to engaging in a costly lawsuit.

The sad patent dance over Sun’s grave. In retrospective, Sun under Schwartz’s leadership looks like a somehow idealistic company. That made the demise inevitable.

Spring and Maven reduce feedback

So as I sat there today for several minutes watching maven download jars, I realised I want the pain that its shielding me from back in my face. Don’t medicate me away from pain with these abstractions. In the human body pain is feedback calling attention to something that needs to be fixed. The wise response is to pay attention, not to medicate. So this is why I am against maven and spring and the like. They attempt to cover over things that I want direct contact with, things that I want to feel, things that give me feedback. If my app is hard to configure, I want the feedback. If my app is a 50MB war with a ton of dependencies, I want the feedback.

Experiencing the pain of development makes sense only if something will be done about it, otherwise it’s just masochism.

Execution in the Kingdom of Nouns

Classes are really the only modeling tool Java provides you. So whenever a new idea occurs to you, you have to sculpt it or wrap it or smash at it until it becomes a thing, even if it began life as an action, a process, or any other non-“thing” concept.

I’ve really come around to what Perl folks were telling me 8 or 9 years ago: “Dude, not everything is an object.”

Steve Yegge’s old rant on how programming languages shape the way we think about the problems.

How (not) to write Factorial in Java.

So please, do us all a favor: if you have the urge to add complexity because “someday we’ll need it, I just know it!”, or because “it’s not sufficiently flexible enough” or “we need reusability in our code” or (God help us!) because it’s “cool”–just go home early.

Fantastic article on overengineering, featuring idiomatic Java programming style.

Apache declares war on Oracle over Java

Charging that Oracle has willfully disregarded the licensing terms for its own Java technology, the Apache Software Foundation has called upon other members of the Java Community Process (JCP) to vote against the next proposed version of the language, should Oracle continue to impose restrictions on open-source Java use.
more on itworld.com

The lost war on Java continues. “Lost” because I see nobody as a winner in the end here.


Apple has nothing to earn and everything to lose by open-sourcing its JDK, so don’t hold your breath.

Apple discontinuous development of Java Virtual Machine for Mac, effectively killing Java on this platform.

An update on JavaOne

Like many of you, every year we look forward to the workshops, conferences and events related to open source software. In our view, these are among the best ways we can engage the community, by sharing our experiences and learning from yours. So we’re sad to announce that we won’t be able to present at JavaOne this year. We wish that we could, but Oracle’s recent lawsuit against Google and open source has made it impossible for us to freely share our thoughts about the future of Java and open source generally.

Oracle’s efforts to kill Java are fruitful indeed.

Some more comments…

Lightning might strike and they might live up to their 2007 commitment to create an independent Java foundation. I’m not holding my breath, but if enough customers rose up in revolt, it could actually happen. But it would require Oracle customers to do this, since the only thing that Oracle pays attention to is money, and that’s what customers hand over to Oracle.

Java creator replies to comments on recent Oracle lawsuit.