Posted
by
ScuttleMonkey
on Monday November 09, 2009 @03:44PM
from the oracle-grinding-a-fresh-new-roast dept.

An anonymous reader writes to tell us that a recent FAQ released by Oracle outlines the plans for many of Sun's popular products like GlassFish, MySQL, and NetBeans. Many are worried at some of the possible avenues the decisions outlined could lead to, especially with respect to NetBeans. "What should have happened, Oracle should not have missed a beat and should have announced work on Oracle plugins for NetBeans and active Oracle support of NetBeans. This type of announcement would have brought a large and some-what skeptical NetBeans community much closer to Oracle. It would have been a big win for Oracle. NetBeans will continue to grow either way - but Oracle has missed a big chance to really change perceptions and at the same time move their tools to another level. What JDeveloper lacks is buzz, a wealth of community developed plugins, a wealth of support for other languages and a very, very large community. And of course it does not offer a platform in the NetBeans and Eclipse sense of the word. This is a huge missed opportunity for Oracle."

I don't know about the GP, but J2EE is old hat, its been Java EE for while now, and Eclipse has some nice tools for working with Jboss (Red Hat even releases a customized version of Eclipse).
To the parent though, Glassfish is Sun's Java EE baby now and its much better than the former "strict SUN impl".

Really? That's lame. I stated nothing but facts. I used NetBeans in school, I use Eclipse now that I do real projects. And the original point was I didn't realize anyone used NetBeans for real projects. Not that I've been paying attention.

It is not that much slower and the things it does well are pretty important like having a decent JEE Plugin, heavens even after 4 years and 4 releases Eclipses WTP still refuses sometimes to deploy and does not even tell you what is wrong. For heavens sake how hard is it really just to jar something and deploy it?Anyway I have given up on both platforms and am fully on Intellij, it combines the flexibility of Eclipse with the ease of use in Netbeans and adds its own set of excellent tools on top of both pla

I use both. I like Netbeans since 6.x, and I still use eclipse on some legacy projects.

Eclipse is snappier at times, but it reeks of being created by a committee of competitors and a pain in the ass at times to setup for anything more substantial than editing (Subclipse or Subversive as a case in point). However, once you get it working, it works fairly well.

The latest incarnation of Netbeans has more features out of the box and a whole lot easier to install and get to work with your SCM and etc.

I agree. I used Eclipse for years but I've started using Netbeans 6.7 for more and more. The problem we have where I work is that we do PHP projects and Java projects. Six or eight months ago we were having real trouble getting getting PDT to play nice and, so far, NetBeans just works and switching between projects is very easy.

Anyway, they are both great IDE's that continue to get better and better. If I have to switch back to Eclipse is won't be a major sacrifice, but I'll be unhappy that there won't be a free IDE competitor to keep the Eclipse devs motivated:-)

Uuum, you mean that huge slow mess of co-dependent modules and shit, that you have to wade through for weeks to get to anything usable, that is called Eclipse?

Really! as a Java, J2ME, Haskell and web developer, I stopped after two fucking weeks! It's even worse than the Miranda IM! Hell, it's worse than installing Gentoo from Stage 1! And that means something!

Sorry for the hate. But sometimes, hate is deserved.

I'm happy if you are happy with it. And in system administration, I can also be a bit that way.But

I actually went back to a decent text editor. When I went back into the repository I found I wrote more code with the text editor than I did with Ecilpse by shear line count. I also had less bugs. This I completely did not expect at all. I also billed less time to "life cycle" AKA bug fixes. I guess looking back at it now I can attribute it to having less distractions and being required to actually research the interfaces I was using.

Sorry, but IMO you are talking rubbish. We run Eclipse on 32bit P4's and it uses significantly less RAM than that - a typical session doing JEE or PDE work uses 200-300MB, running on Java 6 (on Win2000).

Yeah, NetBeans is not used all that much. Eclipse is used a lot more in the real world where consultants get paid more if they spend longer doing basic project/environment setup and waiting for the UI to come back.

Of course for anyone who wants a quick and feature rich IDE, you can't go past newer versions of NetBeans. I am thankful that more recently I have been in a position to say "I am using NetBeans, even if all you idiots settled on Eclipse" and it has worked out quite well.

You should consider giving it another shot. NetBeans, in my opinion, is by far the best free Java IDE out there right now. As everyone has already pointed out, Eclipse is a plugin nightmare. The NetBeans UI is incredibly polished and while it might be slower at doing some things (e.g. autocompletion), it has a few features that I can't live without.

