r/foojay • • 2h ago

Lottie4J 1.3.0 and 1.4.0 are out, with better parsing and full writing of Lottie files

2 Upvotes

On Foojay, u/FrankCodeWriter covers two Lottie4J releases that came out of work on AnimatorFX, Dirk Lemmermann's application that imports Lottie animations through the library.

1.3.0 loads real-world files that don't follow the spec, such as expressions, unknown layer types and bare number properties. It


r/foojay • • 2h ago

Which JDK are you on and what stops you from upgrading?

2 Upvotes

We asked the Foojay Slack community which JDK they run in production and what holds them back. Dominika Tasarz wrote up the 14 replies (not a survey), which ranged from JDK 21 and 25 to one team on 27 and a speaker using 28 early access.

The blockers were mostly not about Java itself. They were about checking that frameworks, libraries and production environments still work together. The article also covers why "LTS only" is not the same as "supported", how Renovate and OpenRewrite help with upgrades, and why quarterly updates are worth checking.

Which JDK are you on, and what keeps you there? Read the article here: https://foojay.io/today/which-jdk-are-you-on-and-what-stops-you-upgrading/


r/foojay • • 1d ago

Shopify Was Wrong and Right to Dump React Native, by Shai Almog

3 Upvotes

On Foojay, we published an article by Shai Almog on Shopify's decision to move its mobile apps off React Native and rewrite them in Swift and Kotlin.

Shai argues that React Native deserved to go because it is a heavyweight UI toolkit, which hands your widgets to the OS and the vendor skin. He cites a Samsung keyboard issue that can hang a text field as one example. His view is that replacing it with two native codebases doubles the costly parts, which are platforms, testing and store churn, and that AI makes each of them worse.

The article also covers the heavyweight versus lightweight toolkit split, and the cold start and crash-free numbers Shopify reported after its rewrite.

Read the full article here: https://foojay.io/today/shopify-was-wrong-and-right-to-dump-react-native/


r/foojay • • 1d ago

Passion Project Contest: share what you built and why, win €500

2 Upvotes

We just published details of the Passion Project Contest, written by Maaike van Putten. It is a free contest for developers who built something because it annoyed them, seemed like a good idea, or simply made them happy. The tech implementation is not judged, and any language or stack is welcome. The focus is on what you made, why, who it helps, and what you learned.

A jury of developers, including Java Champions, picks five projects for a showcase video. Jury and public each count for 50% of the vote, and the winner gets €500. Every entrant gets free access to the live seminar Self-advocacy for developers.

You can enter if you are 18 or older, build software, and live in the EU, EEA, UK, or Switzerland. The deadline is 31 December 2026.

https://foojay.io/today/passion-project-contest/


r/foojay • • 2d ago

Build a full-stack web app using only Java, in 5 small classes

3 Upvotes

On Foojay we published a new article by Hyyan Abo Fakher about building a small customer app where every line is Java, screens included. No separate JavaScript framework, REST layer or second build.

The app has a side menu, a sortable table on top of a database and a validated form. It comes to five classes and one test, about 240 lines, built with webforJ. The author works at webforJ and says so in the article.

The article explains how to generate the project with the SideMenu archetype, how routing and layouts work, how to switch on JPA and H2, and how the entity uses Jakarta validation constraints.

Requirements: Java 21 or higher, Maven, a terminal and a browser.

https://foojay.io/today/build-full-stack-web-app-in-java-with-webforj/


r/foojay • • 2d ago

Porto TechHub 2026: talks on agentic AI frameworks for Java and Git 3

3 Upvotes

On Foojay, Nicolas Frankel shares his notes from Porto TechHub, held on November 10th, where he attended and spoke for the 4th year. He summarizes the talks he saw and adds his own opinion on each.

Topics covered:

  • Embabel, an agentic AI framework for the JVM, and how it compares with BPMN workflow engines
  • A talk on agentic loops built around demos of coding assistants
  • A comparison of Spring AI, LangChain4j and Embabel, with a table of capabilities
  • What's new in Git 3: SHA-256, reftable, main as the default branch, and safer bare repositories

He also explains why he goes to fewer conferences since leaving DevRel.

Read the full article: https://foojay.io/today/porto-techhub-2026/


r/foojay • • 2d ago

Small, signed, and scanned clean can still mean vulnerable: what makes a Java container secure

3 Upvotes

At Foojay, we published an article by Catherine Edelveis about a Java container image that was distroless, signed with Cosign, shipped with an SBOM, and scanned clean on 1 December 2021. It still contained log4j-core-2.14.1.jar, and Log4Shell went public nine days later.

The article goes through six common assumptions about container security and explains what each measure actually guarantees. Topics include image size, zero-CVE scan reports, distroless versus hardened images, signatures, and the limits of a secure base image. It also covers practical steps like generating an application SBOM at build time, rescanning continuously, and verifying signatures at deploy with an admission controller.

https://foojay.io/today/what-makes-java-containers-secure/


r/foojay • • 2d ago

Paging DTO Projections in Spring Data JPA: Three Approaches Compared

