Eclipse vs NetBeans

Eclipse vs NetBeans …On which side are you on? Let us know which IDE you think is better and why.

Think of Java IDEs and two names that will come up are Eclipse and NetBeans. I have been using NetBeans for many years now and Eclipse has been a more recent addition to my Java armory. I have enjoyed working with both tools and as such don’t have a clear favorite. I prefer NetBeans a little more than Eclipse as I have been using it longer and am more comfortable with it.

The thing I am most surprised about is how rapidly Eclipse has grown and how it has well and truly eclipsed NetBeans over the past year or so.

In the article: Migrating to Eclipse: A developer’s guide to evaluating Eclipse vs. Netbeans, the author shows the differences between the two IDEs.

Just Eclipse or Eclipse in its WSAD avatar or MyEclipseIDE avatar is definitely good but hey..is it so good that nobody wants to be talk of NetBeans these days??? I haven’t as yet tried out the new NetBeans 4 Beta 2 but I do hope it is very good. So that the competition between Eclipse and NetBeans stays fierce and there is no clear winner.

The end user gets two very good IDEs.

* Apr08 Update – Do have a look at this new comparison of JDeveloper, Eclipse and NetBeans

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!

258 thoughts on “Eclipse vs NetBeans

  • December 3, 2005 at 11:31 pm
    Permalink

    Netbeans is very good. But this does not matter. Remember the war OS/2
    against Windows. OS/2 was better and who has won? What really matters
    is what the big software companies opt for. They opt for Eclipse.

  • November 29, 2005 at 3:45 am
    Permalink

    I have to admit that eclipse does better refactoring than netbeans does. But netbeans is catching up with eclipse in refactoring. Perhaps nebeans is not so rich in refactoring as eclipse. But those existed satisfied most of our common needs.

    I am not a native English speaker. That’s why I failed to make me understood clearly.

    >It is just because NetBeans implemented these features a little later that it >can learn from eclipse and do even better than eclipse.

    >>well, there you go. You are saying Netbeans is behind Eclipse. Components in Eclipse evolve, and are refined in each successive release.

    >>>NetBeans is not behind Eclipse. In fact, the so-called plugin-platform model existed earlier in netbeans than eclipse. NetBeans did learn some tricks from eclipse. But so did eclipse too. They learned from each other. As to these features(eg. refactoring), NetBeans is a little behind eclipse. But that’s not all the story. NetBeans also has some features ahead of eclispe. JDK 1.5 language specification support is one of them.

    >Eclipse using round-tripping to synchrnoize gui forms and codes, which, >as I know, is damn slooooow! It is really stupid to synchronize forms and >codes from time to time! CPU, memory and other computer resources are >completely wasted!

    >>Netbeans form files breaks so many programming design rules, I don’t know where to begin. If I want to change anything – like change the name of a component in my code, forms will freak out because it is POORLY DESIGNED, and quite often the forms file will magically blank itself. And it is so selfishly designed that only Netbeans developers can modify and Swing code. PS – get a faster computer

    Flexibility is deleterious to productivity. ASM is so flexible that you can even program to a single port I/O. But can you develop a morden software with ASM. Though form-file solution does destroy the flexibility, it helps to make the codes neat and clean, reduces the probable errors, and what’s more enhances productivity. As I know, many GUI designers are using xml-form files to help generate the codes.
    By the way, NetBeans does give you the freedom of customizing. But the flexibility is relatively limited. You can enter you customized code (before and after initializing the components) in the property panel.
    Of course, you can also modify the code by other IDE, except that you follow some rules.
    My computer’s CPU is of 1.8G, 256M memory. It runs pretty fast, faster than eclipse 3.1 with the same project size.
    >’Netbeans is faster : Are you kidding me?? ‘
    >Hey, baby, I am not kidding you. I have also used eclipse for more than 3 >years. Don’t you think I am just guessing! Even on Windows, eclipse is >only slightly superior on UI response!

    >>Errm… So you are saying Eclipse is faster? ok then.

    Fastness not only means GUI responsiveness, but also some other facts. For example, compilation, debug and etc. SWT due to its optimization on Windows, it should be faster than swing. But I cannot say this is true on other platforms. On unix-like OS and Mac, SWT can even not compete with swing, not only for its compatibility, but also for its speed. There are already many articles and debates among SWT and swing. SWT perfoms worse and worse in the competition with swing.
    As to GUI responsiveness, I should say they 50 to 50. But except this, NetBeans is definitly faster than eclipse. That’s my real meaning.
    As to memory comsuption, the two are also 50 to 50.
    >’Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    >Only because you don’t know how tune it.
    >Of course, maybe you have a different idea about what is beautiful.
    >’The icons are big and clucky’
    >You can change them to small icons. You have already got used to >eclipse icons. That’s why you think netbeans’ are ugly.

    >>Dude…. what do you know about why I think Netbeans is ugly??? When I switched from JBuilder to Eclipse I was instantly impressed by the economy of scale, colours and real estate organisation of the application. It had a comfortable responsive GUI that looked great.

    It is undeniable that eclipse does a good job in user interfaces. The icons, the layout, the menu designs and the perspective conceptions. But NetBeans also has its advantages. It outperforms eclipse on space usages. The auto-hiding feature of the navigation view is a good idea. Its icons and flash screens and menu designs are catching up. I believe there’s another factor, you have got used to eclipse interface style, that makes you favor eclipse’s user interface. What if you get used to NetBeans?
    As my experience with NetBeans, NetBeans surely can be tuned just as beautiful as eclipse. You’ll see to what extent it can be tuned if I can post snapshot here.

    >You have a long way to learn netbeans if you want to feel its grandness!

    >>Which is precisely the reason you mentioned that makes Eclipse so bad.

    A long way is not that long as eclipse. It is definitely much shorter than eclipse. NetBeans has better localized help documents to read. What about eclipse. I am not native English speaker. It is really hard for me to learn even a very small new trick in eclipse.

    >’Creating a project in Eclipse is hassle : I find this the easiest thing about >Eclipse. ‘
    >Another evidence that you have worked on eclipe for too long!

    >>see above comment.

    See the above comment.

    >’Netbeans also doesn’t have auto compile’
    >Auto compilation is trade-off. I don’t think it is good way.

    >>Auto-compile is one of the best things about Eclipse. Having class files completely transparent means that I can ignore that they even exist. Everything is kept in synch just the way it should – there is none of the weird class files being out of synch problems which i have had to endure with JBuilder.

    Auto-compilation did cost a lot of time to wait. I was keeping thinking why not make the feature configurable so that I could turn it off!

    >Eclipse has many, which require you to buy them, which have poor >compatabilites, which can even not work well with the platform! Though >NetBeans has relatively fewer plugins than eclipse. But their qualities are >high.

    >>So are you saying every single plugin is for free for Netbeans? Many plugins exist for eclipse that are free including Visual Editor…. which is better than Matisse, and most you can evaluate for a month and then pay a measly $100 or so.

    Currently, I don’t if all the NetBeans’ plugins are free. But most of them are free and of product quality.
    I also have ever experienced Visual Editor. Frankly speaking, it is probably the best GUI designer IF Mattise DID NOT EXIST. I don’t know whether you have experienced Mattise. It surely deserves applause. Its intuitive designing way is just fantastic as Delphi and VB. And it’s totally free.

    >They fit together much better. They can provide you almost any kinds of >development. That’s enough. Do you want to spend a lot of time just in >order to learn how play around an IDE?

    >>Yes I do want to spend a lot of time to learn how to play around with Netbeans to ‘discover its grandness’

    Have you ever heard that NetBeans is harder to learn than Eclipse? Search on the net.

    >What we need is productivity! Not >flowerish, useless, meaningless tricks.

    >>If you call refactoring a meaningless trick you should go back to prgramming Cobol 101. Programming has long gone from waterfall models, and in todays environment of highly iterative developement, you need to use Agile methodologies and refactor rigourously. I can’t think of anything that is flowery in Eclipse – it has EXCELLENT usability of its GUI which has increased my productivity by around 50%.

    By saying playing around IDE, I don’t refer to refactoring. I also agree with you on refactoring is great tools. What I mean is the process that you build up a complete development enviroments. Can you compare that of eclipse with NetBeans? It’s dreadful nightmare!
    You promoted your productivity 50%. I think you are comparing to write you code using notepad. I think I can boost my productivity using any IDE. The quesiton is how to compare and what to compare to.

    >>Netbeans is good, but not THAT good. I’m all for supporting the underdog in the IDE wars, but I have to rigourously defend some of the idiotic false accusations levelled at Eclipse in this forum.
    NetBeans is not THAT good. I agree. BUT DON’T TURN YOUR HEAD FROM IT AND SNEER AT IT NAIVELY.

  • November 29, 2005 at 3:45 am
    Permalink

    I have to admit that eclipse does better refactoring than netbeans does. But netbeans is catching up with eclipse in refactoring. Perhaps nebeans is not so rich in refactoring as eclipse. But those existed satisfied most of our common needs.

    I am not a native English speaker. That’s why I failed to make me understood clearly.

    >It is just because NetBeans implemented these features a little later that it >can learn from eclipse and do even better than eclipse.

    >>well, there you go. You are saying Netbeans is behind Eclipse. Components in Eclipse evolve, and are refined in each successive release.

    >>>NetBeans is not behind Eclipse. In fact, the so-called plugin-platform model existed earlier in netbeans than eclipse. NetBeans did learn some tricks from eclipse. But so did eclipse too. They learned from each other. As to these features(eg. refactoring), NetBeans is a little behind eclipse. But that’s not all the story. NetBeans also has some features ahead of eclispe. JDK 1.5 language specification support is one of them.

    >Eclipse using round-tripping to synchrnoize gui forms and codes, which, >as I know, is damn slooooow! It is really stupid to synchronize forms and >codes from time to time! CPU, memory and other computer resources are >completely wasted!

    >>Netbeans form files breaks so many programming design rules, I don’t know where to begin. If I want to change anything – like change the name of a component in my code, forms will freak out because it is POORLY DESIGNED, and quite often the forms file will magically blank itself. And it is so selfishly designed that only Netbeans developers can modify and Swing code. PS – get a faster computer

    Flexibility is deleterious to productivity. ASM is so flexible that you can even program to a single port I/O. But can you develop a morden software with ASM. Though form-file solution does destroy the flexibility, it helps to make the codes neat and clean, reduces the probable errors, and what’s more enhances productivity. As I know, many GUI designers are using xml-form files to help generate the codes.
    By the way, NetBeans does give you the freedom of customizing. But the flexibility is relatively limited. You can enter you customized code (before and after initializing the components) in the property panel.
    Of course, you can also modify the code by other IDE, except that you follow some rules.
    My computer’s CPU is of 1.8G, 256M memory. It runs pretty fast, faster than eclipse 3.1 with the same project size.
    >’Netbeans is faster : Are you kidding me?? ‘
    >Hey, baby, I am not kidding you. I have also used eclipse for more than 3 >years. Don’t you think I am just guessing! Even on Windows, eclipse is >only slightly superior on UI response!

    >>Errm… So you are saying Eclipse is faster? ok then.

    Fastness not only means GUI responsiveness, but also some other facts. For example, compilation, debug and etc. SWT due to its optimization on Windows, it should be faster than swing. But I cannot say this is true on other platforms. On unix-like OS and Mac, SWT can even not compete with swing, not only for its compatibility, but also for its speed. There are already many articles and debates among SWT and swing. SWT perfoms worse and worse in the competition with swing.
    As to GUI responsiveness, I should say they 50 to 50. But except this, NetBeans is definitly faster than eclipse. That’s my real meaning.
    As to memory comsuption, the two are also 50 to 50.
    >’Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    >Only because you don’t know how tune it.
    >Of course, maybe you have a different idea about what is beautiful.
    >’The icons are big and clucky’
    >You can change them to small icons. You have already got used to >eclipse icons. That’s why you think netbeans’ are ugly.

    >>Dude…. what do you know about why I think Netbeans is ugly??? When I switched from JBuilder to Eclipse I was instantly impressed by the economy of scale, colours and real estate organisation of the application. It had a comfortable responsive GUI that looked great.

    It is undeniable that eclipse does a good job in user interfaces. The icons, the layout, the menu designs and the perspective conceptions. But NetBeans also has its advantages. It outperforms eclipse on space usages. The auto-hiding feature of the navigation view is a good idea. Its icons and flash screens and menu designs are catching up. I believe there’s another factor, you have got used to eclipse interface style, that makes you favor eclipse’s user interface. What if you get used to NetBeans?
    As my experience with NetBeans, NetBeans surely can be tuned just as beautiful as eclipse. You’ll see to what extent it can be tuned if I can post snapshot here.

    >You have a long way to learn netbeans if you want to feel its grandness!

    >>Which is precisely the reason you mentioned that makes Eclipse so bad.

    A long way is not that long as eclipse. It is definitely much shorter than eclipse. NetBeans has better localized help documents to read. What about eclipse. I am not native English speaker. It is really hard for me to learn even a very small new trick in eclipse.

    >’Creating a project in Eclipse is hassle : I find this the easiest thing about >Eclipse. ‘
    >Another evidence that you have worked on eclipe for too long!

    >>see above comment.

    See the above comment.

    >’Netbeans also doesn’t have auto compile’
    >Auto compilation is trade-off. I don’t think it is good way.

    >>Auto-compile is one of the best things about Eclipse. Having class files completely transparent means that I can ignore that they even exist. Everything is kept in synch just the way it should – there is none of the weird class files being out of synch problems which i have had to endure with JBuilder.

    Auto-compilation did cost a lot of time to wait. I was keeping thinking why not make the feature configurable so that I could turn it off!

    >Eclipse has many, which require you to buy them, which have poor >compatabilites, which can even not work well with the platform! Though >NetBeans has relatively fewer plugins than eclipse. But their qualities are >high.

    >>So are you saying every single plugin is for free for Netbeans? Many plugins exist for eclipse that are free including Visual Editor…. which is better than Matisse, and most you can evaluate for a month and then pay a measly $100 or so.

    Currently, I don’t if all the NetBeans’ plugins are free. But most of them are free and of product quality.
    I also have ever experienced Visual Editor. Frankly speaking, it is probably the best GUI designer IF Mattise DID NOT EXIST. I don’t know whether you have experienced Mattise. It surely deserves applause. Its intuitive designing way is just fantastic as Delphi and VB. And it’s totally free.

    >They fit together much better. They can provide you almost any kinds of >development. That’s enough. Do you want to spend a lot of time just in >order to learn how play around an IDE?

    >>Yes I do want to spend a lot of time to learn how to play around with Netbeans to ‘discover its grandness’

    Have you ever heard that NetBeans is harder to learn than Eclipse? Search on the net.

    >What we need is productivity! Not >flowerish, useless, meaningless tricks.

    >>If you call refactoring a meaningless trick you should go back to prgramming Cobol 101. Programming has long gone from waterfall models, and in todays environment of highly iterative developement, you need to use Agile methodologies and refactor rigourously. I can’t think of anything that is flowery in Eclipse – it has EXCELLENT usability of its GUI which has increased my productivity by around 50%.

    By saying playing around IDE, I don’t refer to refactoring. I also agree with you on refactoring is great tools. What I mean is the process that you build up a complete development enviroments. Can you compare that of eclipse with NetBeans? It’s dreadful nightmare!
    You promoted your productivity 50%. I think you are comparing to write you code using notepad. I think I can boost my productivity using any IDE. The quesiton is how to compare and what to compare to.

    >>Netbeans is good, but not THAT good. I’m all for supporting the underdog in the IDE wars, but I have to rigourously defend some of the idiotic false accusations levelled at Eclipse in this forum.
    NetBeans is not THAT good. I agree. BUT DON’T TURN YOUR HEAD FROM IT AND SNEER AT IT NAIVELY.

  • November 28, 2005 at 1:09 pm
    Permalink

    I have to respond :

    >It is just because NetBeans implemented these features a little later that it >can learn from eclipse and do even better than eclipse.

    well, there you go. You are saying Netbeans is behind Eclipse. Components in Eclipse evolve, and are refined in each successive release.

    >Eclipse using round-tripping to synchrnoize gui forms and codes, which, >as I know, is damn slooooow! It is really stupid to synchronize forms and >codes from time to time! CPU, memory and other computer resources are >completely wasted!

    Netbeans form files breaks so many programming design rules, I don’t know where to begin. If I want to change anything – like change the name of a component in my code, forms will freak out because it is POORLY DESIGNED, and quite often the forms file will magically blank itself. And it is so selfishly designed that only Netbeans developers can modify and Swing code. PS – get a faster computer

    >’Netbeans is faster : Are you kidding me?? ‘
    >Hey, baby, I am not kidding you. I have also used eclipse for more than 3 >years. Don’t you think I am just guessing! Even on Windows, eclipse is >only slightly superior on UI response!

    Errm… So you are saying Eclipse is faster? ok then.

    >’Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    >Only because you don’t know how tune it.
    >Of course, maybe you have a different idea about what is beautiful.
    >’The icons are big and clucky’
    >You can change them to small icons. You have already got used to >eclipse icons. That’s why you think netbeans’ are ugly.

    Dude…. what do you know about why I think Netbeans is ugly??? When I switched from JBuilder to Eclipse I was instantly impressed by the economy of scale, colours and real estate organisation of the application. It had a comfortable responsive GUI that looked great.

    >You have a long way to learn netbeans if you want to feel its grandness!

    Which is precisely the reason you mentioned that makes Eclipse so bad.

    >’Creating a project in Eclipse is hassle : I find this the easiest thing about >Eclipse. ‘
    >Another evidence that you have worked on eclipe for too long!

    see above comment.

    >’Netbeans also doesn’t have auto compile’
    >Auto compilation is trade-off. I don’t think it is good way.

    Auto-compile is one of the best things about Eclipse. Having class files completely transparent means that I can ignore that they even exist. Everything is kept in synch just the way it should – there is none of the weird class files being out of synch problems which i have had to endure with JBuilder.

    >Eclipse has many, which require you to buy them, which have poor >compatabilites, which can even not work well with the platform! Though >NetBeans has relatively fewer plugins than eclipse. But their qualities are >high.

    So are you saying every single plugin is for free for Netbeans? Many plugins exist for eclipse that are free including Visual Editor…. which is better than Matisse, and most you can evaluate for a month and then pay a measly $100 or so.

    >They fit together much better. They can provide you almost any kinds of >development. That’s enough. Do you want to spend a lot of time just in >order to learn how play around an IDE?

    Yes I do want to spend a lot of time to learn how to play around with Netbeans to ‘discover its grandness’

    >What we need is productivity! Not >flowerish, useless, meaningless tricks.

    If you call refactoring a meaningless trick you should go back to prgramming Cobol 101. Programming has long gone from waterfall models, and in todays environment of highly iterative developement, you need to use Agile methodologies and refactor rigourously. I can’t think of anything that is flowery in Eclipse – it has EXCELLENT usability of its GUI which has increased my productivity by around 50%.

    Netbeans is good, but not THAT good. I’m all for supporting the underdog in the IDE wars, but I have to rigourously defend some of the idiotic false accusations levelled at Eclipse in this forum.

    ¬O.

  • November 28, 2005 at 1:09 pm
    Permalink

    I have to respond :

    >It is just because NetBeans implemented these features a little later that it >can learn from eclipse and do even better than eclipse.

    well, there you go. You are saying Netbeans is behind Eclipse. Components in Eclipse evolve, and are refined in each successive release.

    >Eclipse using round-tripping to synchrnoize gui forms and codes, which, >as I know, is damn slooooow! It is really stupid to synchronize forms and >codes from time to time! CPU, memory and other computer resources are >completely wasted!

    Netbeans form files breaks so many programming design rules, I don’t know where to begin. If I want to change anything – like change the name of a component in my code, forms will freak out because it is POORLY DESIGNED, and quite often the forms file will magically blank itself. And it is so selfishly designed that only Netbeans developers can modify and Swing code. PS – get a faster computer

    >’Netbeans is faster : Are you kidding me?? ‘
    >Hey, baby, I am not kidding you. I have also used eclipse for more than 3 >years. Don’t you think I am just guessing! Even on Windows, eclipse is >only slightly superior on UI response!

    Errm… So you are saying Eclipse is faster? ok then.

    >’Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    >Only because you don’t know how tune it.
    >Of course, maybe you have a different idea about what is beautiful.
    >’The icons are big and clucky’
    >You can change them to small icons. You have already got used to >eclipse icons. That’s why you think netbeans’ are ugly.

    Dude…. what do you know about why I think Netbeans is ugly??? When I switched from JBuilder to Eclipse I was instantly impressed by the economy of scale, colours and real estate organisation of the application. It had a comfortable responsive GUI that looked great.

    >You have a long way to learn netbeans if you want to feel its grandness!

    Which is precisely the reason you mentioned that makes Eclipse so bad.

    >’Creating a project in Eclipse is hassle : I find this the easiest thing about >Eclipse. ‘
    >Another evidence that you have worked on eclipe for too long!

    see above comment.

    >’Netbeans also doesn’t have auto compile’
    >Auto compilation is trade-off. I don’t think it is good way.

    Auto-compile is one of the best things about Eclipse. Having class files completely transparent means that I can ignore that they even exist. Everything is kept in synch just the way it should – there is none of the weird class files being out of synch problems which i have had to endure with JBuilder.

    >Eclipse has many, which require you to buy them, which have poor >compatabilites, which can even not work well with the platform! Though >NetBeans has relatively fewer plugins than eclipse. But their qualities are >high.

    So are you saying every single plugin is for free for Netbeans? Many plugins exist for eclipse that are free including Visual Editor…. which is better than Matisse, and most you can evaluate for a month and then pay a measly $100 or so.

    >They fit together much better. They can provide you almost any kinds of >development. That’s enough. Do you want to spend a lot of time just in >order to learn how play around an IDE?

    Yes I do want to spend a lot of time to learn how to play around with Netbeans to ‘discover its grandness’

    >What we need is productivity! Not >flowerish, useless, meaningless tricks.

    If you call refactoring a meaningless trick you should go back to prgramming Cobol 101. Programming has long gone from waterfall models, and in todays environment of highly iterative developement, you need to use Agile methodologies and refactor rigourously. I can’t think of anything that is flowery in Eclipse – it has EXCELLENT usability of its GUI which has increased my productivity by around 50%.

    Netbeans is good, but not THAT good. I’m all for supporting the underdog in the IDE wars, but I have to rigourously defend some of the idiotic false accusations levelled at Eclipse in this forum.

    ¬O.

  • November 27, 2005 at 10:24 am
    Permalink

    ‘Netbeans is still behind the times in implementing features that Eclipse has had for years (eg. flat file package view), and is still behind in the refactoring department. ‘
    Comment: It is just because NetBeans implemented these features a little later that it can learn from eclipse and do even better than eclipse. You know little about NetBeans. How can you boast for eclipse that its refactoring is better than NetBeans?

    ‘The fundamental problem is that Netbeans generates these attrocious form files which (a) make all the Swing classes completely vendor locked (b) make it near impossible doing the most minor refactoring.’ I don’t think a developer often needs to rename a compnent’s name. You can rename its name easily from the property page.
    ‘If I want to change the name of my ‘button1′, why can’t I just refactor in the code?’
    I do think to refactor a variable is more troublesome than to enter a single string in the property panel!
    ‘Eclipse on the other hand has GUI builders which in my opinion are as good as Matisse and DO support round-tripping, DO support refactoring,’
    Eclipse using round-tripping to synchrnoize gui forms and codes, which, as I know, is damn slooooow! It is really stupid to synchronize forms and codes from time to time! CPU, memory and other computer resources are completely wasted!
    ‘Netbeans is faster : Are you kidding me?? ‘
    Hey, baby, I am not kidding you. I have also used eclipse for more than 3 years. Don’t you think I am just guessing! Even on Windows, eclipse is only slightly superior on UI response!

    ‘Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    Only because you don’t know how tune it.
    Of course, maybe you have a different idea about what is beautiful.
    ‘The icons are big and clucky’
    You can change them to small icons. You have already got used to eclipse icons. That’s why you think netbeans’ are ugly.
    ‘and give it that nerdy feel of someone spending their Friday nights in front of Linux. ‘
    You are suely not familar with netbeans. It uses java se 1.5 look & feel, which makes netbeans just as native program. You have a long way to learn netbeans if you want to feel its grandness!

    ‘Creating a project in Eclipse is hassle : I find this the easiest thing about Eclipse. ‘
    Another evidence that you have worked on eclipe for too long!

    ‘Netbeans also doesn’t have auto compile’
    Auto compilation is trade-off. I don’t think it is good way.
    ‘ has poor plugins, etc.’
    Eclipse has many, which require you to buy them, which have poor compatabilites, which can even not work well with the platform! Though NetBeans has relatively fewer plugins than eclipse. But their qualities are high. They fit together much better. They can provide you almost any kinds of development. That’s enough. Do you want to spend a lot of time just in order to learn how play around an IDE? What we need is productivity! Not flowerish, useless, meaningless tricks.
    ‘There is a reason why Eclipse is #1. ‘
    #1, #2 does not stand for any thing. We programmers care only about which is really better, which is catching up!

  • November 27, 2005 at 10:24 am
    Permalink

    ‘Netbeans is still behind the times in implementing features that Eclipse has had for years (eg. flat file package view), and is still behind in the refactoring department. ‘
    Comment: It is just because NetBeans implemented these features a little later that it can learn from eclipse and do even better than eclipse. You know little about NetBeans. How can you boast for eclipse that its refactoring is better than NetBeans?

    ‘The fundamental problem is that Netbeans generates these attrocious form files which (a) make all the Swing classes completely vendor locked (b) make it near impossible doing the most minor refactoring.’ I don’t think a developer often needs to rename a compnent’s name. You can rename its name easily from the property page.
    ‘If I want to change the name of my ‘button1′, why can’t I just refactor in the code?’
    I do think to refactor a variable is more troublesome than to enter a single string in the property panel!
    ‘Eclipse on the other hand has GUI builders which in my opinion are as good as Matisse and DO support round-tripping, DO support refactoring,’
    Eclipse using round-tripping to synchrnoize gui forms and codes, which, as I know, is damn slooooow! It is really stupid to synchronize forms and codes from time to time! CPU, memory and other computer resources are completely wasted!
    ‘Netbeans is faster : Are you kidding me?? ‘
    Hey, baby, I am not kidding you. I have also used eclipse for more than 3 years. Don’t you think I am just guessing! Even on Windows, eclipse is only slightly superior on UI response!

    ‘Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    Only because you don’t know how tune it.
    Of course, maybe you have a different idea about what is beautiful.
    ‘The icons are big and clucky’
    You can change them to small icons. You have already got used to eclipse icons. That’s why you think netbeans’ are ugly.
    ‘and give it that nerdy feel of someone spending their Friday nights in front of Linux. ‘
    You are suely not familar with netbeans. It uses java se 1.5 look & feel, which makes netbeans just as native program. You have a long way to learn netbeans if you want to feel its grandness!

    ‘Creating a project in Eclipse is hassle : I find this the easiest thing about Eclipse. ‘
    Another evidence that you have worked on eclipe for too long!

    ‘Netbeans also doesn’t have auto compile’
    Auto compilation is trade-off. I don’t think it is good way.
    ‘ has poor plugins, etc.’
    Eclipse has many, which require you to buy them, which have poor compatabilites, which can even not work well with the platform! Though NetBeans has relatively fewer plugins than eclipse. But their qualities are high. They fit together much better. They can provide you almost any kinds of development. That’s enough. Do you want to spend a lot of time just in order to learn how play around an IDE? What we need is productivity! Not flowerish, useless, meaningless tricks.
    ‘There is a reason why Eclipse is #1. ‘
    #1, #2 does not stand for any thing. We programmers care only about which is really better, which is catching up!

  • November 27, 2005 at 9:24 am
    Permalink

    ‘Netbeans is still behind the times in implementing features that Eclipse has had for years (eg. flat file package view), and is still behind in the refactoring department. ‘
    Comment: It is just because NetBeans implemented these features a little later that it can learn from eclipse and do even better than eclipse. You know little about NetBeans. How can you boast for eclipse that its refactoring is better than NetBeans?

    ‘The fundamental problem is that Netbeans generates these attrocious form files which (a) make all the Swing classes completely vendor locked (b) make it near impossible doing the most minor refactoring.’ I don’t think a developer often needs to rename a compnent’s name. You can rename its name easily from the property page.
    ‘If I want to change the name of my ‘button1′, why can’t I just refactor in the code?’
    I do think to refactor a variable is more troublesome than to enter a single string in the property panel!
    ‘Eclipse on the other hand has GUI builders which in my opinion are as good as Matisse and DO support round-tripping, DO support refactoring,’
    Eclipse using round-tripping to synchrnoize gui forms and codes, which, as I know, is damn slooooow! It is really stupid to synchronize forms and codes from time to time! CPU, memory and other computer resources are completely wasted!
    ‘Netbeans is faster : Are you kidding me?? ‘
    Hey, baby, I am not kidding you. I have also used eclipse for more than 3 years. Don’t you think I am just guessing! Even on Windows, eclipse is only slightly superior on UI response!

    ‘Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    Only because you don’t know how tune it.
    Of course, maybe you have a different idea about what is beautiful.
    ‘The icons are big and clucky’
    You can change them to small icons. You have already got used to eclipse icons. That’s why you think netbeans’ are ugly.
    ‘and give it that nerdy feel of someone spending their Friday nights in front of Linux. ‘
    You are suely not familar with netbeans. It uses java se 1.5 look & feel, which makes netbeans just as native program. You have a long way to learn netbeans if you want to feel its grandness!

    ‘Creating a project in Eclipse is hassle : I find this the easiest thing about Eclipse. ‘
    Another evidence that you have worked on eclipe for too long!

    ‘Netbeans also doesn’t have auto compile’
    Auto compilation is trade-off. I don’t think it is good way.
    ‘ has poor plugins, etc.’
    Eclipse has many, which require you to buy them, which have poor compatabilites, which can even not work well with the platform! Though NetBeans has relatively fewer plugins than eclipse. But their qualities are high. They fit together much better. They can provide you almost any kinds of development. That’s enough. Do you want to spend a lot of time just in order to learn how play around an IDE? What we need is productivity! Not flowerish, useless, meaningless tricks.
    ‘There is a reason why Eclipse is #1. ‘
    #1, #2 does not stand for any thing. We programmers care only about which is really better, which is catching up!

  • November 27, 2005 at 9:24 am
    Permalink

    ‘Netbeans is still behind the times in implementing features that Eclipse has had for years (eg. flat file package view), and is still behind in the refactoring department. ‘
    Comment: It is just because NetBeans implemented these features a little later that it can learn from eclipse and do even better than eclipse. You know little about NetBeans. How can you boast for eclipse that its refactoring is better than NetBeans?

    ‘The fundamental problem is that Netbeans generates these attrocious form files which (a) make all the Swing classes completely vendor locked (b) make it near impossible doing the most minor refactoring.’ I don’t think a developer often needs to rename a compnent’s name. You can rename its name easily from the property page.
    ‘If I want to change the name of my ‘button1′, why can’t I just refactor in the code?’
    I do think to refactor a variable is more troublesome than to enter a single string in the property panel!
    ‘Eclipse on the other hand has GUI builders which in my opinion are as good as Matisse and DO support round-tripping, DO support refactoring,’
    Eclipse using round-tripping to synchrnoize gui forms and codes, which, as I know, is damn slooooow! It is really stupid to synchronize forms and codes from time to time! CPU, memory and other computer resources are completely wasted!
    ‘Netbeans is faster : Are you kidding me?? ‘
    Hey, baby, I am not kidding you. I have also used eclipse for more than 3 years. Don’t you think I am just guessing! Even on Windows, eclipse is only slightly superior on UI response!

    ‘Netbeans is more beautiful : I find the GUI to be pretty ugly actually.’
    Only because you don’t know how tune it.
    Of course, maybe you have a different idea about what is beautiful.
    ‘The icons are big and clucky’
    You can change them to small icons. You have already got used to eclipse icons. That’s why you think netbeans’ are ugly.
    ‘and give it that nerdy feel of someone spending their Friday nights in front of Linux. ‘
    You are suely not familar with netbeans. It uses java se 1.5 look & feel, which makes netbeans just as native program. You have a long way to learn netbeans if you want to feel its grandness!

    ‘Creating a project in Eclipse is hassle : I find this the easiest thing about Eclipse. ‘
    Another evidence that you have worked on eclipe for too long!

    ‘Netbeans also doesn’t have auto compile’
    Auto compilation is trade-off. I don’t think it is good way.
    ‘ has poor plugins, etc.’
    Eclipse has many, which require you to buy them, which have poor compatabilites, which can even not work well with the platform! Though NetBeans has relatively fewer plugins than eclipse. But their qualities are high. They fit together much better. They can provide you almost any kinds of development. That’s enough. Do you want to spend a lot of time just in order to learn how play around an IDE? What we need is productivity! Not flowerish, useless, meaningless tricks.
    ‘There is a reason why Eclipse is #1. ‘
    #1, #2 does not stand for any thing. We programmers care only about which is really better, which is catching up!

  • November 17, 2005 at 12:21 pm
    Permalink

    I have used Eclipse for about 3 years now and have just started to play around with Netbeans 5.0. Netbeans is still behind the times in implementing features that Eclipse has had for years (eg. flat file package view), and is still behind in the refactoring department.

    In response to some of the above comments :

    Netbeans is better for GUI : Matisse and form editor are all well and good for building a GUI. Hey, maybe using Matisse is better than sex. Whatever. The fundamental problem is that Netbeans generates these attrocious form files which (a) make all the Swing classes completely vendor locked (b) make it near impossible doing the most minor refactoring. If I want to change the name of my ‘button1’, why can’t I just refactor in the code? As for round-tripping you can forget it. Eclipse on the other hand has GUI builders which in my opinion are as good as Matisse and DO support round-tripping, DO support refactoring, DON’T have pointless vendor locked form files.

    Netbeans is faster : Are you kidding me??

    Netbeans is more beautiful : I find the GUI to be pretty ugly actually. The icons are big and clucky, and give it that nerdy feel of someone spending their Friday nights in front of Linux.

    Creating a project in Eclipse is hassle : I find this the easiest thing about Eclipse.

    Netbeans also doesn’t have auto compile, has poor plugins, etc. There is a reason why Eclipse is #1.

    ¬O.

  • November 17, 2005 at 12:21 pm
    Permalink

    I have used Eclipse for about 3 years now and have just started to play around with Netbeans 5.0. Netbeans is still behind the times in implementing features that Eclipse has had for years (eg. flat file package view), and is still behind in the refactoring department.

    In response to some of the above comments :

    Netbeans is better for GUI : Matisse and form editor are all well and good for building a GUI. Hey, maybe using Matisse is better than sex. Whatever. The fundamental problem is that Netbeans generates these attrocious form files which (a) make all the Swing classes completely vendor locked (b) make it near impossible doing the most minor refactoring. If I want to change the name of my ‘button1’, why can’t I just refactor in the code? As for round-tripping you can forget it. Eclipse on the other hand has GUI builders which in my opinion are as good as Matisse and DO support round-tripping, DO support refactoring, DON’T have pointless vendor locked form files.

    Netbeans is faster : Are you kidding me??

    Netbeans is more beautiful : I find the GUI to be pretty ugly actually. The icons are big and clucky, and give it that nerdy feel of someone spending their Friday nights in front of Linux.

    Creating a project in Eclipse is hassle : I find this the easiest thing about Eclipse.

    Netbeans also doesn’t have auto compile, has poor plugins, etc. There is a reason why Eclipse is #1.

    ¬O.

  • November 12, 2005 at 6:37 am
    Permalink

    😉 i have been using it and will continue to use it. with all these ppl complaining about Eclipse i don’t think i will waste my time with such a rudimentary program.Everything i could ever need as a ‘developer’ , i find in Netbeans.
    Tallehou!!!

  • November 12, 2005 at 6:37 am
    Permalink

    😉 i have been using it and will continue to use it. with all these ppl complaining about Eclipse i don’t think i will waste my time with such a rudimentary program.Everything i could ever need as a ‘developer’ , i find in Netbeans.
    Tallehou!!!

  • November 11, 2005 at 4:25 am
    Permalink

    I definitively like NB5. And even NB4 was already great.
    I’ve tried in many rounds Eclipse but I simply can’t understand his philosophy. How to start? Where do I install plugins? Why can’t I even do a damn successful compil of helloworld in less than 5 minutes? Why it’s so complex for simple things?
    I prefere NetBeans of his integrated and fundamental plugins (visual editor, web, tests, DB…) and, and, and his wizards.
    What I hope in the future is an integration of an opensource JDO implementation in NB. That’s still one good point for Eclipse. …for now.

  • November 11, 2005 at 4:25 am
    Permalink

    I definitively like NB5. And even NB4 was already great.
    I’ve tried in many rounds Eclipse but I simply can’t understand his philosophy. How to start? Where do I install plugins? Why can’t I even do a damn successful compil of helloworld in less than 5 minutes? Why it’s so complex for simple things?
    I prefere NetBeans of his integrated and fundamental plugins (visual editor, web, tests, DB…) and, and, and his wizards.
    What I hope in the future is an integration of an opensource JDO implementation in NB. That’s still one good point for Eclipse. …for now.

  • November 4, 2005 at 3:52 pm
    Permalink

    They both suck, here’s why: when deployed in a larger corporate setting, you end up with welfare coders who can’t operate a door knob because the fancy editors do it all for them – VERY BAD – why? because management; instead of providing training and understanding; will put Ashok Contractallibaba in charge of the tool and its configuration; further fucking over the staff. Then Ashok gets canned or goes to work for fuckyouUSA.com subsidary of al quida and the department is hosed.

  • November 4, 2005 at 3:52 pm
    Permalink

    They both suck, here’s why: when deployed in a larger corporate setting, you end up with welfare coders who can’t operate a door knob because the fancy editors do it all for them – VERY BAD – why? because management; instead of providing training and understanding; will put Ashok Contractallibaba in charge of the tool and its configuration; further fucking over the staff. Then Ashok gets canned or goes to work for fuckyouUSA.com subsidary of al quida and the department is hosed.

  • November 3, 2005 at 5:26 am
    Permalink

    I have never seen a IDE which made so greate a jump ahead! It is really awsome! Since Netbeans 4.0, it advanced so much that you even doubt they are of the same IDE!
    The bad looking age ever gone! It is now even more beautiful than eclipse.
    Slowness seems to be mother’s age! Just cannot believe a swing-based software can even be faster than a native-code IDE.
    Good refactoring tools make it catch up with eclipse.
    Well-integrated tools! You don’t have to look around for plugins which might be incompatible , which might be commercial, and which might be bad-fitted with other plugins, not like eclipse!
    Fantastic GUI designer-Mattise. So intuitive, even better than VB and Delphi.
    Exllent J2EE development support!
    Exllent Mobility pack!
    Exllent J2SE 5.0 support!
    I am crazy about it. Originally, I have been using eclipse for 3 years. It is slowing down and down and I start to get bored of its speed and incompatibility- plugins and OS platforms!
    I think eclipse developers who are stil keen to eclipse should turning your head to netbeans and be careful and a little patient to see what is real happening to netbeans these days.

    Netbeans in the battle:
    First, they ignore you.
    Then, they laughed at you.
    Then, they fight you.
    At last, you win.

    Netbeans is eclipsing eclipse. Eclipse is being eclipsed.

  • November 3, 2005 at 5:26 am
    Permalink

    I have never seen a IDE which made so greate a jump ahead! It is really awsome! Since Netbeans 4.0, it advanced so much that you even doubt they are of the same IDE!
    The bad looking age ever gone! It is now even more beautiful than eclipse.
    Slowness seems to be mother’s age! Just cannot believe a swing-based software can even be faster than a native-code IDE.
    Good refactoring tools make it catch up with eclipse.
    Well-integrated tools! You don’t have to look around for plugins which might be incompatible , which might be commercial, and which might be bad-fitted with other plugins, not like eclipse!
    Fantastic GUI designer-Mattise. So intuitive, even better than VB and Delphi.
    Exllent J2EE development support!
    Exllent Mobility pack!
    Exllent J2SE 5.0 support!
    I am crazy about it. Originally, I have been using eclipse for 3 years. It is slowing down and down and I start to get bored of its speed and incompatibility- plugins and OS platforms!
    I think eclipse developers who are stil keen to eclipse should turning your head to netbeans and be careful and a little patient to see what is real happening to netbeans these days.

    Netbeans in the battle:
    First, they ignore you.
    Then, they laughed at you.
    Then, they fight you.
    At last, you win.

    Netbeans is eclipsing eclipse. Eclipse is being eclipsed.

  • October 21, 2005 at 10:11 am
    Permalink

    I had been using Eclipse fairly solidy for 2 weeks and as a beginner found it excellent in terms of explain my errors.
    However I had to try and query a database and put data into a form and was struggling combining the two (easy to do seperately).
    Anyway, netbeans helped me build a GUI fairly quickly, and link button events to certain methods…in a way it has pretty much taught me how to do a lot of things and actually giving me some output to work with.

    My only complaint is that it is slower than eclipse to let you know of errors on a line and overall the program is slower than eclipse.

    Any ideas on how to speed up NetBeans?

  • October 21, 2005 at 10:11 am
    Permalink

    I had been using Eclipse fairly solidy for 2 weeks and as a beginner found it excellent in terms of explain my errors.
    However I had to try and query a database and put data into a form and was struggling combining the two (easy to do seperately).
    Anyway, netbeans helped me build a GUI fairly quickly, and link button events to certain methods…in a way it has pretty much taught me how to do a lot of things and actually giving me some output to work with.

    My only complaint is that it is slower than eclipse to let you know of errors on a line and overall the program is slower than eclipse.

    Any ideas on how to speed up NetBeans?

  • October 13, 2005 at 1:52 am
    Permalink

    Many years ago I programmed in C, then C++, then jBuilder came along. Using Borland products for many years finally getting to utilize Microsoft Visual C and Visal Basic. But made the transition to Java Because of the trend of Apache HTTPd servers moving toward Jakarta Ant, Struts and Tomcat. Now almost exclusively I program in .jsp and use the JavaServerPages 2.0 paradigm. In early days of Java I used Eclipse and MySql and at the time were not very stable. Now using Netbeans 4.1 with J2EE AppServer and it works fine for me. Not even have a very fast computer. My test server is running Apache Jakarta Tomcat 5.5.9 and not the 5.5.7 bundled with the Netbeans 4.1. 5.5.9 is stable and usuable for deployment as webserver.
    Oops…made it too long…sorry.

  • October 13, 2005 at 1:52 am
    Permalink

    Many years ago I programmed in C, then C++, then jBuilder came along. Using Borland products for many years finally getting to utilize Microsoft Visual C and Visal Basic. But made the transition to Java Because of the trend of Apache HTTPd servers moving toward Jakarta Ant, Struts and Tomcat. Now almost exclusively I program in .jsp and use the JavaServerPages 2.0 paradigm. In early days of Java I used Eclipse and MySql and at the time were not very stable. Now using Netbeans 4.1 with J2EE AppServer and it works fine for me. Not even have a very fast computer. My test server is running Apache Jakarta Tomcat 5.5.9 and not the 5.5.7 bundled with the Netbeans 4.1. 5.5.9 is stable and usuable for deployment as webserver.
    Oops…made it too long…sorry.

Leave a Reply