Check out the "Find Next/Previous Matching Word" keyboard shortcuts. I think it's bound to Ctrl+K and Ctrl+Shift+K by default. I never have to type more than 2 o

I wasn't aware anyone seriously used it. I used it for school and I've been on Eclipse since I started doing real projects.

Apparently, some people use it productively, but I've always found that hard to believe. Some things are just annoying (like nested dialogs that don't show your previous location when you open them again). Other things appear to be more fundamental, like the lack of a single window (or file) listing all (and I mean all) compiler errors and warnings for a project.

I started professionally programming Java about two months ago and hadn't had any experience with it before.

First impression of Eclipse: it's slow, there were display artifacts. It's versioning scheme was clearly designed with pride rather than usability in mind (which is newer, Galileo or Ganymede, and how can you tell?). I could never find the correct Subversion plugin (was I supposed to be using Subclipse or Eclipse Subversion?). Both of them seemed to depend on other plugins which I was supposed to choose between or manually install. Ran into similar issues with Maven integration. The plugin had a clever name and once installed I never really figured out how to make it "go." I only have so much time to spend any given day on configuring my editor. Both coworkers who used Eclipse also helpfully assured me that I'd have to reinstall it every six months or so, because it tends to "go bad" after a while. Not a great sign.

On a whim I downloaded NetBeans. Nobody in my software group was using it, apparently older versions had turned them off completely. Out of the box, it opens Maven projects and the integration is seamless, and it has Subversion and Mercurial integration out of the box. For a new user, the out-of-the-box experience with NetBeans today beats Eclipse hands-down. Especially coming into a professional environment with many moving parts integrated.

The story isn't perfect. NetBeans takes forever and a day to start up. It also can get unresponsive from time to time. You can sink your whole day into configuring it. Plugin integration seems to in general be better than with Eclipse (at least to me) but configuration is a bit worse; everything seems to get thrown under that one tab in the preferences. It tries to manage Tomcat for me but I usually wind up manually force-quitting it (our app probably has a memory leak) because NetBeans' Terminate option doesn't ever seem to do anything. And there have been plenty of confusing issues. Tab completion worked in EL in our JSF facelets, but only inside in a valid XHTML file; figuring that out took an afternoon. I'm still not altogether sure how to get the relationships between multiple projects right.

If I were going to summarize my opinion of NetBeans as a two month user, I'd say: usually it just works but when it doesn't, it's hard to figure out how to fix it. The situation with Eclipse seems to me to be more like, there's a plugin out there that does what you need, good luck figuring out how to get it installed and use it.

Prior to using Java and NetBeans, I mainly did PHP and Ruby plus some other miscellaneous on a Mac with TextMate, Emacs or Coda, depending on the situation. From a usability perspective, Coda in particular but also TextMate are wonderful tools. NetBeans and Eclipse both do some space-age cool stuff but their usability isn't quite up to par. Lots of things are slow that don't seem like they should be, like switching tabs and opening files, and fundamentals tend to be screwy. For example, in NetBeans, if I'm debugging an app and have an SQL window open, there will be three green play icons on my screen. One of them runs the app in not-debug mode, one of them continues from a breakpoint, and one of them runs the SQL command. None of these have particularly memorable shortcuts and their icons are too similar. NetBeans will happily run and deploy the app while I have it at a break point in a debugging session, though the exact intended meaning of that action would be hard to guess.

All in all, if you have a day to throw at it, I recommend giving NetBeans a shot. Two of my three coworkers wound up switching. It also has better Vim integration, if that's relevant to you.

You think he's bad? I went to France once. What a bunch of lazy bastards with all with all their cheesy l' garbage. Perhaps if the socialist bastards would work more than 20 hours a week maybe they'd have time to spell out le and la in full.

You win the General Internet Douchebag Award for Excellence, in the category of Grammar Douchebaggery in a Tech Forum.

Here's your prize... happy now?

(Besides which, my first sentence is a complete sentence. The direct object is the blockquoted text, the subject is "the man who is too lazy...", the verb is "says".) Perhaps some remedial classwork would be of some benefit?

Unfortunately for Netbeans zealots, it has never caught up with Eclipse. It may have surpassed it temporarily for certain apps (think Grails support - but look at STS 2.2.0). It's also not as good as IntelliJ IDEA (previously, always non-free).

