Eclipse Foundation Celebrates 10 Years
msmoriarty writes with news that the Eclipse foundation is ten years old this week. Although Eclipse was released in 2001, development was controlled by IBM until the creation of the independent Eclipse Foundation in 2004. "According to Eclipse Foundation Director Mike Milinkovich, that's a major reason Eclipse was able to thrive: 'IBM....did an exemplary job of setting Eclipse free ... We became the first open source organization to show that real competitors could collaborate successfully within the community.' He also talks about misconceptions about Eclipse, its current open source success, and what he sees for the future."
The Eclipse line was phased out by 1989. Heck, Data General wasn't even a company anymore by 2001.
Even though I've owned a copy of IntelliJ IDEA for over a year, I still use Eclipse everyday for Java development. Latest version is great and the extensions available for it make it even better.
Reviewing just the first hour of video games.
I hear Flashbuilder is built on top of Eclipse. I need to quit every day and restart because of a memory leak that slows everything down to a crawl with massive type lag of 1s+ between key presses. Its so easy to get stuff done in AS3 compared to any other language, but I often feel like I'm fighting the IDE.
God spoke to me
Java can be pretty quick these days, lots of hard work went into optimizing the runtime.
There are many things a VM like Java can do that you can't do in C++ (although C++ is inherently faster and lighterweight). But it can't optimize virtual calls away like the JVM can.
Mod me down, my New Earth Global Warmingist friends!
I always found Eclipse to be very fidgety, and I've only ever been able to get one non-java project debugging properly inside of it. Conversely, netbeans ... well.. it just works. It has full C++11 support these days, and is, in my opinion, much friendlier to pure java development, using ant as its native build tool.
(My money's on this comment being modded down by eclipse fanboys, ah, but what the hell, I'll post it anyways.)
File under 'M' for 'Manic ranting'
All that you touch
All that you see
All that you taste
All you feel.
All that you love
All that you hate
All you distrust
All you save.
All that you give
All that you deal
All that you buy,
beg, borrow or steal.
All you create
All you destroy
All that you do
All that you say.
All that you eat
And everyone you meet
All that you slight
And everyone you fight.
All that is now
All that is gone
All that's to come
and everything under the sun is in tune
but the sun is eclipsed by the moon.
"There is no dark side of the moon really. Matter of fact it's all dark."
Eclipse and Java make a bit of a unique pair. Java is massively verbose by today's standards, but it's strict typing and highly declarative approach allows your IDE to do amazing things when it comes to refactoring or code analysis. Then there's the fact that Eclipse is by no means just a Java IDE, but that's just part of its giant eco-system.
Eclipse is one of the reasons I was super sad that Oracle bought Java instead of IBM. IBM at least proved they can make a good product using Java, using its strengths and subverting its weaknesses.
It's turtles all the way down.
I've been using Eclipse on for pretty much 10years now and by and large, the tool has been pretty darn soliod. its a memory pig so get over it. I throw 1.5G at the heap and though it rarely if ever gets close to it, the amout of speed it performs mosdt operations is amazing.
There are warts which I find personally lousy (like Mylyn of the built-in profiler, and much of the built-in text validators), but thankfully most of those can be trivially turned off and tweaked to speed up usage even more. With a few choice plug-ins, you can do a lot of the hard lifting without effort.
I've only had cursory usage of Netbeans/Idea, but Kepler is really a dream to use. Note, almost every first few months of a new release are generally ass, and Juno was entirely ass so be warned. Just because one version of Eclipse may be a flake, don't discount the platform.
Bye!
...I'm still running 3.7 because the 4.x releases are (by all accounts) still not "fixed". Sigh.
Agreed. As a development environment, I really dislike Eclipse. The Visual Studio tool line is great (whether you like MS or not, it's a very developer-friendly tool). Eclipse is very cumbersome to use and seems to take forever for tasks that shouldn't. While I like that it's flexible, I'd rather just use Notepad++ and a command line compiler than run Eclipse.
I've been using Eclipse for a few months on CentOs virtual machines for MapReduce development. The Maven m2e plugin is a huge boon. I never noticed Eclipse freezing unless it was doing something like cleaning the workspace, or updating the Maven local repo, or something like that, in which case it tells me it's doing something.
I started doing more Java SE work, so I loaded the same setup onto my workstation that hosts the VMs, which is a pretty decent Win7 machine, and now sometimes it just freezes, then catches up really quickly like lag in an online game...still stays pretty darn normal in Linux. Weird.
memory: did you tweak your heap size in eclipse.ini?
There are many things a VM like Java can do that you can't do in C++ (although C++ is inherently faster and lighterweight). But it can't optimize virtual calls away like the JVM can.
It's not virtual calls that make Eclipse randomly freeze for ten seconds or more. And I've wasted more time having to hit CTRL+C a dozen times to get it to copy than I ever have in virtual function calls in C++. Or restarting it when it runs out of RAM despite having a ton free on the machine, or runs out of handles because they're not closing something properly because, hey, garbage collection will take care of that, right?
Eclipse is a decent IDE when it works, but I'm sure it would work a lot better if it wasn't written in Java.
...and I'm still waiting for it to load!
What the hell would you be doing where optimizing a vtable lookup away will matter in the slightest?
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
It's made by Oracle. Enough said
What I really want to type is Java is dying and a security nightmare, but sadly this ancient relic like IE 6 and Cobol won't die fast enough. I hate having apps requiring one version that conflict and constantly infects the same systems over and over again due to the +100 security holes!! I have read many posters switching to c++ for these reasons
Like SCO you hurt the Foss by using Oracle products.
http://saveie6.com/
I don't use Flashbuilder that much, as I prefer their other tool, but I've never had a problem with any version of Flashbuilder on my Mac. It might be worth a try if the Windows version isn't working for you.
Flash Professional might be another option.
Dude, quit complaining and buy a new computers.
No seriously, that wasn't a typo.
Priest: "Universe from nothing, no laws of physics, sped up time"+ huge discrepancies. Creationism? No. Big Bang Theory
There are many things a VM like Java can do that you can't do in C++
The JVM is written in C++.
I have no love for Oracle, but I use netbeans because, as I said... it works. And it works better than anything else I've tried.
File under 'M' for 'Manic ranting'
"but I'm sure it would work a lot better if it wasn't written in Java."
I'd give up the modest goal "work a lot better" and trade it in for "it happens to work a lot".
Exits quickly, but Eclipse is spectacularly slow preventing actual work from getting done. It is like a low FPS video game where the problem is supposed to be your setup, but I've never found a computer powerful enough to run Eclipse at a tolerable speed considering my impatience.
Priest: "Universe from nothing, no laws of physics, sped up time"+ huge discrepancies. Creationism? No. Big Bang Theory
It's called RonPaulCoin now. Geez!
Priest: "Universe from nothing, no laws of physics, sped up time"+ huge discrepancies. Creationism? No. Big Bang Theory
Eclipse has become a universe onto itself. It's got its own GUI kit, thread model, all kinds of stuff I'm too drunk to name at this moment.
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
One of the most awesome things that the Eclipse people did was switch to a foundation built on OSGi after the first version. Eclipse is a showcase that showcase the power of a modular component framework.
Sun really screwed up by failing to adopt OSGi for Java's module system.
When I think of the best technologies available to the average Java developer like myself I rank the JVM first and OSGi second.
With setup boxes now set to become ubiquitous, I want a box that integrates some OSGi-like framework that will enable me to integrate all the devices in my house.
Eclipses quarks have nothing to do with java. Have you ever looked at the code behind eclipse? It's terrifying!
The way they handle tasking/progress is particularly bad (and the reason why it'll get hung up during certain operations.. it gets stuck in deadloops/race conditions and just chews through memory).
It's actually amazing how well it (generally) works, quarks aside.. given how shaky the code is. I like to think of it as a pile of crap that's been sculpted into something mostly usable.
Have you ever looked at the code behind eclipse? It's terrifying!
No, I haven't. But I'll concede that anyone who can write bad code in Java can write much worse code in C++.
From the limited time I've spent in eclipse's code, it seems a case of poorly done decoupling. It's layers upon layers of abstraction that's expected to just kinda sort itself out, which of course it doesn't and things end up in loops until the operation either times out, fails, or something changes that lets it get out of the loop and maybe even finish.
Clicking the cancel button is optimistic at best, especially when it's in one of it's death patterns. It just really seems to do a poor job of operation management in my opinion. When eclipse seems to be "taking forever", chances are it's two operation tasks bouncing back and forth waiting on each other, and not actually slow processing.
That said, I still love eclipse for Java development. Once you learn the do's and don'ts (and which files to delete when eclipse has a melt down), it's pretty usable.
It's great.
There a lot of shitty plugins when used as an IDE, like the Javascript ones that add JS validation and builders to your web projects, bring the IDE to a standstill when every they run.
Eclipse is six of one, half a dozen of the other. I've used it for many years, but the Kepler release has decided that it's going to do something Eclipse never did in the past: crash. Hard. As in *poof* -- it's gone.
It's also been freezing up under Debian at random.
The windows build seems more stable, and that's what I use for most debug sessions, but I *prefer* to work on my Linux box due to the better resolution and nicer interface devices than my laptop.
But hey, it's a big project (both Eclipse and my own.) Big projects have bugs. Period. I certainly can't complain about Eclipse, all in all. It does what I need, does it well enough, and integrates with JEE debugging environments. Can't really expect something dealing with that big a pile of steaming code to also be stable.
I do not fail; I succeed at finding out what does not work.
Amen. I have been using Forte for Java, then Netbeans. In the mean time ( years, really ) I did one or the other odd project on Eclipse. No comparison in ergonomy and user-friendliness. Netbeans gives you the tools you need in obvious places; in Eclipse, you must either search for the tool, or you have dozens of them lying around when you really need only one. Eclipse = usability hell.
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
Have you adjusted the heap memory settings in eclipse.ini?
Here's the guide I wrote for using the IBM JVM for RSA and RTC, Oracle/JVM settings are similar.
XML is a known as a key material required to create SMD: Software of Mass Destruction
Maybe a clumsy choice of words, but I was thinking about the heavy use of annotations, or XML or property files used by many of the popular Java technologies.
Things are rarely glued together with scripting in the Java ecosystem, somehow it lends itself to complex XML config.
Eclipse can statically analysis all the XML config (and annotations etc) to show the developer how everything fits together in a more visual and cross referencing way.
Others in this conversation chain have mentioned how this approach often falls apart under complexity though regardless of how good your tools are.
It's turtles all the way down.
But . . . C++ isn't webscale!
I read TFA and all I got was this lousy cookie
Well, I love it for just about all my C/Android/Java Servlet programming.
The only thing I can't really use it for is LINUX kernel programming/device driver development.
Just too big.
But I would like to thank everyone who works on the plugins for Eclipse, especially Toad which is one of my favorites and svn plugin.
Kisses and hugs to you all.
xoxoxox :-)
Got Geometrodynamics? Awe, too hard to figure out? Too bad.
Eclipse is my saviour. I needed a UI to program under and I haven't really been happy with one since the pre-.NET versions of Visual Basic (horrendous language, lovely development environment for me - I honestly think we lost something in not taking that UI further in open-source development environments).
Got back into C99 and Eclipse with CDT was phenomenal. Bit of faffing with the config at first but I was able to get a development environment consistent across platforms, with all the tools you could ever want.
The debug UI is fabulous, to me. The customisability of the workspace (get out of my damn way and let me code, oh except for that one REALLY useful feature that's earned the right to be there all the time, etc.). In a way, it's my development "Opera" - hugely customisable to my particular odd way of working.
Plug it into gcc in its various flavours (native Linux, MinGW, Cygwin, etc.) and it's quite happy. Move your program to a Linux VM for testing and you can take the development UI with you if need be.
Plug in every kind of tool imaginable, including fairly decent versioning management (not its strongest suit but more than capable). Upgrade simply by making a copy of the eclipse folder and then running the upgrade over the top.
And - at the end of the day - when you have to write that Android wrapper for your program, or the website or online documentation of your masterpiece, you can do without even having to come out of it.
Eclipse is what got me back into my programming and allowed me to push out several apps for my employers on a whim. None of the other programs managed that.
And, best of all, it's free and keeps moving onwards. All the people I've heard whinge about Eclipse (which I've only been using since before Galileo) complain about it being heavy/buggy. It's something I've honestly not experienced and, damn, my buggy programming must test it to the limit sometimes. If you're developing on a "light" machine, I can't see how you're helping yourself. But I'm not using a supercomputer here, just a handful of fairly decent laptops / desktops.
I think Eclipse is a little like Windows. Keep it clean, don't experiment too much with random third-party junk, and make backups of the working config (so easy in Eclipse that I have a folder of every named release that I've ever used just in case I needed to rollback) and it'll stay up and stay working. Mess about with it too much and it'll turn into an unmanaged piece of junk.
I can't honestly say that I've ever seen it crash, though. And we're talking Windows (XP / 7) / Linux (Slackware and Ubuntu, several versions), desktop / laptop, old clunker and shiny new machine, and quite a lot of stuff plugged in (CDT, Android SDK, several SVN connectors as they've changed over the years, Valgrind, etc.).
have they improved default code style, finally?
No, those things are nothing to do with inherent problems with Java, and everything to do with the fact Eclipse is shit.
There are Java applications that are far more complex and require far higher stability and performance than Eclipse that work just fine. Eclipse is just an exceptionally bad piece of software.
It works fine for me. I like the fact I can just copy over the whole eclipes 'install' directory from one computer to another and it just seems to work.
Same with workspaces, just copy that whole thing over. Works fine.
I also use a mercurial plugin with it to save my code to bitbucket. Again, works like a dream.
It's never crashed or slowed down for me (though I rarely update it, because it just works)
However, I mainly code in C++ with it and have only produced one commercial java/android project with it...that worked fine too.
In fact, I love it so much that I donated to them recently.
The only other IDE I think is better in M$ Visual Studio...but that doesn't run on linux and uses shed-loads of disk space, so they can keep it.
Eclipse doesn't freeze for years for me and its performance is pretty ok for JavaEE development. I guess people are stuck with this "eclipse is slow" opinion just like some people still think java is slow.
It can be.
Red to red, black to black. Switch it on, but stand well back.
Well there is nothing you can do in C++ that you can't do in a turing machine.
Thank you for that link, as it's probably quite useful.
However, addressing Eclipse rather than you, I've never used any other IDE that required a user adjustment in heap memory settings. There's something wrong with that.
I use Eclipse all day, every day. It's fast and stable, until certain plug-ins are added. Then, slowdowns happen, mostly because the plug-in is blocking because it is poorly written. As far as CTRL-C not working, I just don't see that. I don't have memory issues, either, as long as I create reasonably large heap, stack, and perm gen.
your anti-virus software. This is a drawback of Java in general, as anti-virus insists on scanning every one of those files in the JAR's.
I found Eclipse horrible. IntelliJ or Netbeans both look better, are faster, leaner and just...feel better. So many "solutions" to problems on Eclipse involve uninstalling and reinstalling, or using the "restart" option on the File menu (don't laugh). Why? Why is it recomended you don't uninstall plugins you no longer want to use? Does it have to be that unstable?
Even though I'm often skeptical of Java's performance, I'll play the devil's advocate here and point out that Emacs is written in elisp, which runs on a byte code interpreter and is garbage collected. Despite the jokes, it doesn't have as much stuff as Eclipse, but still it runs fast.
There are Java applications that are far more complex and require far higher stability and performance than Eclipse that work just fine.
Can you name some "client side" (something you'd run on your PC) pieces of software like that? Serious question - no snark.
I guess people are stuck with this "eclipse is slow" opinion
It makes sense to be stuck with it when it comes from recent personal observations.
On the desktop? Minecraft? Azureus? IntelliJ IDEA? OpenOffice? NetBeans? SoapUI?
If you're looking for substantially more complexity than these sorts of things though then there aren't really any desktop examples that come to mind. It's all server side stuff.
Sure there is! You can run out of memory!
You're obviously not familiar with Java then. It's a computer program running inside a virtual machine. The JVM's maximum heap size is set at startup via a command line switch.
So far almost all the comments are about Eclipse as an IDE, which may be its biggest application but not the only one. I have used it as a platform for other applications, IBM's scheduler IIRC. It was familiar and the MDI nature (multiple document interface/overlapping child windows) made presenting a lot of information and options easy and accessible. It may not be the easiest to develop components for or the best organization method, but it beats the pants off a poor implementation. I wish those who can't do environments well would stop trying and implement on top of eclipse, at least they'd be consistent.
http://www.eclipse.org/communi...
http://wiki.eclipse.org/Rich_C...
P.S. kudos to eclipse for keeping the hot-keys alive, very usable w/ limited mouse required; a plus in my book.
"Happy families are all alike; every unhappy family is unhappy in its own way." -- Anna Karenina by Leo Tolstoy
Touché
It needed 2G of RAM 5 years ago... and growing. emacs has handed the bloatware crown on.....
mark, remembering brief
It's just the way Java works, and Eclipse is all Java. To make it work like any other program just set the min heap size small and the max heap size huge.
(Smalltalk was the same. Ah Smalltalk, I knew thee well.)
XML is a known as a key material required to create SMD: Software of Mass Destruction
C++ can do it too. Read about HP Project Dynamo.
'Modern' coding using Design Patterns I guess. Too much cruft in code like that.
So since when did Visual Studio get decent refactoring support out of the box?
Why is it recomended you don't uninstall plugins you no longer want to use? Does it have to be that unstable?
Dependencies I bet.