Eclipse Ganymede
If you've never looked at Eclipse and you work with multiple programming languages or multiple platforms, take some time to try Eclipse.
Be prepared. Eclipse is a large, complex tool, and you won't grok it if you invest only 15 minutes. In addition to being large and complex, Eclipse's roots are at IBM, and it's big in the Java world, so there's a bit of "Blue-Speak" and "Enterprise-Speak" to deal with at times (and, of course, XML).
Most IDEs come with built-in “support” for lots of programming languages. Although for a lot of them, support means it colorizes your code. Eclipse is a bit different. It doesn't come with built-in support for many languages, or any, depending on the version you download. Support is provided via Eclipse Plugins. And normally, “support” means more than just colorizing your code. You usually get something that understands your language. It can show you an outline of the functions and data in your code; it can help you refactor code; it can show where something is defined, and it integrates with the language's debugger.
Eclipse is not without its annoyances. Perhaps the most annoying is that it's only an IDE and not a text editor. Of course it edits text, but it's not a general-purpose text editor. If you want to open a file that's not part of a project, it's a bit cumbersome. There's no filesystem browser, and the open dialog doesn't remember the directory that you used last time. And, if you don't have a plugin for the file type you open, you don't get any code colorizing. So, you often end up using Eclipse for your “projects” but then using another text editor to look at files that aren't part of your project.
If you develop only C++ applications for KDE on Linux, or only XXX applications for YYY on ZZZ, there might be a better IDE than Eclipse. However, if you use multiple languages and/or multiple systems, and you want to use only a single IDE, there's no better IDE than Eclipse. And, even if you use only one language on one system, Eclipse sets the bar pretty high.
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
| Trying to Tame the Tablet | May 08, 2013 |
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Home, My Backup Data Center
- New Products
- Tech Tip: Really Simple HTTP Server with Python
- RSS Feeds
- Connecting Android device to desktop Linux via USB
22 min 31 sec ago - Find new cell phone and tablet pc
1 hour 20 min ago - Epistle
2 hours 49 min ago - Automatically updating Guest Additions
3 hours 58 min ago - I like your topic on android
4 hours 44 min ago - Reply to comment | Linux Journal
5 hours 5 min ago - This is the easiest tutorial
11 hours 20 min ago - Ahh, the Koolaid.
16 hours 58 min ago - git-annex assistant
22 hours 58 min ago - direct cable connection
23 hours 20 min ago
Enter to Win an Adafruit Prototyping Pi Plate Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Prototyping Pi Plate Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- Next winner announced on 5-21-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.



Comments
Thanks for letting us know
Thanks for letting us know about this and I hope to read more from you. Keep the posts coming!
Multivitamins
Eclipse may be idiosyncratic
Eclipse may be idiosyncratic for some things. But, in general, it doesn't need a lot of time to learn the ropes and begin to appreciate the lack of coupling between all the various components and plug-ins that Eclipse allows you to bring together into a strong, process-driven development environment. When it comes to integrating strong process, from check-out, library dependency resolution, artifact creation and maintenance, to integrating easily and painlessly with continuous integration systems (essentially by re-using the same Ant scripts used for building the project within and outside the IDE), you'd be hard-pressed to match the flexibility provided by Eclipse.
Of course blogging and
Of course blogging and social networking complement each other, and blogging's still relevant. After all, all the major social networking sites include blogs as part of your account. Not to mention the fact that Boutin seems to ignore that you can copy and paste embed code to put images and video in your blog.Now, I agree that people shouldn't expect blogging to make them an instant celebrity any more. It's also true that if you just want to write about the minutiae of your day, you're better off blogging on your MySpace or Facebook account, wholesale lingerie where your musings will be easily accessible by friends who actually care. But there is still a subset of people for whom a non-social-network blog is a perfectly viable option.
Good Program
Very good program and software.
Eclipse v/s NetBeans
I used to like NetBeans - even prefer it over Eclipse for quite some time. Especially when they introduced first-class support for Ant as a project manager. However, although first-class support is great, you don't always want the build-script that tied up with the development environment as NetBeans manages to do it now. With this level of coupling, the build-script is no longer usable outside the IDE - a major reason for using something like Ant in the first place.
Eclipse may be idiosyncratic for some things. But, in general, it doesn't need a lot of time to learn the ropes and begin to appreciate the lack of coupling between all the various components and plug-ins that Eclipse allows you to bring together into a strong, process-driven development environment. When it comes to integrating strong process, from check-out, library dependency resolution, artifact creation and maintenance, to integrating easily and painlessly with continuous integration systems (essentially by re-using the same Ant scripts used for building the project within and outside the IDE), you'd be hard-pressed to match the flexibility provided by Eclipse.
Flexibility does indeed ask a price of you, the user. But in development environments, flexibility is very important.
What was the point of this article? Filler?
So the entire point of the article can be boiled down to:
"If you haven't tried Eclipse, then you should"?
Nothing more to say about arguably one of the most complex Java projects that continues to grow organically (and require more disk/memory with each plug-in or new version)?
Looks like somebody had to meet an editorial deadline and nothing to write about.....
"Be prepared. Eclipse is a
"Be prepared. Eclipse is a large, complex tool, and you won't grok it if you invest only 15 minutes."
As they say time is a valuable thing.
Which is exactly why I use NetBeans and vi for fast quick edits.
Yes you cannot comprehend and become proficient with vim in 15 minutes; however
it takes about 5~10 minutes to become pretty comfortable with NetBeans.
I think and obviously it is my personal impression, Eclipse design is unnecessary complex for the end-user. The shortcuts are hard to find, un-intuitive (similar to Emacs in complexity) and overall design is largely botched.
If you want to dedicate your life studying Eclipse and how to circumvent-n-overcome its gotchas (which abound, for instance maintaining projects on a mounted/remote file system) - sure - go ahead.
If you want to write software and finish your projects - you owe it to yourself to try NetBeans :o)
I am not affiliated with neither IBM nor Sun Microsystems.