Yes, both Netbeans and Eclipse are also RCP platforms, but how many real Netbeans platform apps are there? (The Nokia one on the web site is vapourware - yes it shows a real customer RAN - without their permission, I should add! - but it's never been a product delivered to customers). Real Eclipse RCP apps do exist (XMind, Lotus Smartsuite...). Realistically, they both over good RCP platforms (one pure Java, one SWT) but Oracle won't really care about that.

As for JDeveloper - well it's a typical Oracle product - if you're in an Oracle house, it's pretty good, but no, it's not got a large userbase or community supporting it.

Oracle should let Netbeans drift off into open source land. Perhaps it'll thrive? I don't know. JDeveloper's functionality should be ported to Eclipse (along with SQL Developer, while we're at it).

Oracle are great at giving you tools once you've signed up for the ride, and why not rebase your products on the best? Which in my opinion is Eclipse.

I think that might be part of the reason I don't like Eclipse. I don't get the functionality I want without customizing the crap out of it. That might be useful for some, but not for me. I like power, but I also like convention, so long as it follows the convention I use.

Hmm, as a java development platform (and as a C/C++ development IDE) it is unrivaled by Eclipse. Things seem to work so much smoother in netbeans. You don't have to configure the shit out of it to use it. Most stuff follows the convention over configuration principle. At least that's the way it seems to me
Every time I use eclipse I'm surprised at the exceptional amount of options there are to do something simple. I rarely use them. Most of the options could be done with a couple bits of typing anyway.
As for the RCP stuff, I don't particularly care about that. I think eclipse has the upper hand in that stuff, as that's what it was designed to be in the first place, unlike Netbeans, which was designed to be a Java IDE.

ost stuff follows the convention over configuration principle. At least that's the way it seems to me

I think you may be misinterpreting the "convention over configuration" principle. It is exactly the principle that Eclipse follows.

Convention over configuration means that if you are doing standard stuff, no configuration is required. If you want to do non-standard stuff, you need to configure it. This is why there are so many configuration options in Eclipse. 99.9% of them you don't need unless you are

If 99.9% of the time I don't need to configure Eclipse, how come whenever I try to use it I have to mess with the configuration for an hour or two and even then I'm still fighting with the damn thing to get it to behave in a manner I consider sane? Grandparent knows exactly what he's talking about when he says Eclipse doesn't correctly favor convention over configuration. Time was I thought I hated IDEs and swore by plain text editors. Turns out I just hate Eclipse. The IDE should not be more arcane tha

If by convention you mean always using CVS and having some flashback to the 90's, then yes, Eclipse has a wonderful convention. Setting up svn on Eclipse can be a royal pain in the ass, and don't even dare delve into fancy Maven plugins. Ant builds will always be the one true way. Throw in IBM's nightmarish fleecing of java swing for swt, and little conspiracies will start to flare up in your head. There are some very powerful plugins on Eclipse that Netbeans won't match like BIRT, but there is a painful pa

I agree with you on the point that Eclipse can be complicated, but if there is one thing in Eclipse that really shines its Mylyn and Issue tracking integration. Being able to "switch tasks" and have it remember what you were looking at is pretty awesome, or being able to tag a bug with a Mylyn context, its pretty cool.

Yes, both Netbeans and Eclipse are also RCP platforms, but how many real Netbeans platform apps are there?

Well, with Eclipse, the IDE is pretty good, but the RCP platform -- not so much. It's quite obvious that this thing was designed to write Eclipse (IDE) plugins. For writing standalone applications, the whole approach seems overengineered. OSGI doesn't buy you much in that context, and one doesn't want to turn every small standalone app into a kind of mini-Eclipse, with simple things like command shortcuts and editor selection synchronizations being handled by 5 plugins interacting in complex ways. And then the whole SWT/native-UI-toolkit thing is bound to bite you at some point, e.g. if you're trying to have a table control with varying row heights, for God's sake.

Netbeans isn't there in terms of industry backing and support (which is what we hope Oracle will provide). As far as the software itself is concerned I find it to be at least as good if not better than Eclipse. It's been significantly improved over the last couple of years from version 4.x to 6.x. There are two things that I like it better than Eclipse:- it's 100% Java and runs fine on anything that has a JVM (Eclipse's SWT has platform specific dependencies which prevented me from using it on 64bit machines, it took ages for it to have proper x64 support)- better developer experience because of a cleaner and sensibly chosen set of plug-ins that all work out-of-the-box with no dependency hell (Eclipse plug-ins is a mess unless you pay for commercially packaged versions like MyEclipse)

If you ask me all the IDEs are getting bloated to the point where I think in 2-3 years you're going to need a 64 Bit environment with 8GB or more of RAM just to develop. (Where I am we find Weblogic development using Eclipse is getting slow on 32bit machines with 2GB RAM is getting...difficult) There is some attempt to address this with each IDE by making the platform extensible, and component/plugin based. Unfortunately to do even basic things you end up finding yourself stuck needing a long list of plugin

