Android & Java both have quite similar APIs. Naturally, the benefit of Android & Java’s APIs being similar is that it makes it possible to develop frameworks and libraries that work on both platforms. This blogpost takes a look at seven Android libraries which Java developers should at least know about. Also, it’s a good post for Android developers to be aware of too, just in case there are some libraries you may not be aware of.
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…
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 ;-)
The Wise Developers’ Guide to Static Code Analysis featuring FindBugs, Checkstyle, PMD, Coverity and SonarQube
Chapter I: Welcome to static code analysis, that thing you aren’t doing
“The quality of your code is a weak spot in almost every software project you’ll ever touch. This is because ongoing development ensures that even the bits you were once proud of become, over time, first less elegant, then rough, and finally incomprehensible.”
— Oleg Shelajev, Java Developer/Author
[publication id=”87″ label=”Read it later! (PDF download)”]
Java Build Tools: Part 1 – An Introductory Crash Course to Getting Started with Maven, Gradle and Ant + Ivy
Build tools are an integral part of what makes our lives easier between checking code in and testing your product. Love them or hate them, they’re here to stay so let’s first take a look at what they are, how they emerged and why they are both hated and revered today.
Introduction: Let’s get even more curious
In the Curious Coders Java Web Frameworks Comparison we looked individually at the top 8 most popular Java Web Frameworks at a feature-by-feature level and scored them. We got some great feedback and added two more feature categories based on this commentary, plus analyzed the strengths and weaknesses of each framework against seven different application types (use cases)…
People love Eclipse, or love to hate it, or, as non-geek coders, feel more or less indifferent about their IDE. However one thing is true–the majority of Java and Java EE developers use Eclipse. This RebelLabs report starts shallow and goes deep into orbit around the ecosystem of Eclipse, showing you the best things that Eclipse has to offer, and letting you know how to turn off some of those annoying bits (“Why does content assist keep asking me about awt??!?!”). From packaged solutions to plugins and customizations, it’s all in here, from n00b to ninja in 40 pages.
The Ultimate Java Web Frameworks Comparison: Spring MVC, Grails, Vaadin, GWT, Wicket, Play, Struts and JSF
In this latest report from Rebel Labs, we match up Spring MVC, Grails, Vaadin, GWT, Wicket, Play, Struts and JSF in a comparison of the top 8 most used Java Web Frameworks in the industry today. We wanted to know more about simple Market Share % and latest versions. After all, wouldn’t you want to know about the following abilities/features of a framework you’re testing?
1. Rapid application prototyping
2. Framework Complexity
3. Ease of Use
4. Documentation & Community
5. Framework Ecosystem
7. Code Maintenance/Updates
8. UX, Look and feel
Will the big guys like Spring MVC, JSF and Struts dominate the show? Or are smaller players like Vaadin, Grails and GWT going to finally trump their predecessors? Either way, you’ll be left with a pragmatic guidebook to gauging whether certain frameworks will be right for your next project. Stay tuned for a Part II report, which compares the same frameworks against different use case, application types and user profiles. Follow it all @RebelLabs on Twitter.
This is the third post in our review of Java web frameworks, having already covered Vaadin and Grails. Today we look at Spring MVC, a web framework and module of the larger Spring Framework, also by Pivotal (like Grails). According to our latest Developer Productivity report, Spring MVC is the most commonly used web framework among Java developers, accounting for 30% of the market.