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

HuH?

[russ1337]

"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.."

Now I know that is in English, but I have no idea what half of those words mean.

Re:HuH?

[140Mandak262Jamuna]

You think he knows more about the words than you do? Those who know, do. Those who don't talk.

Re:HuH?

[Frymaster]

You think he knows more about the words than you do? Those who know, do. Those who don't talk.

those who don't and think they do, post on slashdot.

Re:HuH?

[Bluesman]

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.

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.

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.

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.

Re:HuH?

[Bluesman]

Actually, I was being a bit facetious.

People actually DO get J2EE apps to work. Here is a very informative instructional video by some Japanese researchers who show how it's done:

J2EE Example

Re:HuH?

[iwan-nl]

PMS applications? *shudders*

Re:But does it support JCV

[WED Fan]

Whole new bunch of acronyms are coming down the pipe. I don't think all are web, and may not be associated with a particular OS or file format. Microsoft just trade marked, patented and are looking for fast track ISO approval of the following:

• SUP
• ERCA
• LIFR
• AGILIST
• ICEX
• PIA
• LIDOC
• IOUS

This according to an attorney in their IP department, M. Poppins.

The sound of it is quite atrocious.

Does anyone have insight on these?

Re:But does it support JCV

[Anonymous Coward]

> Seriously, do these flavor of the month java libraries mean anything to anyone?

Yes, they make them specifically for no-talent hacks on slashdot can sneer at them and say how they could write a distributed transaction backend with reliable multicast messaging using PHP and MySQL in a week.