I think (as a new Java developer) that a big part of Java's success lies in the IDE. We have to put the complexity somewhere. Some languages put it in the library, some into the language itself, and Java definitely puts a lot of it into the IDE. I find it hard to imagine needing or wanting or even being able to provide this kind of experience to a malleable language like Ruby or a terse language like Haskell. But for Java it really makes a big difference to use a bloated IDE.

Unfortunately for Netbeans zealots, it has never caught up with Eclipse.

It depends. In terms of how easy it is to create, say, an UI application, NetBeans is much better out of the box than Eclipse, especially its awesome visual Swing designer. I've also found J2ME development to be more of a breeze in NetBeans compared to Eclipse offerings.

The problem with Eclipse, it seems, is that it overemphasizes extensions to the point that, to do anything useful, you need some mix of extensions. And often there are several extensions available that do the same thing differently, so you have to pick. So it's kinda like Linux - it's pointless to debate it in general, because the specific experience really depends on one's set of extensions used.

NetBeans is much more of a "turnkey" approach - you download the full version, install it, and everything that it can do, is there and working. If you want web or J2EE development, you get the full stack of servers, too. In that, it's much closer to Visual Studio in approach (which may be a good or a bad thing depending on your perspective).

I like Netbeans because it's easy to use. Perhaps Eclipse is useful for super-uber-professional programmers, but I do think Netbeans is the IDE for the rest of us. I like how everything seems to be self-explained and intuitive.

Unfortunately for Netbeans zealots, it has never caught up with Eclipse.

that's an opinion that i'm guessing has either to do with how you use your IDE, or the fact that you haven't used netbeans in a while. i use both. i use netbeans for java / java EE development, and eclipse for android development (since netbeans doesn't have officially blessed android plugin).

leaving out the lack of an official android plugin, netbeans beats eclipse in every way. ease of use, plugins, stability, ease of install, flexibility, standards. the only thing i can say bad about netbeans is that it uses more resources that eclipse...

If Oracle is not interested, other people/companies will carry on the development. In general Sun customers should be applauding the foresight of the company to make pretty much every peace of their hardware and software Open Source and compare their situation to that of Peoplesoft or Siebel customers. Even if everything Sun is killed off tomorrow, it would still be possible to manufacture Sparc-based servers running Solaris and with applications developed using Java and Netbeans.

In reality the only free IDE's that manage to rival Visual Studio (at least to some extent) are those that are backed by big companies: Eclipse (IBM) and Netbeans (Sun). Your average sourceforge IDE project (and there are many) offer no where near the functionality of those two. With lose of the backing by Sun it is very likely that Netbeans will stagnate behind.

...if you want to interact with Oracle products. I tried really hard to use it, even using it as both a Java IDE and a PL/SQL IDE and, while yes, it does work, I found it too slow and clunky to just "bang out some code" when you need to write up a throwaway program really really fast.

But, like I said, if you want total interaction with your database or app server (assuming that app server is oc4j), then I suppose, if you have to use only a single tool, I guess, well, shrug, I guess it's better than nothing...I guess.

MySQL matters. NetBeans, not so much. Most of the web runs on MySQL. There aren't that many good open-source alternatives. (Oracle owns BerkeleyDB, too.)
PostgreSQL is about it, and because that's Berkeley-licensed code, not GPL, it can be forked and the open version abandoned.

Oracle has to dump something. I'm surprised they kept the SPARC line alive. It just doesn't seem to be necessary any more, and it was a money drain for Sun.

Er, why? And from what I understand, the code is GPL'd, right? So they own it kinda in the same way RedHat owns RedHat Linux? (the answer to "why" may be found in educating me just what Oracle owns now, too, hehe...)

Redhat probably have complete ownership of some apps (not sure what their contributor rules are like for say rpm) but most of them they either don't own any of the code in an app at all or they only own some of the code (which doesn't really get you much except the ability to reuse the code they own in other projects). So afaict other than the brand and it's associate reput

SPARC is still quite relevant; there are few things as nice as running a multi-threaded set of applications on the Sun Niagara chips. If I were a database software outfit I would want to make sure there were two architectures out there (IBM POWER and something else) focusing on enterprise performance rather than media creation/encoding.

Take a look. [sun.com] Is there anything in the Intel or AMD product pipeline that will get you 2 x 10 Gb ethernet, 64 thread pipelines, and 128 GB of RAM in a 1U box? Even better, the price is really competative with buying the same performance worth of x86 gear in multiple boxes by the time you think about rack space, cooling networking and all the rest of the data center head aches.

