I have just started seriously using Netbeans for the first time - I've been forced to because it's what the client uses.
And I have to admit, that having used Eclipse up till now, I am definitely not enamoured with netbeans at all. In fact it has done nothing to recommend it. I constantly find myself going... oh, I wish I was using Eclipse.
Netbeans fans might be crying foul right now... and they have a right to, let me record some of my initial frustrations...
1. No inline variable
2. No inline method (though there is an extract method, called introduce method).
3. When you use the template short cuts (for, create field etc) the tab does not leave you where you want it to
4. It hides a lot - we're doing web service development - all the ant xml files which are used to compile and build, you don't see.
5. No call hierarchy
6. Search facility is nowhere near Eclipse
7. No Quick diff comparing repo version with local version (via the ruler)
A good way to explain netbeans is to say it is opinionated software (I remember someone describing ruby on rails like that) - iow, it's great, if you obey the rules and if you want to stay within the confines of what it wants. I don't like the ant scripts it generates and uses to build - I want to roll my own, as eclipse will let me and thus customise them the way I want to.
So what do I like about Netbeans?
It has very strong integration with glassfish - tells you a lot about the running glassfish server you're using to deploy to. I also wish I could use the collaboration stuff, because I've seen that it is very good.
I'm going to have to continue using netbeans so I'll see if my opinion changes... I'll wait and see.
Python, typescript, java, kotlin, C#, .net… Which is your technology of choice? Which one are you currently working in and which do you wa...
Yes, who would need a build that does not have a Head? That sounds like it's out of a horror story. What I mean however is a build whi...
If I had R10 or a dollar, for the amount of times developers assume something because they say it "should" be like that, I would b...
When I arrived on my current project one of the first statements that was made is that we need a wiki. I hadn't used one in the past so ...