NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Charles Ditzel has an interesting blog entry on ths issue. One of the reasons I find it interesting is because he uses content from posters on Javalobby to support most of his arguments. I would be very interested in hearing the comments of the people who wrote the posts that he uses to support his arguments.
So what are some of his reasons why Eclipse users are going to Netbeans? One is the speed issue which has been discussed here. Netbeans has been getting faster since version 3.5, whereas Eclipse seems to keep getting slower. Another reason is that Eclipse does not support platforms other than Windows very well, primarily because of SWT. Ditzel cites one post on Javalobby about how the GTK binding for SWT is so slow, it is practically unusable.
What are your comments? As I said, I am especially interested in hearing the comments of the people who wrote the posts he uses to support his arguments.
The URL to the blog entry is here so that you can see if your posts are among the ones he used:
> Interesting how he only picks up the pro-netbeans
> comments, as if he set out to prove a foregone
> conclusion.
That's one reason I am interested in hearing the comments of the original posters. I want to see if any of them think their posts were taken out of context or anything.
Sorry, but NetBeans doesn't work on Linux for most most people. This is due to Java Bug 4799499 that make it impossible to write certain characters on non US keyboards. What characters depend on your locale you use, but in many cases characters often needed in programming languages is affected.
This same bug is a problem to many other java based development tools. This is one of the reasons why eclipse is so popular in the Linux community.
Re: SWT/Eclipse is open source, Swing/Netbeans is not
Would you like to elaborate on that?
Both Eclipse and Netbeans are open source. Are you suggesting that open source people are less tolerant to bugs?
I would guess that most people regardless if they like open souce or not would be quite annoyed if they had a bug that made it impossible to make full use of their keyboards, and that bug wasn't fixed for FIVE years.
> Another reason is that Eclipse does not support platforms other than Windows very well, primarily because of SWT.
Uh huh. Fire up NetBeans 4.0 on OS X and you get an app with the menu in the window instead of the system menu bar. Click on File->Open and you get a hideous non-standard file dialog. It takes about 5 seconds total to realize that it's yet another unbelievably ugly, utterly non-standard Swing app. Eclipse may be a slow pig, but it actually looks and behaves like an OS X app.
Swing fans just don't get it, and I'm guessing they probably never will.
Granted I am using Eclipse on windows, but it rans fine for me. I would consider Netbeans if it had:
* Quick fix
* Code formatter that wrapped lines over 80 characters. Preferably allowing you to specify the formatting rules
* Warning of unused imports
* Local history
* Type hierarchy
* Call hierarchy
* Incremental compiler
Wait... let me add one for you:
* And was named Netclipse, or Beanclipse, or something-clipse...
:D
For me it's all about the code editor, Eclipse has a code editor that saves me a lot of typing, same goes for IntelliJ (autocomplete-everywhere I like to call it).
> Granted I am using Eclipse on windows, but it rans
> fine for me. I would consider Netbeans if it had:
> * Quick fix
Work on a module for this is started
> * Code formatter that wrapped lines over 80
> characters. Preferably allowing you to specify the
> formatting rules
See the nbdev at netbeans dot org list - a community member has a new version of the jalopy plugin that should show up in CVS and on the update center in a few days
> * Warning of unused imports
PMD plugin for the tasklist is back in business
> * Local history
Don't know quite what you mean - view the undo buffer?
> * Type hierarchy
Choose Inheritance Hierarchy on the combo box in the Navigator window
> * Call hierarchy
Got a demo of this in IDEA the other day, already started, shouldn't be hard.
> * Incremental compiler
Using Ant as *the* build system sort of precludes that, but I think what you want are the *benefits* of an incremental compiler, as opposed to an incremental compiler per-se.
Tim Boudreau NetBeans.org
Evangelist/Senior Staff Engineer, Sun Microsystems
> Eclipse may be
> a slow pig, but it actually looks and behaves like an
> OS X app.
It's slow as a pig which means I am way more productive in Netbeans on Mac than in Eclipse. I really don't care if it looks exactly like a native app. That and Elipse has many bugs in OS X, partly because SWT has many bugs in OS X.
Megga Ditos.
I like most everything about the NetBeans 4.1 environment except the editor. All the J2EE wizards, resource (DBs, Servers, libraries) management, JavaDoc, Ant based projects...the NetBeans people really get it.
And then you launch the Java editor - what a disappointment! This is the only reason I switched back to Eclipse...well, that and the meager refactoring support.
The editor's auto-completion and 'intellisence' are slow.
The code formatting options are severely limited compared to eclipse (which lets you customize your code style out the wazoo).
The editor also takes ~ 10-15 sec. to pick up syntax errors; removing the 'red sqiggly' lines after errors are corrected can take almost as long. In eclipse, this is all instantaneous due to the incremental compiling and continuous AST parsing stuff.
I've tried IDEA also. Its editor puts both Eclipse and NetBeans to shame.
Why Eclipse Users are Moving to Netbeans
At 7:35 PM on Mar 15, 2005, Michael Urban wrote:
Fresh Jobs for Developers Post a job opportunity
Charles Ditzel has an interesting blog entry on ths issue. One of the reasons I find it interesting is because he uses content from posters on Javalobby to support most of his arguments. I would be very interested in hearing the comments of the people who wrote the posts that he uses to support his arguments.
So what are some of his reasons why Eclipse users are going to Netbeans? One is the speed issue which has been discussed here. Netbeans has been getting faster since version 3.5, whereas Eclipse seems to keep getting slower. Another reason is that Eclipse does not support platforms other than Windows very well, primarily because of SWT. Ditzel cites one post on Javalobby about how the GTK binding for SWT is so slow, it is practically unusable.
What are your comments? As I said, I am especially interested in hearing the comments of the people who wrote the posts he uses to support his arguments.
The URL to the blog entry is here so that you can see if your posts are among the ones he used:
http://cld.blog-city.com/read/1126337.htm
112 replies so far (
Post your own)
Re: Why Eclipse Users are Moving to Netbeans
Interesting how he only picks up the pro-netbeans comments, as if he set out to prove a foregone conclusion.Re: Why Eclipse Users are Moving to Netbeans
> Interesting how he only picks up the pro-netbeans> comments, as if he set out to prove a foregone
> conclusion.
That's one reason I am interested in hearing the comments of the original posters. I want to see if any of them think their posts were taken out of context or anything.
Re: Why Eclipse Users are Moving to Netbeans
Sorry, but NetBeans doesn't work on Linux for most most people. This is due to Java Bug 4799499 that make it impossible to write certain characters on non US keyboards. What characters depend on your locale you use, but in many cases characters often needed in programming languages is affected.This same bug is a problem to many other java based development tools. This is one of the reasons why eclipse is so popular in the Linux community.
SWT/Eclipse is open source, Swing/Netbeans is not
That sums up the Linux community pretty well, I think.Re: SWT/Eclipse is open source, Swing/Netbeans is not
Would you like to elaborate on that?Both Eclipse and Netbeans are open source. Are you suggesting that open source people are less tolerant to bugs?
I would guess that most people regardless if they like open souce or not would be quite annoyed if they had a bug that made it impossible to make full use of their keyboards, and that bug wasn't fixed for FIVE years.
This is the case with java swing on Linux.
Re: Why Eclipse Users are Moving to Netbeans
> Another reason is that Eclipse does not support platforms other than Windows very well, primarily because of SWT.Uh huh. Fire up NetBeans 4.0 on OS X and you get an app with the menu in the window instead of the system menu bar. Click on File->Open and you get a hideous non-standard file dialog. It takes about 5 seconds total to realize that it's yet another unbelievably ugly, utterly non-standard Swing app. Eclipse may be a slow pig, but it actually looks and behaves like an OS X app.
Swing fans just don't get it, and I'm guessing they probably never will.
Re: Why Eclipse Users are Moving to Netbeans
Granted I am using Eclipse on windows, but it rans fine for me. I would consider Netbeans if it had:* Quick fix
* Code formatter that wrapped lines over 80 characters. Preferably allowing you to specify the formatting rules
* Warning of unused imports
* Local history
* Type hierarchy
* Call hierarchy
* Incremental compiler
Re: Why Eclipse Users are Moving to Netbeans
Wait... let me add one for you:* And was named Netclipse, or Beanclipse, or something-clipse...
:D
For me it's all about the code editor, Eclipse has a code editor that saves me a lot of typing, same goes for IntelliJ (autocomplete-everywhere I like to call it).
Re: Why Eclipse Users are Moving to Netbeans
> Granted I am using Eclipse on windows, but it rans> fine for me. I would consider Netbeans if it had:
> * Quick fix
Work on a module for this is started
> * Code formatter that wrapped lines over 80
> characters. Preferably allowing you to specify the
> formatting rules
See the nbdev at netbeans dot org list - a community member has a new version of the jalopy plugin that should show up in CVS and on the update center in a few days
> * Warning of unused imports
PMD plugin for the tasklist is back in business
> * Local history
Don't know quite what you mean - view the undo buffer?
> * Type hierarchy
Choose Inheritance Hierarchy on the combo box in the Navigator window
> * Call hierarchy
Got a demo of this in IDEA the other day, already started, shouldn't be hard.
> * Incremental compiler
Using Ant as *the* build system sort of precludes that, but I think what you want are the *benefits* of an incremental compiler, as opposed to an incremental compiler per-se.
NetBeans.org
Evangelist/Senior Staff Engineer, Sun Microsystems
Re: SWT/Eclipse is open source, Swing/Netbeans is not
Swing is not open source, therefore Netbeans is not totally open source because it has proprietary dependencies.Eclipse == Open Source
SWT != Open Source
Re: Why Eclipse Users are Moving to Netbeans
> Eclipse may be> a slow pig, but it actually looks and behaves like an
> OS X app.
It's slow as a pig which means I am way more productive in Netbeans on Mac than in Eclipse. I really don't care if it looks exactly like a native app. That and Elipse has many bugs in OS X, partly because SWT has many bugs in OS X.
Re: SWT/Eclipse is open source, Swing/Netbeans is not
But both Netbeans and Eclipse depends on a java runtime, that usually is not open source.Re: SWT/Eclipse is open source, Swing/Netbeans is not
Eclipse can be compiled with GCJ or used with GNU's JIT.Re: Why Eclipse Users are Moving to Netbeans
Megga Ditos.I like most everything about the NetBeans 4.1 environment except the editor. All the J2EE wizards, resource (DBs, Servers, libraries) management, JavaDoc, Ant based projects...the NetBeans people really get it.
And then you launch the Java editor - what a disappointment! This is the only reason I switched back to Eclipse...well, that and the meager refactoring support.
The editor's auto-completion and 'intellisence' are slow.
The code formatting options are severely limited compared to eclipse (which lets you customize your code style out the wazoo).
The editor also takes ~ 10-15 sec. to pick up syntax errors; removing the 'red sqiggly' lines after errors are corrected can take almost as long. In eclipse, this is all instantaneous due to the incremental compiling and continuous AST parsing stuff.
I've tried IDEA also. Its editor puts both Eclipse and NetBeans to shame.