With this post, we continue the series of one-page cheat sheet for Java developers. This time we’ll look at everyone’s favourite topic, regular expressions! Often seen as the tool capable of solving almost any problem, but all too often it’s just a source of other issues.
We’ve gathered the data at the following services: StackOverflow, LinkedIn, GitHub, and Google search, and unified it through a simple, but effective ranking formula. And we rank some of the most prominent Java web frameworks according to this popularity index.
Last week we published a short Java challenge that required you to make javac generate the smallest Java class possible.
It got a pretty good response, quite a few of the readers decided to stretch their javac knowledge and try their hands on the challenge.
In this post, I’d like to show you a couple of solutions that I got from our readers.
Spoiler alert! If you want to see whether you can convince javac to generate a smaller class file, this is the right time to stop reading and open your terminal.
Today, however, I’d like to pose you a code-golf like challenge:
What’s the smallest Java class you can generate using javac (any vendor, any release)?
In this post, I’ll list the libraries which we learned about in the latest Virtual JUG session: The JavaFX Ecosystem by Andres Almiray. Andres has presented on the Virtual JUG before; you might remember his excellent session on how to use Gradle effectively.
The session focused on the open source JavaFX libraries that offer something that you often need in a project. And it was organized by topic: layout, testing, icons, and so on. So we’ll follow that path and cover the JavaFX libraries that Andres gave a shout out to. Disclaimer, this is not the full list of the libraries in the JavaFX ecosystem! But it’s a great place to start if you’re new to JavaFX, or if you have some experience with it and want to get better.
This post continues our series of one-page printable cheat sheets about Java and related technologies that we’ve been producing for almost a year now.
Today it’s all about Java generics. The feature was added to Java 10 years ago, and even today it still confuses many Java developers.
This post continues with the series of the cheat sheets that we’ve been producing all year. And this time it’s all about Spring Framework annotations. We look at the annotations that make Spring a flexible, but at the same time a very stable choice of a framework.
You can find tons of tutorials about how you should use Spring — its configuration and a myriad of excellent Spring projects on the internet. We, however, want to provide a one-page reference for the most commonly used annotations. With this, you will always remember which annotations go where. Here we go!
A couple of months ago, we released our annual Developer Productivity Report, where we looked at the results of asking Java developers about what tools and technologies they use. Among all kinds of cool findings, like what IDE is the most popular, whether microservices offer a salvation from solving hard problems, and so on, we got the data about the web frameworks our respondents use.
We saw that both Spring and Java EE are pretty popular choices, and the general consensus is that both are quite excellent. That realization made us ask a deeper question. What components of the platform do you actually use?
In this post we analyze the data we gathered to answer that question
RebelLabs is the media partner for the Virtual JUG, the online Java User Group which brings you the best sessions by world class speakers. The best part? You don’t have to leave your house or office to enjoy them! You can educate yourself and become a better developer even from the comfort of your home!
This time I want to recap a magnificent session we had just recently: “Java 8 Puzzlers: The Strange, the Bizarre, and the Wonderful”. The speakers who brought it to our screens are two established experts in the Java community: Baruch Sadogursky and Viktor Gamov.
Well, if for the last ten years you haven’t been living under a rock, or not on the JVM, you probably have at least some experience with JUnit. You’ll know it’s the most used library to write unit tests in for Java projects.
JUnit is quite mature and is pretty good as libraries go, however recently, after the release of the JDK 8, the JUnit team worked hard and delivered a major rewrite of the test engine. One of the main syntactical reasons was to adopt lambdas, so you can write code that is full of them and benefit from unit tests that use a similar code style. However, the differences between JUnit version 4 (or older, if you’re still half under the rock) and the fresh version 5 do not stop there.