A First Look At Red Hat Developer Studio

juanignaciosl writes "The first beta of Red Hat Developer Studio was published yesterday. RHDS seems promising. This IDE is a bunch of Eclipse plugins that comes from the fusion of JBoss IDE and Exadel Studio. The main advantages it offers are: JSF development improved, in particular integrating RichFaces and Ajax4JSF libraries; Seam (next J2EE middleware standard?) integration; and plugins for JBoss, Hibernate... Here are my first impressions."

Comments

Re:Sounds promising..

[TheAwfulTruth]

GUI builders are not IDEs they are one of MANY components to a real IDE.

An actual IDE takes care of GUI design, code editing, debugging, project management, documentation, source control and on and on. And they are scripted environments with plug-in interfaces, compilers and debuggers source control front entds etc. so that you can choose what programs you want to use for what tasks.

That is an Integrated Devlopment Environment. Admitedly IDEs are not for everyone but as this is the subject...

Visual Studio is hardly "perfect" but it is BY FAR in advace of /anything/ I've used on Linux that calls itself an "IDE".

Re:HuH?

[Bluesman]

Me too. I think that's what happens when you try to make a all-in-one solution without realizing there's a tradeoff between power and flexibility. You either make something that's too specific to be useful so that users have to constantly fight against design decisions you made, or something that requires almost as much work to make it do what you want than writing it from scratch would.

The ridiculously complex configuration files are a symptom of moving as many design decisions as possible out to the last possible moment. Complexity isn't reduced, it's just in a different place.

Which, ironically, makes the whole thing that much more complex, since now you have multiple places things can go wrong.

I tried using this stuff years ago, and found it wasn't close to worth the hassle, especially for a single developer. I just did a search for "J2EE success story," and the vast majority of hits were about a small team of Python programmers replacing large J2EE teams that failed to produce a working product.

But maybe I'm wrong, and the people who know much more than I do about this can list a hundred different projects where J2EE saved the company. It just seems like it's overhyped and people are really much more concerned about the scaffolding they're using than the work that they're supposed to be doing with it.