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."
I need an integrated IDE solution to support the latest JBC and WAJAX 2.1.2 standards, along with full SDJ support. Can this do that? Seriously, do these flavor of the month java libraries mean anything to anyone?
"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.
Yup, they are still around despite the best efforts of SCO. And RH is making useful and relevant (cross-distro too) tools unlike the Me crap from SCO. I am running this on ubuntu and can even deploy on different platforms! Sounds like RedHat is confident in the quality of their products, unlike that sue-happy company.
Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
Your confusing Red Hat with SCO.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
...welcome in advance our glossary-posting overlords!
Tsunami -- You can't bring a good wave down!
Trolltech's suite so far has been the best one I've seen yet but has licensing issues. I've tried KDevelop and it's not that bad, but still not great. The ones I've seen for gnome have been even harder.
A good IDE for developing GUI applications, should help the developer a bit more with the GUI stuff and not make it mandatory that you know every call to every function of every widget for whatever library that package supports. If you knew that, might as well stick with Emacs/vi/nano and code it. Which it seems is how most development is done. (which isn't bad) but makes it harder for someone else starting out and wanting to give it a try.
Java is too apparently.
Badass Resumes
I have yet to see an IDE that has a text editor that compares to TextMate. The fonts are ugly, color/theme management is poor, integration with the PC is poor or non-existent, and macros and custom code are much more difficult than TextMate.
These may be good when you need to manage massive projects, but I can't stand to use them for actually writing code. If there was only some way to replace the text editor in these IDEs with TextMate but keep all the trappings that make compiling and deploying these apps easy.
I'm in the hole of the broadband donut.
There are some truly nifty plugins for Eclipse: Mylar comes immediately to mind. Exadel Studio has some decent functionality, but it's grotesquely slow and not terribly stable either. And JBoss IDE always struck me as a few miscellaneous plugins that didn't really accomplish anything. The Hibernate stuff is all right if you're using the xml files, but I use JPA, and it's useless there.
All I really want are some clicky wizard dialogs for the functionality in seam-gen, and a decent stable IDE for Drools/JBossRules (which I don't think RHDS even includes).
Netbeans would be a more ideal IDE except for how it makes you really regret it if you subvert the bureacracy of the "add new file" wizard in a project. With eclipse, I can just drag new files in and hit refresh. That and Netbeans still has no TestNG plugin (the existing one always sucked, and doesn't even work in recent versions). I suppose I could pay for IDEA if I was still doing Java full time.
Done with slashdot, done with nerds, getting a life.
I love Aptana for my Rails programming. It's pretty damn awesome.
I have to say this a pretty scant entry for the front page of /. Amazing it got through really. Still this does look like quite a nice tool - I hope the port it to one of the better IDE's eventually. Eclipse always seems to me to be the Windows of Java IDE's. Hugely, unaccountably successful. It does everything but it doesn't do anything well. I actually prefer Netbeans of the free/open source tools though neither are a patch on IDEA.
"next J2EE middleware standard?"
Probably. Parts of Jboss Seam and Google Guice amongst others are being formalised into the JEE6 spec -
See http://jcp.org/en/jsr/detail?id=299. Oh and its JEE now, not J2EE. Has been for quite a while).
Could You name one that "Company"? I worked for World biggest Healthcare company, few Financial Institutions (including Banking) whose standardized on Eclipse with great success. You know, real programmers, don't necessarily need fancy GUI wizards for composing HTML pages, drag-and-drop class/build-file wizards, programming etc. - simply because developers doesn't project HTML, unless You work for one-person, swiss-knife DYI "company". You know, usually companies have HTML developers who use their own tools (and those are not Eclipse nor VS, from what I can see). So without generalization please. Artur
Hey everyone.. I work on the JBossTools and RHDS Team and just wanted to give some community-level info about our project.
p _id=22866&package_id=242269&release_id=531957
Red Hat Developer Studio is our commercial offering of the JBossTools open source project (formerly known as JBossIDE), which has a vibrant community of users and contributors. You can check out our project(s) at the following URLs:
JBossTools main page: http://jboss.org/tools
JBossTools blog: http://jbosstools.blogspot.com/
JBossTools 2.0.0.beta3: http://sourceforge.net/project/showfiles.php?grou
RHDS 1.0.0.beta1 (based on JBossTools 2.0.0.beta3): http://www.redhat.com/developers/rhds/index.html
Feel free to drop by #jbosstools on freenode, we'd love to hear from you!
arcane for life
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
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!
If I mod you up, it doesn't necessarily mean I agree with what you've said, sorry.
I know the parent is just flamebait, but for the record I'm blown away anyone would have this opinion. After using visual studio for several years, switching to Eclipse at a new job was a breath of fresh air. Sure you don't have the drag-and-drop UI design, but that aside the out-of-the-box features blow VS away and that's not even starting with the plugins, many of which are free and open source like the IDE itself.
You folks haven't done non-Java/Ruby (aka, non web app) development in Eclipse it seems. The CDT is a waste of bits - other than nice syntax highlighting, most of the eclipse functionality doesn't work.
I think the most frustrating thing with Java is how many things they did wrong in early versions that we have to deal with today. It's an extremely confusing language to learn from scratch because for everything that doesn't make sense, someone has to give you a history on why it's done that way. I agree that half of Java has been marketing (but hell, half of .net is marketing too!). It really is an amazing language with a very rich set of API's provided by Sun, don't get me wrong. I just think Java has such a bad history it may never recover from all the preconceived notions it is currently entangled in.
If an officer ever threatens to taze you, say you have a pacemaker.
Jesus Christ, will someone please rip off ASP.NET? I've looked at all the crazy proliferation of Java web frameworks and they all pretty much suck. You have to maintain a bunch of XML files for things that ASP.NET just figures out on its own, docs suck, architecture is bizarre. It's all just a giant, productivity draining mess. Why can't I just have transparent interaction between the page and code? Why do I have to "register" crap (through XML file) that should just be available transparently from page code? Why do I have to create "navigation rules"? Why do I have to "declare beans"?
No wonder turds like Ruby on Rails are so popular. I'd rather shoot myself than use Java for web development.
The linux community had this, it was called Kylix. It was bought to u by Borland. Borland priced it too high and the free versions weren't adopted by the OSS community. But tools like Visual Studio don't come free, but you really can't fault Borland for wanting to charge for it products.
I believe the GUI editor of the nice free Netbeans IDE is working something like the one of Visual Studio.
Not that I ever tried Visual Studio, but Netbeans Matisse GUI editor is really some of the most impressive UI stuff I've seen.
Start getting everyone you know to start leaning on the folks at CodeWorks to get Delphi & C++ Builder ported over to Linux. Say what you will about Borland, but imagine those 3 tools being completely X-Platform between Win32, Linux ( Gnome & KDE ) and OS-X. That alone would put a very LARGE dent in Visual Studio.
Hey KID! Yeah you, get the fuck off my lawn!
try wicket. no xml, no navigation rules, not a single piece of code in your markup files (it's simply not possible), ALL logic is in the java files. no stupid bean mapping to forms, a component concept (oh, there i can download a tabbed panel component, let's do this) that actually works. it really is what i think MVC should be like.
and a very good api design, KISS, no overhead and all that core servlet stuff is hidden from you.
On second thought, let's not go to Camelot. It is a silly place.
Google maps on my cell phone written in 100% in java loads in 3 seconds.
Doesn't sound slow to me.
http://saveie6.com/
How in the fuck was the parent post modded troll? It was a perfectly reasonable response to the GP.
This poo is cold.
"Your" means you have possession of something. "You're" is a contraction for "you are". Note the apostrophe, and notice how the addition of the apostrophe allows you to lose a letter (the "a"). That's how contractions work: you substitute the apostrophe for the missing letter(s) and combine the two words.
Rather than assume you weren't paying attention in first grade I'm going to assume you don't have English as a first language and give you a pass this time. But it's actually an important thing to remember- contractions are easy and simple, and using them incorrectly makes you come across as an ignorant dumbfuck.
(Hardly flamebait. An opinion outside what the majority thinks, apparently, but still not intentional flamebait. Go ahead and look through my history. I'll wait here.)
Eclipse is truly, truly terrible. It is hopelessly slow and buggy, and lacking in such basic features as to be useless. I'm absolutely shocked anyone could tolerate it, let alone call it "a breath of fresh air."
Open source is nice, but software needs to be judged on its own merits, rather than just the merits of its license. If the best defense you can come up with for software is that it's open source, you have completely failed to defend it.
I didn't like the syntax highlighting, either. It worked great for my code, but seemed to completely fail to parse system headers. Maybe they've fixed that by now, though.
Sure! Palm development environment is constructed with Eclipse. In a word, it sucks. But that isn't fair to sucking. I have never, ever seen a less capable development environment. Sure, the compilers suck - that isn't really Eclipse's fault, though. That's a plugin, right? The debugger also sucks. Oh, but that's a plugin too, right? The editor sucks, too. I think that's actually built in functionality, but I could be wrong. Qt's Eclipse-based tools? Also suck harshly. Symbian's? Suck harshly. Eclipse's own C Development Kit? Sucks harshly. Go ahead - I'm waiting. Tell me an Eclipsed-based product I can download that doesn't suck. I've just named at least three that you can download, one that's even included in the initial download.
One last thing: If the only IDE you can compare Eclipse to is VIsual Studio, you've led a sad, sad life. No wonder Eclipse seems almost decent.
It's missing an important piece to be compared to ASP.NET. Proper IDE support. After all that is what this discussion is about (No, the Eclipse, Netbeans plugins don't hold a candle).
You are a moron. Java is not slow.
Do you SERIOUSLY think that Java has survived over a decade and become the most popular development language in the world because of _hype_? Do you think that eBay and Google use Java because of hype?
This kind of brain-dead me-too critique of Java wasn't accurate five years ago and it even less accurate now. If you want hype, go see Ruby. Java is continuing on regardless because it gets the job done.
Yeah, being the most popular development language in the world is a shit of a position to be in. How will they ever cope?
Living With a Nerd
And apparently, I'm an ignorant dumbfuck because the entire sentence wasn't inside a parenthesis. /slaps self /backs away
Living With a Nerd
What are you talking about. Both eclipse and netbeans (and intellij IDEA) are vastly superior to Visual Studio.
evil is as evil does
You should take back your comment. Cause java IS slow once you start dealing with graphic library loading. If you use it to write ascii or computational programs then it is as fast as any other language.
It's disappointing that I got modded troll because it's acknowledged by most in the Java community that there were many big design mistakes in the first few versions of Java. Java 5 (aka 1.5) really was the first great version of Java.
The original GUI toolkit was admittedly thrown together for the sake of having a GUI toolkit. Swing is leaps and bounds better, but it's very confusing to beginners learning two GUI toolkits at the same time. If you didn't know the history of why there are two it's very confusing.
The original garbage collector sucked hardcore and was slow. The current garbage collector is actually pretty good, but for many they equate Java with being slow because of old versions.
Containers are leaps and bounds better and much more type-safe, but again it's confusing to beginners why there are so many redundant ways to use containers. There are numerous optimizations at the compiler level. The biggest being the ability compile code adaptively instead of the whole program on startup. I/O is confusing to learn and imo overly complex. Again, this is because of Java's subpar original I/O subsystem.
Java has really grown up and gotten leaps and bounds better over the years. Java today is what it should have been in the first place and what was originally advertised. That's where the marketing came in. Java honestly wasn't very impressive to me when it first gained attention. Today I'm very impressed by it. But most people don't understand how much Java has grown up and in their minds they have Java of 1999 stuck in their heads.
If an officer ever threatens to taze you, say you have a pacemaker.
The important question now is do they support Oracle back-ends and middle-ware. Some of us have to run with the adults you know.
While I agree that complex configuration files are a bane to development, I disagree with the assertion that J2EE requires them. ORM technologies like JPA are utilizing Java 5 annotations to declare configuration inline with code instead of XML. Frameworks like Wicket and GWT are providing developers with Java solutions to UI that are devoid of XML configuration, JSP, and markup-heavy implementations. IMHO, Wicket deserves to be called a breath of fresh air.
I do think it's a mistake for J2EE to include a particular view framework in its specification. JSF, while an innovation in the 90's, is simply a pig wearing lipstick compared to some of the new frameworks out there. Frameworks that, for example, are built on AJAX instead of including it as an afterthought.
I suppose the bewildering set of choices may be the root of the problem here. But if you make the effort to do your research, you'll find that many of your assumptions are incorrect.
Emacs, maybe?
Honestly, if all that a purely Mac OS X oriented editor is gonna come up with is some obscure, yet-another-programm-specific configuration and automation language that I have to learn to automate and speed up my everyday tasks, then I might aswell use the CLI version of Emacs right away. Ok, the 20 basic commands are really bizar (Crtl+V == Page down; Alt+V == Page up, Ctrl+x (for 'eXecute') Ctrl+s == Save, etc... ) but when I then go on to learn automation via Lisp, at least then I know my programm is free and runs on anything that uses electricity. And it's not more difficult to use than TestMate (apart from the first 20 I mentioned). And the OS X Terminal Fonts look just as good as everything else on the Mac.
Frankly the best editor in existance (OSS or not) is jEdit. The only problem I have with it is that it can be a performance hog and it bogs down my 1Ghz iBook with a mere 512MB (I know, I should've gotten 1GB) to much when I'm running other stuff in parallel. Aside from that, jEdit is way beyond any other editor out there (features and ease-of-use), including TextMate. However, if I ever should get so far as to start automating my programming and editor functions I'm not gonna use BeanShell (jEdits Script) or some strange proprietary TextMate Script PL. I'd rather use lisp for that. And be sure it runs on every enviroment I'll ever encounter for the rest of my life.
Why people think that a proprietary 2006 Emacs clone is the cream of Editors just because it uses the neat looking Aqua tray is beyond me. Use Emacs if you like that sort of stuff. Its plattform independant and it's so insanely fast on our modern computers that you'll finally know how much crunching power those 2Ghz+ really have.
We suffer more in our imagination than in reality. - Seneca
Sounds like you're looking for Seam. All the xml stuff is optional in Seam, so you'll actually come to like the xml configs for its good parts (like complex navigation rules) when you're not forced to use it for everything. No declaration needed, you don't even need "backing beans" or even a class for your page (take that, ASP.NET).
If you really want tight integration between page and code, there's wicket (which I frankly find awful) or Tapestry5 (which looks really nice, but it's not finished yet). Or if you prefer to just code guis straight to the web without all the multitier nonsense, there's no shortage of frameworks to choose from there, including GWT, Echo2, and Thinwire. There's even a few that will publish swing apps straight to the web, so you can design your page in Matisse. I don't personally recommend that approach, but it's there if you want it.
Done with slashdot, done with nerds, getting a life.
I was talking about the Wicket integration into these IDEs. ASP.NET is well integrated into VS. Wicket integration through plugins is relatively thin. Don't get me wrong. I have not used VS in 3-4 years although I have a copy and have been using Netbeans and Eclipse.
Let me put it this way. Java IDEs are the ONLY programs that make me wish I have a newer computer.
Java is now good because of Metcalfe's law. It has reached critical mass. Like you, I hated Java when it first came. It was the wrong solution for most things it was initially used for. Now things are beginning to look better. One thing that still bothers me is the mindset of the libraries and frameworks available. Many seem to fail to curb complexity. Either that or a person like me is not what they had in mind when they designed these.
It is often far simpler to use a dynamic language to cook something up very agile on the server side than resort to bloated app servers, xml hell, design pattern hell etc. Java, after 13 years still makes designing a client UI with some DB components more complicated and far less productive than it was with Delphi 1 or VB 3. And where are the third party components? I am pretty sure there are far far fewer Swing components now than Delphi with its modest user base did in 2000 (about 4000 OSS and 4000 commercial components in 2000 if I recall right).
Java will eventually get it all right but why is taking so long?
I'm not a big fan of eclipse (although I've tried it over, and over, and over, hoping one day it would make me "see the light" with some new, nice version). I wouldn't say it's popularity is due to a license though. Eclipse has momentum due to it being hyped as being representative of "industry best practices and standards". Some people are quite happy to use that as a metric for deciding to adopt it, regardless of whether those "best practices" apply to their particular programming problem or industry, or if the tool is actually technically superior to others available for the problem domain. This is a pervasive attitude in computing - there is an unusual and hard to explain aversion to having a diversity of ways to solve a problem. It's very much a "all you have is a hammer, so everything looks like a nail" mentality to me. I say use the right tool for the job, be it a language, framework, programming pattern, or editor. Choosing a "standard" because it's all you know or are comfortable with, and contorting it to do something it wasn't designed for is one of the contributing factors to all of the bad software that exists in the world.
I don't know about wicket per se but I bet it has an eclipse plug in. Every framework known to mankind has an eclipse plug in.
evil is as evil does
"Graphic library loading"????
Do you have two whole brain cells to rub together?
I can tell you that OpenGL and hardware accelerated 2d graphics work quite happily within Java.
Speaking about Visual Studio was not a matter of quality but of integration. Until Netbeans 5.5 I had never seen before a "all in one" open source package which let me develop a new project from scratch and deploy it in an application server. You use to have to install many different apps and libraries until it works. Nevertheless I wanted to avoid "direct confrontation" between NB and RHDS, since it's what people was doing for sure (just read comments here). Mentioning VS was neither comparison nor quality but an example of integration.
In theory, it should be possible to integrate Visual Studio with nearly anything. In practice, though, it's another one of those things that always seems to suck. Having never tried to write a plugin for it, I can't tell you if it is due to the complexity and/or flakiness of Visual Studio or just incompetence on the plugin developers. I suspect it's mostly Microsoft's fault...
Meh. I can't even think of a good IDE right now. I like a lot of the way Xcode works, but not all of it. Still, I thought Eclipse as a more-weak-than-average entry overall.
It's not the _connectivity_ what I whas talking about, but "packaging". VS is the best (and almost only) option if you use MS-only technologies, and it allows you to begin with them with little effort. That's what I think's worthy with RHDS: JBoss + RichFaces + Seam + JPA made easy.
IMHO, of course
Oh, certainly. I think VS is the best tool for Windows development, precisely because it's made by Microsoft. I honestly wouldn't use anything else. I hate the UI and a lot of the features, but there's little argument that it gets the job done in a way that only the OS developer could probably pull off.
:)
Apple's Xcode is similar on the Mac. There's a few things I like more than Visual Studio, and a few things that I like less. Overall, I think it's just about the same, with maybe a slight edge on design (which you'd expect when comparing an Apple product to a Microsoft one). It isn't as strong as it should be, though.
And yes, I see the same potential in RHDS. I know it's going to be well integrated. I just wish it was also good interface design, if you follow me.
And all of them have their strengths as IDEs, but it bothers me that they're all so weak. It shouldn't be hard to build an IDE that doesn't suck. I don't know what it says that programmers can't design good UIs for programmer tools.
Well, I don't agree "I don't know what it says that programmers can't design good UIs for programmer tools.". Eclipse can be better, but it's not bad IMHO.
Read my post again. I am saying that Wicket has plugins (for all 3 major IDEs in fact) and that they are nowhere as integrated as ASP.NET natively is with VS. Having a plugin says nothing. A plugin may do little more than add a couple of config files and add a build task to the project. That cannot equate with polished products.
>I am saying that Wicket has plugins (for all 3 major IDEs in fact) and that they are nowhere as integrated as ASP.NET natively is with VS.
What the hell does that mean?
What specifically is your gripe about the wicket plug in?
evil is as evil does
Wow just 3 seconds! On a processor running at 600MHz. You Java types have been so trained to low expectations you don't know what speed is.
an ill wind that blows no good
This cheapens the concept of "development". I guess Redhat is doomed only to be a webapp server and nothing more. Its time we get over java and move on.
Yes, really slow.
I checked the HelloWorld example, it look very similar to Tapestry (another Apache project). Two very similar projects under the same roof... no wonder web development is such a mess. Granted, Tapestry is more complex than wicket (at first sight; I'd have to look deeper). Looks like in wicket they got rid of the intermediate .page of .jwc files (XML files with the component definitions for the stuff in the HTML files; the page/jwc files is where you define the connections between UI components and the control classes).
Worth checking out, this wicket. If it's as powerful as Tapestry and is really simpler, I think we might switch. We have some medium to large size apps in Tapestry.
Go hug some trees.
> What specifically is your gripe about the wicket plug in?
What gripe? I don't have any. My point is that ASP.NET is not comparable to Wicket. It's like comparing Delphi to Eclipse with a C++ plugin. Both will do the job. The development experience is nowhere similar.
1. Can you drag and drop widgets into a WYSIWYG page designer and set properties in a Wicket plugin?
2. Can you find (free or commercial) the same spectrum of third party components that will also show up in your workbench?
3. Can you visually compose compound components?
4. Does wicket support data binding like ASP.NET as well as have visual tools for the same?
Try click.sourceforge.net. Seriously. No nonsense, just a couple of jar files, no messing around with a hundred xml files, no stupid theories about IoC, Dependency Injection etc.. All pretty simple.