<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Michael Gasche on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/michael-gasche/</link><description>Articles written by Michael Gasche on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Jul 2024 07:26:01 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/michael-gasche/index.xml" rel="self" type="application/rss+xml"/><item><title>beetRoot: Yet Another Web Framework?</title><link>https://foojayio.github.io/website/today/beetroot-yet-another-web-framework/</link><pubDate>Tue, 02 Jul 2024 07:26:01 +0000</pubDate><guid>https://foojayio.github.io/website/today/beetroot-yet-another-web-framework/</guid><description>&lt;p&gt;&lt;em&gt;News: beetRoot 3.2.0 was released on December 8, 2025&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Over the years, I have struggled with various Java web development frameworks and they all have their weaknesses and strengths.&lt;/p&gt;
&lt;p&gt;A few years ago, I evaluated around 10 of these frameworks for a project for a Swedish company. Nothing really impressed me at the time.&lt;/p&gt;
&lt;p&gt;It was only later that &lt;a href="https://spring.io/projects/spring-boot" target="_blank" rel="noopener noreferrer"&gt;SpringBoot&lt;/a&gt;
 came along, which seemed to fulfill all the requirements and there was actually very little to criticize about it. Then came microservices such as &lt;a href="https://quarkus.io/" target="_blank" rel="noopener noreferrer"&gt;Quarkus&lt;/a&gt;
 or &lt;a href="https://micronaut.io/" target="_blank" rel="noopener noreferrer"&gt;Micronaut&lt;/a&gt;
, which are often compiled into native code for small web service applications, but which can then rarely be embedded in a more mature architecture.
&lt;img src="https://raw.githubusercontent.com/autumoswitzerland/autumo-beetroot/master/web/img/autumo-beetroot-login.webp" alt="beetRoot starting on console" loading="lazy"&gt;
&lt;/p&gt;</description></item><item><title>Building JavaFX with Gradle</title><link>https://foojayio.github.io/website/today/building-javafx-with-gradle/</link><pubDate>Thu, 05 Jan 2023 11:32:24 +0000</pubDate><guid>https://foojayio.github.io/website/today/building-javafx-with-gradle/</guid><description>&lt;p&gt;Usually Maven is my build tool of choice and for Java front-ends I sometimes still build a front-end application using ANT, Swing with Oracle&amp;rsquo;s JDK 8u202 and JDK 8&amp;rsquo;s Java Packager, but don&amp;rsquo;t tell anyone&amp;hellip;.&lt;/p&gt;
&lt;p&gt;Over time, as I wanted to move forward with some more lightweight front-ends, I started building JavaFX applications.&lt;/p&gt;
&lt;p&gt;Of course, I don&amp;rsquo;t want to lock customers into JDK maintenance contracts; for backend software and servers, where the customer usually has their own runtime architecture, that&amp;rsquo;s easy, but for GUIs, I generally don&amp;rsquo;t want to ship a full JDK anymore, I want to use modular Java, ship a JDK of my choice, and provide a proper build system for it all. So that&amp;rsquo;s it, I use the following components and software:&lt;/p&gt;</description></item></channel></rss>