Skip to content

Commit 64332b2

Browse files
committed
Fix links
1 parent 5873328 commit 64332b2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/blog/2025/20250211-welcome-java-21.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ tags: ["Java"]
66

77
2025-02-11 by Frank Delporte
88

9-
_**The development of the Pi4J library faced a decision point...: "_Should we stick to Java 11 for existing projects and old Raspberry Pi's ([with ARMv6](/documentation/java-for-arm/)), versus moving on and making use of better and more performant Java code with the latest Long Term Support (LTS) version?_"**_
9+
**The development of the Pi4J library faced a decision point...: "_Should we stick to Java 11 for existing projects and old Raspberry Pi's ([with ARMv6](/documentation/java-for-arm/)), versus moving on and making use of better and more performant Java code with the latest Long Term Support (LTS) version?_"**
1010

1111
We actually wanted to move on to Java 22, as it brings a new way of interacting with C-code, thanks to [JEP 454: Foreign Function & Memory API](https://openjdk.org/jeps/454). As this is the core behavior of Pi4J to interact with the GPIOs, it would make it much easier to implement new ways to control electronics, as confirmed [with a first test by Robert "Eitch"](https://github.com/eitch/pi4j-test/blob/develop/src/main/java/ch/eitchnet/pi4j/test/LibGPIODController.java). But as Java 22 is not an LTS release, we won't make this move yet.
1212

0 commit comments

Comments
 (0)