1 Upvotes

On Foojay, Rey Pham compares three ways to build a paged, filtered list screen in Spring Data JPA without loading full entities. The same orders screen is used each time: five columns from two tables, three optional filters, newest first.

The article covers a JPQL constructor expression in @Query, interface projections, and a generated read model built with Model Query, an open-source library. For each one it lists the trade-offs, such as strings that are only checked at runtime, duplicated count queries, optional filters written as ":x is null or ...", and nested projections that select more columns than expected.

Rey also suggests checking the SQL your own Spring Data versions generate.

Full article: https://foojay.io/today/paging-dto-projections-spring-data-jpa/

java #springboot #jpa


r/foojay • • 3d ago

One Does Not Simply Vibe-Code My Executor

4 Upvotes

On Foojay, Loic Mathieu explains what happened when a coding assistant got a real feature request for the execution engine of Kestra, an open-source orchestration platform he has maintained for almost four years. The request was to kill the other tasks in a parallel branch when one of them fails.

Three pull requests later, the code looked plausible but was still wrong, and the PR was closed. His view is that the assistant had a generic model of executors and a grep-built model of the code, but not the human one that holds the boundaries and the reasons. He then gives it his own map of where the change belongs, and it works.

https://foojay.io/today/one-does-not-simply-vibe-code-my-executor/


r/foojay • • 3d ago

JEP 515 stores method profiles in the AOT cache, with mixed long-run results

3 Upvotes

On Foojay, Sven Woltmann looks at JEP 515, which since Java 25 stores the method profiles from the training run in the AOT cache, so the JIT compiler can use them right after startup.

In his javac example, rounds 2 to 5 take 14% less time on Java 25 with the profiles than without. In the long run, the program becomes 5% slower with the profiles than without a cache after 200 rounds on Java 28. He traced the cause to the JVM source code: the profiles lose their lambda entries when the cache is written, so C2 no longer inlines those lambdas.

The article also covers how to get the profiles into the cache, how to switch them off for comparison, and how long the training run should be.

https://foojay.io/today/ahead-of-time-method-profiling/

Java #JVM #AOT


r/foojay • • 3d ago

Idempotent Spring Boot: lessons from going 0.1 to 1.1

3 Upvotes

On Foojay, Youssef Ben Henda walks through how idempotency-spring-boot-starter evolved release by release. Each version fixed a concrete failure mode, and most fixes came with a cost.

The article covers:

  • why a pod killed mid-request left a key locked for 24 hours until 0.4 split the claim and completed-record lifetimes
  • what "exactly-once" does and does not cover with join-transaction, plus a load test showing its latency cost with a small connection pool
  • support for Spring Boot 3.5.x and 4.1.x, MySQL and MariaDB, Caffeine, and WebFlux
  • the 1.0 compatibility promise, including storage key and record format

Full article: https://foojay.io/today/idempotent-spring-boot-1-1/


r/foojay • • 3d ago

Why agent tool calls run twice, and how to make that safe in Java services

2 Upvotes

On Foojay, Vishnuvardhan Reddy Kaithapuram explains what tends to break first when an AI agent moves from demo to real work. It is often not the model. A timeout, a retry, or an at-least-once queue delivers the same tool call twice, and a repeated write leaves bad data.

The article covers:

  • Building an idempotency key that names the logical operation, not the attempt
  • Claiming the key with a conditional write, storing the result, and using a lease for abandoned claims
  • A short Java sketch of the lookup, claim and complete flow
  • Running a playbook's full evaluation set before every release, tool changes included
  • Starting with the write tools

Read it here: https://foojay.io/today/agent-tool-calls-run-twice/

Java #AIAgents #Idempotency


r/foojay • • 3d ago

Java4Shell (CVE-2026-114938): what it is, who is affected, and what to do

4 Upvotes

Just published on Foojay: an article by Pavel Petroshenko on Java4Shell, a memory-corruption flaw in the hardware-accelerated Base64 decoder in OpenJDK's HotSpot VM. It affects x86-64 systems with AVX-512 enabled, and Calif showed it can lead to remote code execution.

The article explains who is affected, how the CVSS 3.1 and 4.0 ratings relate, why it is not a zero-day, and what to do now. If you run another Java distribution, check with your vendor.

https://foojay.io/today/java4shell-cve-2026-114938-what-it-is-who-is-affected-and-what-to-do-now/


r/foojay • • 4d ago

An Introduction to JSR 381, the Java Visual Recognition API

5 Upvotes

We just published an article by Geertjan Wielenga on JSR 381, the Visual Recognition API (VisRec). It is the Java Community Process standard for image classification and related machine-learning tasks in Java, and it reached Final status in February 2022.

The article explains what the API standardizes. Your code calls the javax.visrec interfaces, such as ImageClassifier, and the library that does the recognition is an implementation found on the classpath at runtime. It also shows how to use the official reference implementation built on Deep Netts, and then writes a new implementation backed by DuckDB to show how small the contract is.

Link: https://foojay.io/today/jsr-381-java-visual-recognition-api/


r/foojay • • 4d ago

