Slashdot Mirror
Netbeans 6 Dual-Licensed Under GPLv2, CDDL
Lally Singh writes "Interested in the new Netbeans 6, but didn't trust Sun's (already OSI-approved) CDDL? Sun just Dual-Licensed it under the GPL (v2) with Classpath Exception. Keep your karmic license purity and mix in all the (now compatible) GPL code you want. If you've been using Eclipse, Netbeans 6 is really worth a look. Lean, well-featured, and fast."
If it's your code you can license it however you want, for example MySQL is dual licensed under both the GPL and a Commercial license. Anyone can download the GPL version make their modifications and as long as they follow the GPL redistribute according to the GPl, or if they license the commercial version for a fee from MySQL AB they can basically release a closed source version all closed up.
If you were to dual license your code under the GPL and BSD people who wanted to redistribute modified code could follow either one they wanted, with BSD being one of the avaible choices they could close it up a lot if they so desired.
In your example, the code derived from it has to be compatible with the GPL license OR the BSD license. Once code is licensed under one or the other its usually hard to go back, but one has to make a choice up front about it.
For example I can take some code I write and release it under GPL and my own for pay license. If someone pays for a copy they and I have to abide by my paid-license, if someone downloads it then they can do things with it as allowed by the GPL. This allows me to be flexible and support the needs of buisnesses (and pay my bills) while still supporting the community.
Netbeans is very stable and mature platform. There's nothing to bitch about. Eclipse on the other hand offers much more comfort concerning plain editing and refactoring tasks. Additionally it is part of a much more attractive ecosystem.
Still there is one thing where Netbeans beats every other Java IDE easily: The matisse GUI builder is really fun to work with! For Java there's nothing even close. And for that alone Netbeans has a very well founded raison d'être. If it's GPL now, lets wait and see how long it takes for Eclipse to absorb that great tool. There's already a commercial port for MyEclipse, but it's not free or usable on vanilla Eclipse, yet.
The Netbeans 6 dev/beta releases have been quickly becoming the best Ruby/Rails IDE, bar none. Used to be Eclipse/RadRails for Windows/Linux, and Textmate for Mac. Netbeans has completely blown Eclipse out of the water for Ruby development as Aptana+RadRails has stagnated. Textmate isn't really an IDE to begin with, it's quite a unique and useful text editor. But the pace and quality of Netbeans Ruby support would be very tough to match, so even many hardcore Textmate Mac users have switched to Netbeans
Along with JRuby and Glassfish Rails, Netbeans is proving that Sun is dead serious about being the best Ruby game in town. They've got competitors in all three areas, but they are quickly becoming a major force in the Ruby community
"When text editing is less then instant on a 3ghz machine you know something is very very wrong..."
> runs like I have it on a 486, not a quad core Q6600 Intel processor.
While Netbeans is not winning any performance awards, its performance is quite acceptable. I upgraded my processor only because I was unhappy with Netbeans performance. But mine should still be 3 times slower than a Q6600 and I think the performance is OK now. Perhaps there is something wrong with your VM memory settings or such?
> I don't know how people compare Netbeans to Eclipse, actually feels native (because it IS native) and runs snappy as hell.
The primary reason is that Netbeans has better out of the box support for Java standard frameworks. Swing and J2EE tools are still ahead of Eclipse offerings. If you can, use both. But if you are using a code only app such as your JOGL project, Netbeans does not offer a whole lot.
> Not only that, but Eclipse is great for python, javascript, c/c++ and many, many other non-java technologies.
Netbeans is catching up with all that and exposes a rich client framework just like Eclipse.
Yeah I know it just sucks that Sun gives away millions of man-hours under the GPL but not every single last line of code they ever wrote. I mean who the hell do they think you are by not dedicating every resource they have to the service of free software instead of themselves?
Done with slashdot, done with nerds, getting a life.
As nice as Sun makes it sound, they really aren't fully committed to the GPL. They only seem to use the GPL when it suits them
A company using a license only when it makes sense to do so? How terrible!
If Sun was truly committed to free software, they would use the GPL on everything because in a true free software space it doesn't matter if your customers mix-and-match the pieces
Let's get real here, folks. Making some of your software available as open source does not mean that you should have to make *everything* you create open source. I certainly don't. Some things are open source (all of the ones on my site at the moment are GPLv2 because I loathe the moral crusade the fanatic otherwise known as RMS is trying to get the world to join in with v3); some things are commercial.
I get so sick and tired of the GPL fanboys who think that everything else is evil. The people who own the code get to decide what they want to do with it, not you. Deal with it.
If they want to give it away, be happy that you got something new to use or play with. If they want to sell it, either buy it or don't, but for the love of everything decent, stop bitching about the fact that not everything is released under your favorite license.
I've known a lot of developers that have stopped writing open source software because they got sick and tired of dealing with the fact that no matter what they released, people bitched at them because it wasn't "free enough" or because not *ALL* of their software was open source.
The whole of the world doesn't want to be Stallman followers and, to be honest, I view that as a very very good thing because the man is off his rocker.
Everything I need to know I learned by killing smart people and eating their brains.
Also, if you've been using emacs, vim is worth a look. Vim is lean, well-featured, and fast.
If you are about to mod me down, keep in mind that this post was most likely sarcastic.
You can licence your code however you want, but if you make it conditional like that you could very easily make it incompatible with the licences they're based on, or open up loop holes, or make it not hold up in court or whatever.
The way they do it for MySQL and others is when you get it, only one licence applies. You choose which one you want to apply, but the choice of the commercial licence means you have to give them money. They're just giving you the ability to sell a product and keep the source closed if you're willing to pay for it.
Victory or awesome!
NB's ability to use your normal build system (ant or maven) as it's project file is what sold me. Oh, and I don't have to have this directory structure anymore:
:-)
eclipse
- 3.3
- 1
- 2
- 3
Where each one is an installed copy of eclipse, and the lower numbered ones are copies that have fried themselves.
*And* a decent profiler built in
Care about electronic freedom? Consider donating to the EFF!
Visual Basic (pre .NET) and RealBasic place restrictions on the generated code, because the distribution terms have to be compatible with the distribution terms on the runtime engine that the executables will require.
OTOH, maybe Eclipse is *really* focusing on the Win32 experience, and the Mac experience is just crappy?
It runs fine on both Win32 and Linux, but yes the Mac experience is crappy. Apple likes to brag about their Java support, but the OS X support for the SWT features needed to fully support Eclipse is spotty. Check out how long the infamous SWT_AWT not implemented bug took for them to resolve. That was a showstopper for a variety of Eclipse plug-ins, and it was open from 6/15/2004 to 4/20/2006. Things are better now, but there's still a subset of SWT_AWT not implemented that breaks some tools, like parts of the fairly popular MyEclipse: see SWT_AWT.new_Shell() unimplemented for that dreary mess, which well over a year old now.
While these specific bugs are unlikely to be the sources of your crashes etc., every time I read up on the state of Eclipse+Mac OS X I find myself distrusting that combination; the base platform seems unstable, and as you can see from these two the bugs that are found can sit for years before being fixed. Recent moves from Apple like pulling Java 6 from Leopard aren't comforting either.
Sun's policy?
Sun is a US company and by US law, Sun is not allowed to export to restricted countries.
As said above, you can perfectly do that (within the limits of the law), if it's your code, you get to set the terms. However, such a scenario is not dual-licensing, it's creting a wholly new license (which happens to be based on two other licenses). That very different from dual-licensing where the recieving party get to choose between the licenses. It also is likely very to create a license which is incompatible with both the licenses it is based on.
I don't seem to get why anyone needs to pick one or the other.
Personally, for the last 3 years I've been using Eclipse 3.x and Netbeans 5.x. I can see the benefits of each, and each annoys me in it's own seperate ways.
For example, in Eclipse, why can't I add an external folder to the classpath without stupid variables? Why only a jar? In Netbeans there isn't a distinction.
To me though, Netbeans just feels alot clunkier. Once I have everything set up in Eclipse, I'm definitely more productive, with one caveat. The GUI builder in Netbeans is fantastic, it really is. Nothing free that the Eclipse world offers even comes close to competing with it. I usually do most code in Eclipse, make the GUI in Netbeans and import that into Eclipse.
So I say, why pick one over the other? You need more than one tool to build a house, why not use as many as you like to build your software?
But see, that's what happens when your IDE doesn't include any features, and actually requires plug-ins for some basic tasks. A few years ago, I tried to used Eclipse to do up a quick little Java app with a GUI. Apparently, at the time, you could either hand code your GUI or install some buggy plugin that did the job OK, but not quite that well. Or if you used Netbeans, then the drag-and-drop GUI designer was included as a core part of the IDE. IDEs as far as I'm concerned need a lot of functionality, because of their purpose. If their purpose was just typing code, then we could all just settle for notepad, but those who have used a good IDE know that they are so much more than that. So they should include a lot of features as core components that are well tested and well supported, because relying on third party plugins for things that should be core components leads to a very unstable program.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
I used to do most of my Ruby and Ruby on Rails coding using TextMate but I have switched to using NetBeans. Beta 2 understands Ruby code well enough for (mostly) meaningful code completions and having popup documentation for the standard classes is useful. The integration of the "fast debugger" is also handy. Rails support is also very good. I usually use native (Matz C) Ruby, but NetBeans supports JRuby also. BTW, I used to use Common Lisp, Ruby, and Java about equally in my work, but recently I have been living with the Ruby performance hit and I am starting to use Ruby for just about everything that I do.