#graalvm — Public Fediverse posts

Are you still using Spring over @quarkusio Are you sure you want to use native?

Think again: https://quarkus.io/blog/new-benchmarks/

And this is BEFORE Leyden, which smashes the numbers for startup time compared to native.

#java #development #software #openjdk #leyden #performance #optimization #native #springFramework #quarkus #quarkus3 #graalvm

Are you still using Spring over @quarkusio Are you sure you want to use native?

Think again: https://quarkus.io/blog/new-benchmarks/

And this is BEFORE Leyden, which smashes the numbers for startup time compared to native.

#java #development #software #openjdk #leyden #performance #optimization #native #springFramework #quarkus #quarkus3 #graalvm

Previously I shared a blog post comparing Java JNI and FFM examples, the follow up is compiling these back to native images using GraalVM https://lofthouse.dev/2026/02/20/java-back-to-the-native/ #JNI #FFM #Native #Java #GraalVM

Previously I shared a blog post comparing Java JNI and FFM examples, the follow up is compiling these back to native images using GraalVM https://lofthouse.dev/2026/02/20/java-back-to-the-native/ #JNI #FFM #Native #Java #GraalVM

Previously I shared a blog post comparing Java JNI and FFM examples, the follow up is compiling these back to native images using GraalVM https://lofthouse.dev/2026/02/20/java-back-to-the-native/ #JNI #FFM #Native #Java #GraalVM

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

Post-OOP Imperative Functional Java.
Model the process. Not the domain.

Most Java code still asks the wrong question:
"What is this domain object?"
But production systems fail, scale, and burn because of processes, not nouns.

If your system is a sequence of irreversible steps, model it as a sequence,
not as interacting objects pretending to be immortal.

This follows ideas from Railway-Oriented Programming (ROP):
errors and decisions are values, not control-flow side effects.

Modeling the process means you can read this top to bottom
and understand exactly what happens.
No debugger. No IDE magic. No tribal knowledge.

Control flow is explicit.
You see the execution order.
Nothing hides in constructors, annotations, or overrides.

Failure is a first-class concept.
Once it fails or decides early, nothing else runs.
No exception archaeology.

Processes > Objects.
Real systems are workflows where refactoring is safe.

Steps are reordered, removed, or replaced
without collapsing a class hierarchy.
Testing is trivial, small stepwise context — even for an AI.

Feed input. Assert final result.
No mocking five layers of indirection.

GraalVM / native-friendly.
No reflection rituals.
The compiler smiles.

Objects are great for long-lived entities.
User actions, payments, rules, and failures are short-lived processes.

I model what happens,
not what pretends to exist forever.

Influenced by:
Railway-Oriented Programming,
Functional Core / Imperative Shell,
Workflow / Saga patterns,
Command pipelines,
Unix philosophy,
and value-oriented libraries like Vanilla-DI.

Don't be stuck in axioms.

#PostOOP
#ImperativeFunctional
#ProcessOverObjects
#ModelTheProcess
#WorkflowFirst
#RailwayOrientedProgramming
#FunctionalCore
#ImperativeShell
#CommandPipeline
#ExplicitControlFlow
#ValueOrientedDesign
#ProcessModeling
#FailFast
#NoExceptionArchaeology
#ComposableSystems
#NativeFriendly
#GraalVM
#NoReflection
#DeterministicCode
#RefactorSafe
#SagaPattern
#UnixPhilosophy
#VanillaDI
#ModernJava
#ArchitectureMatters

What is JBang? The Complete Guide to Java Scripting

#graalvm #groovylang #java #jbang #kotlin

https://blog.marcnuri.com/jbang-introduction

What is JBang? The Complete Guide to Java Scripting

#graalvm #groovylang #java #jbang #kotlin

https://blog.marcnuri.com/jbang-introduction

Oh, look. It's @graalvm being ~thrown under the bus~ detached from the train.

Right in time before Java 25 (LTS) has been released.

Gotta love the timing. 🤡

https://blogs.oracle.com/java/post/detaching-graalvm-from-the-java-ecosystem-train

#Java #JVM #GraalVM #ProjectLeyden

Oh, look. It's @graalvm being ~thrown under the bus~ detached from the train.

