Another version, another milestone. The last update post was back in April about JRebel for Android 2.2. In this post you’ll get the highlights over the last 46(!) releases.
With all the latest improvements, you’ll want to try JRebel for Android even if you’ve already tried it in the past. Just search for JRebel for Android in the Android Studio or IntelliJ plugin repository and install it for free!
JRebel for Android instantly pushes your code and resources changes to your running Android app during development. It’s like Instant Run with a hyperdrive. In case you did not know, JRebel for Android has a Free version as well as an Enterprise version. Today we’ll take a look at the features that come with the Free version. More specifically, how it allows you to speed up your development flow.
JavaOne is the major conference on the Java technologies scene, held annually in San Francisco. The first time I attended JavaOne was in 2007 and it was huge! The event was located in Moscone Center and thousands of people came to learn about the latest and greatest updates in Java.
If somebody asked about the Gradle feature that everybody should know about, I would probably point them towards buildSrc. It is a magic Gradle Java/Groovy project inside your repository, available as a library to all of your
This approach allows you to write code in your favorite JVM language and to use it right there in your build scripts. As a bonus, you can also cover trickier parts of your build logic with unit tests!
Java 9 is finally here
After many delays, we finally get our hands on Java 9, along with its new features and improvements!
One of the greatest and most talked about new features in Java 9 is the Java Platform Module System (previously known as Project Jigsaw). Not only has the Java runtime been split into individual modules, Java now also supports the creation of your own modules and declaring their interdependencies. This can now be done without the use of a third party module runtime (like an OSGi container). The module system also introduces stricter access checks for compile time, runtime, and reflection. Public is no longer public! You can now have classes that are public to other classes in your module — and only your module — as well as limit how classes in other modules can manipulate your private state using reflection.
Welcome to the Java Tools and Technologies Landscape Report 2017! This is an analytical report, based on an online survey of the Java community about the tools that teams and developers use, popularity and reasons for using these tools, architecture choices and so on.
For this year’s report, we focused on why Java developers use the tools they use and how satisfied they are with their choices in tools, architecture, and so on.
Download the PDF version of the report (in excellent quality):
GET THE REPORT!
RebelLabs Developer Productivity reports are analytical reports based on online surveys of Java developers. Over the last 6 years, we reported on the ecosystem landscape, performance tooling choice, software development quality and predictability, and so on. One of our main reasons for writing the reports is to understand how the Java developer community evolves, which tools they use and the current trends.
This year’s report focuses on why Java developers use the tools they use and how satisfied they are with their choices in tools, architecture, and so on.
The data for this report comes from the results of a public RebelLabs survey that we ran in May-July 2017 which received about 2060 responses.
We analysed the data and all the findings are publicly available in the main report blog post.
However, this year we decided to share the data we gathered as well as the analysis. This way you can always check the claims, do additional research, or just play with the data to generate pretty graphs about your favorite tools.
Oh em gee! Traditional performance management is broken, who broke it?!? Well in all honesty, it has always been broken because, most companies don’t start thinking about performance monitoring until the application is in production. In fact, we’ve found that over 75% of the application performance issues make it to production where customers experience them. Just imagine if we did this with our QA issues.