This article was originally published in print on December 3, 2003"Eclipse
represents the worst of Java"
Lately, there's been a lot of guff spouted about how Sun isn't joining
Eclipse. While I understand the bitterness aimed at Sun somewhat, I think
that this particular brand of talk is counterproductive and, dare I say it,
wrong. The talk tends to center around the concept of NetBeans and Eclipse
using common technology, and I think this is misguided, and here's why.
I really dislike Netbeans. I think it blows goats from here to Sussex, and
considering that I live in the middle o... (more)
Yesterday, Sun made an early access version of Studio Creator (i.e., "Project
Rave") available. I downloaded it for both of my normal development platforms
(the SPARCle, running Solaris, and Windows) and gave it a go.
On first impressions, Creator is meant to be a Web application development
tool, from the looks of it. There's no mention of distributed APIs outside of
the servlet environme... (more)
Lately it's been easy to dislike Sun. Their JVM is slow; Sun ONE is certainly
nowhere near the fastest J2EE application server; Forte, while capable, is
far from what coders actually want to use if they want to write code in a
reasonable amount of time; MS's constant marketing and technical assaults eat
away at Sun's armor; Sun's stock (as of this writing) is roughly a dismal $4.
All this... (more)
I am really coming around to Java Studio Creator. I spoke with Jim Inscore
from Sun today about it, after detailing my initial impressions on it, and we
spent some time discussing the product, its positioning, and its future role.
For one thing, he never called it "Rave," that I remember. I like the name
"Rave;" it's distinctive, it has a certain panache. That said, it's only a
code name ... (more)