As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm new to Java. I took an introductory course where I was using NetBeans, but I noticed that some of my classmates were using Eclipse. From what I've understood, Eclipse is the popular IDE among IT companies.
My question is, as a new programmer, should I stay with NetBeans or switch to Eclipse?
You forgot one more: IntelliJ.
They are all different and there is no single "best one", for example each has a feature that another doesn't.
My personal remarks:
Eclipse is probably the most open. It's very actively developed. It was the de facto standard at all 4 companies I worked for so far. Eclipse is completely free.
IntelliJ is kind of intelligent. It's really interesting to use, but not all features are available in the community edition. I evaluated it because somebody claimed that a study shows that it makes you about 10% more productive but I haven't seen the study itself. I think IntelliJ is awesome but I'm so used to Eclipse it's really hard to switch.
Unfortunately I've never even seen NetBeans.
Considering these points, Eclipse seems the safest choice, due to its popularity at my past workplaces and open and free nature. But your mileage may vary.
Just keep in mind that Eclipse/NetBeans/IntelliJ whatever are just tools. It doesn't matter whichever you choose, the most important thing is that you get coding, and code well. Use whichever makes you the most productive.
Honestly, I think both are equally prevalent. Once you learn one, it is not a huge deal to switch to the other. Those with whom I work have their own preferences, and the company does not have a preference - nor do the contracting companies that we work with. To each his own seems to be pretty standard policy. That being said, in my experience the IDE choice has sometimes been defined by the problem at hand (ease of use, different plugins for particular purposes, etc.).
Bottom line - learn both. It isn't that hard to do and you will probably use both eventually anyway.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I've just watched a video of the Groovy inventor, James Strachan, in which he goes on quite passionately about loving Scala. That caused me to want to find out more about Groovy which lead me to Groovy++. Groovy++ is a statically typed and compiled version of Groovy (which is apparently completely dynamic).
I attempted to figure out what Groovy++ (latest version at 0.9.1?) was in contrast with Scala (latest version at 2.10). The activity on the Groovy++ forum doesn't have very much recent activity regarding the latest version for which to be able to draw much information.
So, is there a nice simple comparison/contrast of Scala to Groovy++? I am not interested in Groovy itself (other than being the basis upon which Groovy++ is designed) as I want to compare statically compiled features side by side. A simple advanages/disadvantages (i.e. tradeoffs) list is basically what I am seeking without having to do dozens to hundreds of hours of research and experimentation.
Thank you, in advance, for anything you can contribute to this contrast and compare query.
Groovy++ project died last year-ish, apparently due to schism between SpringSource Groovy team and non-SpringSource supported Groovy++ team (led by Alex T. who now seems to be an active contributor to the Kotlin project along with, ironically enough James Strachan).
Was pretty ugly, Alex T. was understandably pissed off about getting the rug swept out from under him (Spring Groovy announced their own static Groovy). Check through some of the Old Nabble entries for the back & forth, heated at times. Not sure how things stand now, competition brings out the best & worst, maybe both sides are over it...
At any rate I too bailed, ditching Groovy for Scala and am overwhelmingly happy to have made that decision -- Scala rocks, I dare say, it Scocks™, give Scala a try! ;-)
Groovy was a great transition-to-JVM language for me, but the lack of compile time guarantees just drove me nuts after awhile (probably why static Groovy project(s) came into being in the first place)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Dev-C++ was one of the first IDEs that I got my hand on long ago. To me, Dev-C++ was a small software that can be downloaded and I could quickly do academic assignments with it.
In my college, people have been suggesting Dev-C++ for a quick download and just do the homework, for a few generations now. I recalled I used to have some problems with Dev-C++, mainly not understanding what exactly are mingw, different dependencies, different compilers, and all the complicated stuff.
When I tried to go for bigger projects, I always have the trouble of getting help. Other online helps seem to favor Visual Studio a lot more. For veteran developers who understand compilers and how things go around in software development, this may not be so difficult. But for people who are new to learning programming, is Dev-C++ a reasonable choice? Or should they not use Dev-C++ at all? Will the end justify the mean in the long run?
It's my understanding that Dev-C++ hasn't been supported for a long time and accepts a lot of bad code which it should reject, and it's not recommended simply because it's low quality compared to Visual Studio. Dev-C++ was my first C++ development environment too, and I wouldn't recommend it. VS also has one hell of a debugger, and some strong online reference material, not to mention all the other fun features of having a proper IDE. Visual Studio Express is free for everyone, even the current version, and whilst it's not quite as powerful as the commercial versions, it's still far superior in quality to Dev-C++.
All you have to do is look at the supported versions of Windows. Their latest non-beta version doesn't even list XP as supported.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I am working on my C programming skills. I decided to run Ubunutu Linux and use code::blocks as my IDE. Now, I need a good source control.
Something that's easy for a beginner to administer (I want to concentrate on coding not managing a server)
Free
Hopefully has a plugin that integrates well with code::blocks
I plan to use source control for my own use. I want to be able to undo my changes if I make too many mistakes. I also want to be able to revert back to an old version and do side-by-side comparisons.
Maybe one day, my buddy and I could work on some code together (from different locations), but this is not a major concern at this time.
What works for me?
You want Mercurial or Git. I personally prefer Mercurial.
Subversion is still very popular and stable. It's centralized though, which these days is considered "the old way." (I've heard people say "Git is to SVN what BitTorrent is to FTP.")
Git is pretty much the in thing right now. In my opinion it has a higher learning curve, but its adoption by the open-source community is widespread.
Mercurial is a great DVCS and, in my opinion, doesn't get enough attention. Great commercial products are built on top of it, though, so growing your project to a commercial system is pretty smooth.
There are others.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I've started to read the book "Code Craft" by Pete Goodliffe. The fourth chapter is about instruments that developer uses during his daily work; this chapter made me to review my work and I've seriously decided to make it easier with fully personalized IDE. Eclipse IDE is what I've started my learning from...
I've read documentation and found that it's really easy to do tasks routine from Eclipse. We are using Mantis for tracking tasks and it was great surprise for me to find out Mantis Connector for Mylyn.
Also I was pretty glad to see SVN client integrated into Eclipse IDE.
Also I've found UML2 tool for Eclipse, but was disappointed because there is no any graphic interface for building diagramms. (Or, maybe, I'm was searching in wrong place?)
What useful plugins do you use in your daily work?
How do you use Eclipse for collaboration in your team?
Do you have any links about intergration Eclipse IDE experience in dev. team?
Thank you!
If you do web development with Tomcat, the Sysdeo launcher plugin is handy. Also, it is definitely worth some time to learn the more important keyboard shortcuts. Good lists here and here (with a little overlap). Ctrl-Shift-R and Ctrl-Shift-T are especially vital when you have a large code base.
I use eclipse for Java, so that's pretty much the extent of my experience as far as languages go.
Subclipse (which I guess you are using) and the built in JUnit tool are the two things I use the most.
Also, hitting F3 will take you to the definition of a method, and F4 will tell you which classes implement a given interface.
Eclipse will also generate your getters and Setters (RightClick->source->Generate Getters/Setters)
My two favorite hotkeys in Eclipse are
control-alt-up/down : copy the current line or selected lines
alt-up/down : move the current line or selected lines
Get used to these two and your coding speed improves drastically!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
How does the IDEA Community Edition compare with Eclipse?
IDEA is a far better IDE than Eclipse (general opinion by people that use IDEA).
On a feature point of view, everything that IDEA CE can also been done by Eclipse. However,
IDEA is a commercial product, which limits its adoption. Thanks to the Community Edition, you can test this IDE for free, in order to develop JavaSE applications (or Scala or Groovy). For an enterprise, this is quite limited, as you will not be able to develop J2EE applications.
My conclusion is that IDEA CE is only a tool that allows you to test and understand the philosophy of this IDE. If you are convinced by IDEA, then you will really have to choose between the Ultimate Edition, which will let develop any kind of applications, or stay with Eclipse.
The best, straight answer to this, is to look at the feature matrix of which features are still left in Ultimate-Edition. Eclipse probably has support for all of these things, although the quality of the integrations can always be an issue.
Why IDEA:
detects unused public fields and methods
easy way to run or debug only one test method (you don't need to modify configuration)
faster code coverage report generation (at least for EMMA)
understand difference between source and test source
easier way to manage libs - just include lib dir (in eclipse you have to specify all jars explicitly), so you don't have to update it manually every time when new jar was included