I Trained a Neural Net to Play Pokémon (and Java runs the whole league)

3 Upvotes

On Foojay, Nicholas D'hondt explains how he trained a neural network to play the Pokémon Trading Card Game. It has played more than 4.2 million games against itself and other decks, and he now uses it as a sparring partner for his own decks.

The setup uses three languages. Node runs the games with an existing JavaScript engine, Python trains the net with PyTorch and PPO, and Java schedules everything with JobRunr: parallel games, training, testing, promoting winners and recovering after crashes.

The article also covers deterministic job ids, rate limiters and a port of Python's random number generator to Java. The author works at JobRunr.

Full article: https://foojay.io/today/i-trained-a-neural-net-to-play-pokemon/


r/foojay • • 4d ago

Spring Boot JPA vs JDBC: about 90 MiB less RSS in a small app

3 Upvotes

On Foojay, we published an article by Ted Kupolov comparing two versions of a small Spring Boot app that tracks GitHub stars. One uses Spring Data JPA with Hibernate, the other uses JdbcTemplate. Both run Spring Boot 4.1.1 on JDK 25 with H2 and Thymeleaf.

Across two runs in reverse order, the JDBC version used about 90 to 91 MiB less RSS, roughly 38% less. It reached its first successful dashboard response in about 3.9 to 4.2 seconds, versus 8.1 to 8.8 seconds for JPA.

The article is clear about its limits. It covers two runs on one macOS host and compares two complete application variants, not Hibernate in isolation. The takeaway is to measure before reaching for Hibernate by default on small services with simple persistence needs.

Read the full article:
https://foojay.io/today/spring-boot-jpa-vs-jdbc/


r/foojay • • 5d ago

Comparing Java formatters on Java 21 to 25: Open Java Format vs four others

8 Upvotes

On Foojay, Guillaume Laforge compares five Java formatters on JDK 25: Google Java Format, Palantir Java Format, Open Java Format, Prince of Space and Netflix jfmt. The article was prompted by Alex Abashev's post on Java formatters and his open-java-format fork of palantir-java-format.

The test suite covers 16 targeted snippets and a 1,042-line file with 86 formatting scenarios. The article compares the formatters on parser engine, minimum JDK, default line length, indentation, configurability, import handling and range formatting. It also shows side-by-side examples, such as how each one handles block lambdas and method chains.

Along the way, Guillaume found a compilation-breaking annotation bug in Prince of Space and a crash in Netflix's jfmt on empty blocks with comments. He also contributed a fix to Open Java Format and a pull request to Spotless.

Read the full article: https://foojay.io/today/comparing-java-formatters-why-open-java-format-is-my-new-favorite/

Java #JDK #CodeFormatting


r/foojay • • 5d ago

5 JVM Heap OOM Patterns You Can Reproduce on Your Laptop

4 Upvotes

On Foojay, Amit Sonar shares a set of reproducible labs for JVM out-of-memory behavior across G1, ZGC, and Shenandoah. Each scenario runs on a standard laptop without a cluster, and the repo's CI verifies them on JDK 11, 17, 21, and 25.

The article covers five patterns:

  1. Unbounded cache
  2. Oversized batch
  3. Report builder retention
  4. ThreadLocal leaks
  5. Leaked connections

For each one, it explains how to reproduce the failure, how to diagnose it (heap dump, GC log, or thread dump), and how to fix it. For example, the oversized batch fails on a single cliff in the GC log, while the ThreadLocal leak is invisible without a heap dump.

Amit also shares some observations from running the scenarios on different collectors. In his testing, Shenandoah survived the gradual cache leak much longer than G1, but a sudden oversized allocation killed it faster. He notes these are preliminary results from the repo's benchmarks, not peer-reviewed.

Every lab in the GitHub repo has a broken and fixed mode, a diagnosis guide, and a compare mode.

https://foojay.io/today/5-jvm-heap-oom-patterns/


r/foojay • • 5d ago

Who Is Actually Turning Your Java Object Into JSON? JSON-P vs JSON-B vs Jackson in Helidon

3 Upvotes

We just published an article by Jesus Aguirre on foojay about the JSON layer in Java backends, which is easy to take for granted when an endpoint returns an object and the client simply receives JSON.

Jesus built three small Helidon SE 27.0.0 applications with the same Person record, the same endpoints and the same payload. Each one uses a different JSON media integration: JSON-P, JSON-B (backed by Eclipse Yasson) or Jackson. The goal is not a benchmark, only to see what changes when the JSON technology changes.

The article explains the difference in abstraction level. With JSON-P you build and read the JSON yourself. JSON-B and Jackson both bind Java objects to JSON, so the service code looks almost identical. Adding a LocalDate field shows the difference: JSON-B produced "1995-12-08", while Jackson produced [1995, 12, 8] depending on its configuration. The abstraction removes code from your application, but the serialization decisions still exist. They just live somewhere else.

It also looks at how Helidon connects each technology to the HTTP layer and which dependencies each project pulls in.

Full article: https://foojay.io/today/who-is-actually-turning-your-java-object-into-json/