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

Right idea, wrong reasons!

[Gazzonyx]

That's not the submitter's problem. You need to bone up on some acronyms, or you'll never make a goodJavaProgrammer. Here's a quick lesson in what you should do:

Write a thousand different programs using acronyms that start with J that do nothing except fuck up the data as it's being transmitted between the database and your application. Then, you have to write automated tools that also are acronyms that start with J and contain the word "Bean" in there somewhere, and those exist to generate parts of those previously mentioned thousand programs.
Huh? Are we using JBuilder? Bean... ah, we're talking J2EE. Something to build...something to build... if only we had 'factories' or something.

Then, write some Swing components that have nothing to do with all of this, and call those by almost exactly the same names, so that people get confused and can't do a proper Google search for documentation. Name an IDE after the Swing components, too.

How about that 60 meg folder called 'Docs' that comes with the JDK? It's even got pictures! You can drill down to the 'swing' section (think about the naming and that 'J' thing again while viewing this vs. the SWT ;) )

Finally, call it all "middleware," give it yet ANOTHER name and bundle it all together, making sure that everything breaks if you don't include fifty different XML configuration files in the proper directory hierarchy that changes with each version.

I guess it could be called 'glueware'. Try starting with '.', the hierarchy descends from there. Regardless of what your manager read in 'Buzzword of the Moment Daily', you don't have to use any XML.

Then when all of this doesn't work for more than one project because it's hopelessly complex, do it all over again and call it the next greatest revolution in Java middleware.

Trying using SCM, separation of concerns, encapsulation, and polymorphism.

All that being said, I don't much like java; I just think you're flaming it for the wrong reasons. How about if statements, operator overloading (or lack, thereof), switch statements, and the fact that it FINALLY just got autoboxing? Oh, yeah, and could they make the object names any longer? I can usually almost instantiate an object on a single 80 column line if my variable name is less than 4 letters. And why the crap am I always having to manually repaint the screen?! Just my $.02, YMMV. Fire in the hole!

Re:Right idea, wrong reasons!

[dkf]

Huh? Are we using JBuilder? Bean... ah, we're talking J2EE. Something to build...something to build... if only we had 'factories' or something. You do realize that 'factories' are old hat? You need a factory factory factory these days...