Right in time before Java 25 (LTS) has been released.

Gotta love the timing. 🤡

https://blogs.oracle.com/java/post/detaching-graalvm-from-the-java-ecosystem-train

#Java #JVM #GraalVM #ProjectLeyden

Wie verändern #SnapStart & #GraalVM die Startzeiten von Java-#Lambdas? @VKazulkin liefert reproduzierbare Messdaten, zeigt Performanceeffekte verschiedener Priming-Techniken & dokumentiert die Umsetzung mit #AWS SAM & #Quarkus.

Lese: https://javapro.io/de/entwicklung-ausfuehrung-und-optimierung-von-quarkus-web-anwendung-auf-aws-lambda/

@graalvm @QuarkusIO

Wie verändern #SnapStart & #GraalVM die Startzeiten von Java-#Lambdas? @VKazulkin liefert reproduzierbare Messdaten, zeigt Performanceeffekte verschiedener Priming-Techniken & dokumentiert die Umsetzung mit #AWS SAM & #Quarkus.

Lese: https://javapro.io/de/entwicklung-ausfuehrung-und-optimierung-von-quarkus-web-anwendung-auf-aws-lambda/

@graalvm @QuarkusIO

Developers can summon 20,000 lines of framework incantations.
But writing 100 lines of pure Java, and suddenly, their keyboards break.

Frameworks were supposed to simplify things. Instead, we’ve built microservices with the elegance of a collapsing Jenga tower. Defended layers on layers of “necessary” abstractions, all just to call a method.

Java, on the other hand?
Solid. Modern. Dangerous in the right hands.
Especially when wielded with jlink, jpackage, pr the surgical precision of GraalVM native executables.

From time to time, it’s good to step away from the glue. Touch the metal to actually feel something again.

(PS: Java Logging format still sucks. But we can’t all be perfect.) ☠️🧠💻

#PlainJava #GraalVM #MinimalismIsNotAMyth #CodeLikeYouMeanIt #coding #java #programming #developers

Developers can summon 20,000 lines of framework incantations.
But writing 100 lines of pure Java, and suddenly, their keyboards break.

Frameworks were supposed to simplify things. Instead, we’ve built microservices with the elegance of a collapsing Jenga tower. Defended layers on layers of “necessary” abstractions, all just to call a method.

Java, on the other hand?
Solid. Modern. Dangerous in the right hands.
Especially when wielded with jlink, jpackage, pr the surgical precision of GraalVM native executables.

From time to time, it’s good to step away from the glue. Touch the metal to actually feel something again.

(PS: Java Logging format still sucks. But we can’t all be perfect.) ☠️🧠💻

#PlainJava #GraalVM #MinimalismIsNotAMyth #CodeLikeYouMeanIt #coding #java #programming #developers

🚀 Call for Contributors – #JVM #Performance #Benchmarks

If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks

🧵 DM me or open a PR to get started

#Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

🚀 Call for Contributors – #JVM #Performance #Benchmarks

If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:

🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks

🧵 DM me or open a PR to get started

#Java #JVM #OpenJDK #GraalVM #JMH #Performance #OpenSource

You can download the new Java 23 #GraalVM from #IntelliJIDEA too!
#java #java23

You can download the new Java 23 #GraalVM from #IntelliJIDEA too!
#java #java23

You can download the new Java 23 #GraalVM from #IntelliJIDEA too!
#java #java23

You can download the new Java 23 #GraalVM from #IntelliJIDEA too!
#java #java23

You can download the new Java 23 #GraalVM from #IntelliJIDEA too!
#java #java23

With #Spring Framework 6.1 and Spring Boot 3.2 general availability approaching, don't miss this comprehensive blog post on "Runtime Efficiency with Spring" I have just published. #graalvm #projectloom #projectcrac #projectleyden https://spring.io/blog/2023/10/16/runtime-efficiency-with-spring

With #Spring Framework 6.1 and Spring Boot 3.2 general availability approaching, don't miss this comprehensive blog post on "Runtime Efficiency with Spring" I have just published. #graalvm #projectloom #projectcrac #projectleyden https://spring.io/blog/2023/10/16/runtime-efficiency-with-spring