Brief Overview of the IDE landscape
If you’re just joining the conversation, then you probably know quite well that IDE stands for Integrated Development Environment, and is most likely one the first tools you learned how to use (unless vi was more your style). IDEs emerged in order to give developers working on more complex applications more of a feature-rich experience. At least, more than a glorious notepad capable of opening multiple documents at the same time.
This report is ultimately a quick guide for learning the shortcuts and, to an extent, a bit more about the features, of Eclipse, IntelliJ IDEA and NetBeans. Our goal here is to help you learn your current IDE better, so that you can be more fluent or learn new features. We also hope you’ll get a decent snapshot of other IDEs and how things are done elsewhere, in case you decide to ever switch some day.
BOSTON – Nov. 4, 2014 – ZeroTurnaround, the maker of revolutionary tools for developing quality software faster, today announced the availability of JRebel 6, the first major release of its flagship product to feature full integration of Javeleon technologies, acquired by ZeroTurnaround in March 2013. Now Java developers can create higher-quality code even faster, and with less downtime, from the superclass functionality and superior infrastructure available in JRebel 6.
IDEs vs. Build Tools: How Eclipse, IntelliJ IDEA & NetBeans users work with Maven, Ant, SBT & Gradle
In our recent Java Tools & Technologies Landscape for 2014, over 2000 developers told us a bit about what JVM technologies they use and which tools are interesting to them. From that, we produced a gorgeous, professionally-designed, 60-page report (which you can download) on 14 technology segments. We recently dug deeper into users of Spring MVC, JSF, Vaadin and GWT and the post ended up being really popular.
So we wanted to do the same with IDEs—and got so much awesome data that we needed to continue to break it down into tool segment from there!
ZT Surpasses 100 Customers Milestone in Less than Three Months; Popularity of New Product Illustrates the Growing Interest in Code-Level Testing and Alerts
If a non-developer asked you “What is Java?”, how would you respond? could you answer questions from a muggle about how new features get added, who decides what features do or don’t make it to future versions, and how does a team of dedicated Java platform engineers and random developers around the world influence the language? Have you ever wondered what the whole “Java” thing is really about, and why, for Pete’s sake, did it take so long to get lambdas into Java…
BOSTON – Sept. 22, 2014 – With JavaOne just around the corner, RebelLabs is pleased to announce the publication of its latest community resource, “A Short History of Nearly Everything Java” a comprehensive guide on the Java process, community and history overview of key Java events and innovations.
Believe it or not, Java developers don’t consider build tools to be the most interesting topic out there. They are generally not considered the most exciting segment of any developer’s overall utility belt.
After all, the majority of the dev world still chooses between just two build tools, Maven and Ant, the latter of the two having been created nearly a generation ago. At best, programmers would prefer their build tool remain invisible and stable; at worst, we hear complaints of downloading enormous libraries, scripts failing for no reason due to some invisible rule running in the background, and general annoyances.
However, build tools should still be able to rock, and it’s in the spirit of “Build Tools [Can] Rock!” that RebelLabs has set out to finalize our journey into the realm of Java’s three most popular build tools–Maven, Gradle and Ant (along with Ivy for managing dependencies). After all, if anyone was going to try to put it a little “sexy” back into Ant, it would be us ;-)