User: jedi_programmer

Re:AWT!=Advanced Windowing Toolkit

On: 10 Reasons We Need Java 3

I always thought it stood for Awful Windowing Toolkit =)

amen

On: 10 Reasons We Need Java 3

1. XML does not cure cancer, end world hunger, or promote peace between people with thousands of years of historic animosity. In many ways it is S-exp, rediscovered much later, done poorly.
2. Lisp (and its derivatives) get a lot of things right, especially the minor detail of trying to take the complexity out of doing things and putting the power in the hands of the programmer.

...a couple more things...

On: 10 Reasons We Need Java 3

Rather than looking at the problem as a single amorphous blob, there are three discrete pieces to consider here:

1. Virtual Machine
2. Language Specification
3. Supporting Libraries

The biggest problem with all of these is that Sun alone owns the spec. I doubt it would be possible for highly motivated individuals to try and "fix" any of these items (as in Open Source project) without Sun legal getting their undies in a knot. Sun at minimum shot themselves in the foot by not submitting all of the pieces that make up Java to ECMA or another recognized standards body. Like it or not, this is where M$ will pull ahead with C# and CLR - even though they are everyone's favorite Evil Corporation.

Anyone who has taken a deep look at the the JVM has to question its design (exercise left to the reader). It's interesting to see how the JVM's CISC-like, non-orthogonal instruction set has been perpetuated by one of the leading RISC vendors (perhaps it's not really RISC anymore these days).

The language itself has lots of holes - realizing of course that nothing is perfect. Primitives in Java are messy at best. I hate having a million get() and set() methods to follow the supposed JavaBean "pattern". Why not support something like Properties in C#? Generics? Coming Real Soon Now. Unfortunately the bureaucracy and lack of timeliness in the JCP leaves someting to be desired. A quick reminder: How long did it take to get simple assertions added?

I could easily get over some of the bumps in the JVM and language spec if the standard and extended libraries had some god's-eye view design applied to them. No one but Sun can touch the java.* packages, and javax.* is under their thumb as well.

What rocket scientist thought of java.awt.List and java.util.List? (perhaps no one at Sun ever works with Collections and GUIs at the same time). java.net.URL is a first class citizen, while URLs in other places (such as JDBC connections) are simply Strings. Sure, these are minor details, but they reflect a lack of maturity at many levels - and as they say, the devil is in the details. I won't even go into the monster that is EJB, since that to me is a lesson in how to make the simple very complex.

Bottom line is this: Java has its flaws, many of which can be lived with. But Sun having a stranglehold on the spec is a serious deterrent for anyone (beyond Sun) to step up to plate and make a difference. It's quite sad, since Java is the least of many evils out there in terms of building software in general, and I would love to see it mature well and eventually succeed.

So, anyone want to redo this the right way, free of Sun's shadow?

hi-tech stick figures

On: Searching for Exceptional Multimedia Productions?

stickdeath

but of course...!

On: Searching for Exceptional Multimedia Productions?

jodi.org or superbad.com

Now you owe me $5 for doing your research for you.

Interesting Revenue Tactic

On: Notes From the Cathedral

This article is posted at "themestream", which coincidentally says:

Articles receive 10-cents per viewing (limited time offer)
Exposure to Millions of Readers
Complete Editorial Freedom
Develop a Portfolio of All Your Writing

Question: Should /. readers subsidize an author that repeats a well-worn topic around here? There is nothing new in this author's rambling... and it's an incomplete article at that!

Is Hemos getting a cut of the dimes we're throwing the author's way? =)