I'm surprised they kept the SPARC line alive. It just doesn't seem to be necessary any more, and it was a money drain for Sun.

Well actually, the most common platform for Oracle deployment is Solaris on SPARC. So it doesn't seem so strange to me that Oracle isn't ditching their most used hardware platform now that they own it.

But, you do realize that something that is BSD licensed can also be forked into a GPL version? Simply keep the BSD license notifications and ALL future additions to the fork are licensed GPL/LGPL, GLPv3 etc. You now have a GPL fork. So, if someone (who by the way?) abandons the BSD licensed version and begins solely working on a proprietary fork, the rest of the community can simply take the last BSD licensed version, create a GPL fork, and lock-out future proprietary forks and prevent the proprietary compa

Oracle has a strong track record of demonstrating commitment to choice for Java developers. As such, NetBeans is expected to provide an additional open source option and complement to the two free tools Oracle already offers for enterprise Java development: Oracle JDeveloper and Oracle Enterprise Pack for Eclipse. While Oracle JDeveloper remains Oracle's strategic development tool for the broad portfolio of Oracle Fusion Middleware products and for Oracle's next generation of enterprise applications, developers will be able to use whichever free tool they are most comfortable with for pure Java and Java EE development: JDeveloper, Enterprise Pack for Eclipse, or NetBeans.

I think that's fairly non-committal, which is what the slashdot summary stated.
Most of the comments state that they're missing out on something by not throwing their full weight behind Netbeans.
Then again, Oracle could just be waiting to see what they're gonna do...

What's non-committal about "NetBeans is expected to provide an additional open source option and complement to the two free tools Oracle already offers for enterprise Java development"

They say the same thing about OpenOffice, They expect netbeans to continue to remain a viable tool. Their history shows that they don't just throw tech out after spending money to buy it. Example: They didn't kill off InnoDB. they said virtually the same thing for OpenOffice

I hate to belabor the obvious here, but Oracle is not terribly concerned with what developers think about them. There are two reasons companies buy Oracle licenses: they either absolutely have to have them, or someone much further up the chain than the developers -- at least in most companies -- thinks that they do. From the altitude in the org chart where those decisions are made, there's no difference between us and the janitors.

Disclaimer - I work for Oracle and came from the BEA Systems acquisition.

My personal opinion is that Oracle is very dedicated to the entire Eclipse ecosystem as well as to JDeveloper. It's about choice. There is an entire free download product that is continually being enhanced called the Oracle Enterprise Pack for Eclipse (Oh-Pee is how we say it within Oracle). In fact I believe it was one of the first, if not the first commercial IDE to support the latest Eclipse 3.5 Galileo.
http://www.oracle.com/technology/products/enterprise-pack-for-eclipse/index.html [oracle.com]
OEPE is targeted for Java and JEE developers and is mostly about supporting the Java standards. Additionally, the majority of the TopLink code was donated as the EclipseLink project and is currently the JPA reference implementation. Just take a look at the presence has at the next Eclipse conference and I think you will see that Oracle is committed to Eclipse.
http://www.eclipse.org/eclipselink/ [eclipse.org]

When you get into the "upper-stack" components like SOA Suite for integration and WebCenter Suite for enterprise portal development, and Oracle's Application Development Framework (ADF) that Oracle strongly recommends JDeveloper. Those products have been based on JDeveloper for a long time and the user-experience developing for those products is extremely smooth because Oracle can influence everything about the IDE. If you want to do Java and JEE development in JDeveloper, you can do that too. It's your choice.

Oracle plans to not only broaden and accelerate its own investment in the Java platform, but also plans to increase the commitment to the community that helps make Java an ubiquitous, innovative platform unified around open standards.

Oracle is internally, as I understand it, an eclipse shop. They always have been. They've got Jbuilder for some specific applications, but for the most part it's eclipse all the way. Sun has tried a number of times to change this, but it's never worked, Oracle just doesn't like NetBeans much. When you combine that with the fact that it's not a hugely popular product(it's a lot more limited and a lot less powerful than eclipse) it's not really a huge shocker they're not going to pour resources into it. They'

Early versions of NetBeans really, really sucked. It has come a long away. But I think it was too long getting there and Eclipse and other IDEs got mindshare and market share. Right now there are virtually zero Oracle customers who are going to defect to someone else because they don't have NetBeans support. There are some that want Eclipse very badly (mostly those that are not pure Oracle shops but use WebSphere too). So it's a no-brainer for them. There's no payback to them supporting 3 IDEs (NetBeans and