Customizing the look is an utter mess. No concept of "themes" built in. All the colors and font attributes are attached directly to smallest Java syntax details and have to be micromanaged.
To be fair, my criticism might only be valid up to some point last year because that's when the Scala IDE distribution I'm using was built. Mainline Eclipse's version 4 seems to be out already, dunno how extensively it fixes theming. I'm actually more interested in whether they've done anything about the shitty editor and keyboard shortcuts.The next version... 4, is it? ... is supposed to have support for actual themes.
Themes are hardly essential for a music player. You listen to a music player. You look at an IDE for hours a day.Themes are hardly an essential, this isn't a music player.
Well, Eclipse falls on its face then. The editor is a laggy, user-hostile piece of shit. This is the first IDE I have ever seen where I can't even switch between tabs without going through a dialog (which is, apparently, its own OS window based on how the menu bar blinks out of existence when the minimenus are open, and Eclipse lags half a second upon switching to this other window and back.). I'm running Eclipse on OS X, and it doesn't feel like an OS X application, or like a Windows application, or like any Linux application I have used. I have ran it way back in the past on Windows and it was no better on that platform. The default keyboard shortcuts have no internal logic and are supremely unergonomic. What incredible moron thought cmd-F6 was a perfect choice for switching between tabs? (By the way, it looks to me like plain "F6" isn't used at all. Maybe the devs are reserving it for something more important like a future FactoryEclipseAdapterComponentWizard shortcut.)The core features of the ide and fast and reliable as well as being easily accessible.
Okay. How do I make the editor usable?That is ultimately what is needed and you just have to spend time learning how to use it well. Eclipse is an excellent ide, and the only one I know of that support incremental compilation, which is a killer feature on a real project.
Eclipse is an excellent ide, and the only one I know of that support incremental compilation, which is a killer feature on a real project.
Perhaps for you, if you didn't use anything better, or didn't understand its limitations. However, VS is generally despised by people coding more than Windows software. Debugger is surely nice, but that's about it. It might serve well for Windows only developing, but world is moving away from that.
2. Both support many platforms and compilers, while VS works only on Windows and with MS compilers
3. Both Nebeans and Eclipse own VS when it comes to understanding and navigating code. VS editor can't understand OO code at all, and for example it can't build proper call graph if function is virtual (same function name exist in different classes). On the other hand, Eclipse and NB use compiler to parse the code.
4. VS has weak integration with SVN and other configuration management tools, while with other two you can do anything you want within the IDE.
5. VS has very backwards way of setting up projects. Project files must be added via GUI. Project options must be setup in GUI. Any file you add to project will be compiled, so you can't easily support multiple configurations. A more powerful ways are used in C/C++ with makefiles and Java Ant/Maven. Just flexibility is not there - there is only one way to do projects.
I've done my embedded C programming in AVR Studio and Freescale Codewarrior.
Vim Superiority.
Throw some Tmux in there and you have the perfect IDE.
Themes are hardly essential for a music player. You listen to a music player. You look at an IDE for hours a day..
I still don't understand the hate for Eclipse. I've used it for years (well myEclipse and RAD) because everything I've worked on deploys to a WebSphere App server and don't have any problems with it. Maybe I am just not picky or haven't used anything better.
And Eclipse is just terrible, no usability, will make an i7 with a fast SSD feel slow and is just buggy as hell.
This thread is still alive?
I used Eclipse for RCP and RAP Developers within a VM hosted on my laptop for a couple of years. The VM has one vCPU (host laptop has an i7) and 1 GB of RAM. Host laptop also has a spinning drive. My typical workspace has 200+ projects for different plug-ins we are working on.
I've never really noticed any slowdown, crashes, or bugs that you speak of.
The only big issue I have with Eclipse is how it handles resources and detects changes to files in your workspace done outside of Eclipse.
As far as usability goes, Eclipse does have a learning curve, but once I got it down I found it very intuitive. Problems can occur when 3rd party plug-ins do not follow design guidelines/best practices.
What I find most impressive about Eclipse is their release model. It is a hugely distributed project with many moving parts. They are able to plan features, consistently hit their dates, and deliver releases reliably on an annual basis; all for an open source project. A lot of different projects (both OSS and paid) could learn a lot from a release management perspective.
This thread is still alive?