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.
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.
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.
Slashdot Mirror
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.
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
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.