Our webinar series Devs@Home brings IT experts into your (home) office. On Thursday, May 14th at 13:00 CEST, Ram Lakshmanan will be putting 7 JVM arguments (out of over 1,000 in total) into the spotlight and showing us how they can be useful when coding our applications.
Text blocks were added to Java as a preview feature in JDK 13. With JDK 14 the feature was previewed for a second time with the addition of two more escape clauses. Now, text blocks will be a full-fledged feature in JDK 15 because the community is in agreement: text blocks are ready. Let’s take a closer look.
A competitor recently published a microbenchmark comparing the performance of their stack to Quarkus. The Quarkus team feels this microbenchmark shouldn’t be taken at face value because it wasn’t making a like-to-like comparison leading to incorrect conclusions. Both of the two frameworks under comparison support reactive processing. Reactive processing enables running the business logic directly on the IO thread, which ultimately performs better in microbenchmark focusing on response time and concurrency. The microbenchmark should have been written so that both frameworks (or neither framework) obtain this benefit. Anyway, this turns out to be a very interesting topic and good information for Quarkus users, so read on.
Every month, we take a look back at our top ten most clicked topics. Last month was packed full of exciting stories, interviews, and new releases: We welcomed the new versions of Visual Studio Code and Node.js, looked into trending programming languages and GitHub projects, and highlighted seven important JVM arguments.
The monthly update for Java on Visual Studio Code has arrived from Microsoft. The April 2020 update includes support for Java 14, new performance upgrades, previews for proposed upcoming changes, and much more. See what’s new.
Another month, another update to the TIOBE Index. The Index tracks the popularity of programming languages according to search engine results. This month, C moved up past Java and entered the number one position.
Every Monday, we take a step back and look at all the cool stuff that went down during the previous week. Last week, Quarkus 1.4.1.Final arrived—and it deprecated the still widely used language version Java 8. We also got to know the new Project Leyden and spoke to Rust core developer Steve Klabnik.
Quarkus 1.4.1.Final arrived with several new features. This version deprecates Java 8; users are now recommended to use Java 11. It also introduced a new FaaS framework and a new command mode for building command line apps.
Chief Architect of the Java Platform Group at Oracle, Mark Reinhold, has written a call for discussion proposing a new project, Project Leyden, that will address the long-term pain points of Java’s slow startup time, slow time to peak performance, and large footprint. It will do this by introducing static images to the Java platform and JDK. Let’s take a closer look.
Our new webinar series Devs@Home brings IT experts into your (home) office. On Thursday, April 30th at 13:00 CEST, Thorben Janssen will show us how to use lesser known features of Hibernate to implement common features, such as generating UUIDs as primary keys, quickly.
Almost there – Garbage collection with the Z Garbage Collector is almost completely free of infamous safepoint operations. Stack processing is the only thing not really running in a concurrent phase yet. JEP 376 addresses exactly this problem and should finally put an end to unnecessary pauses. Let’s take a closer look.
Every Monday, we take a step back and look at all the cool stuff that went down during the previous week. Last week, we launched our big DevOps survey, found out how to integrate Python with Java, and learned how to keep networks secure while working remotely. We also took a deep dive into the MVC web framework Go-Web.
Shenandoah has been part of the JDK since Java 12. When it was integrated, it was given experimental status similar to Epsilon GC and ZGC. JEP 379 proposes to change its status from experimental to production – and it will get its way, since JEP 379 is officially targeted to JDK 15. Let’s take a closer look.
