Elder Moraes @elderjava

Helping @java developers to build and deploy the best software in the industry. @Java_Champions. Published author. Board member @soujava. eldermoraes.com At some JVM out there Joined March 2016

Tweets

9K
Followers

8K
Following

876
Likes

7K

Elder Moraes @elderjava

23 hours ago

So the real call for a Java team: you get Docling-grade parsing without rewriting your RAG pipeline in Python. Orchestration, observability and security stay in your JVM stack. The cost you take on is running docling-serve. Weigh it against the parse fidelity. 5/5

0 0 1 56 0

View Details

Elder Moraes @elderjava

23 hours ago

What you run underneath: Docling itself runs as a docling-serve instance. The LangChain4j integration is a Java REST client for it, built on the official Docling Java library. You operate a separate service and point the parser at its endpoint. 4/5

1 0 0 57 0

View Details

Elder Moraes @elderjava

23 hours ago

@langchain4j 1.15.0 shipped an integration with #Docling, @IBM Research's document parser. If you build #RAG in @java, it lands on the messiest stage of the pipeline: getting clean text and tables out of real PDFs and DOCX. 1/5

1 1 4 376 1

View Details

Elder Moraes @elderjava

a day ago

Hi @bcherny! Claude Code plan mode still asks permission for trivial stuff (ls, grep, find). Anyway to make it more confident?

0 0 0 183 0

View Details

Thariq @trq212

2 days ago

Workflows are the biggest upgrade to Claude Code’s capabilities since skills and subagents. I dove deep into it with @sidbid to figure out best practices, examples and more. I’m particularly excited about the non-technical tasks it enables for Claude Code.

Thariq @trq212

2 days ago

x.com/i/article/2061…

208 1K 9K 2.4M 21K

162 336 4K 911K 8K

View Details

Elder Moraes @elderjava

2 days ago

A change to the default object layout can move your cost per pod more than another framework rewrite will. It's unglamorous, it ships inside the platform you already run, and RDP1 for JDK 27 begins June 4. 6/6

0 0 1 95 0

View Details

Elder Moraes @elderjava

2 days ago

The catch with any default is that it moves your baseline quietly. Heap sizing, GC behavior, and footprint numbers all shift under you. Re-measure on your real workload before you trust the new defaults in production. 5/6

1 0 0 98 0

View Details

Elder Moraes @elderjava

2 days ago

JDK 27 forks from the main line on June 4. Two JVM defaults flip in this release, and both change what a Java service costs to run in a container. Neither asks you to touch a line of code. 1/6

1 2 8 839 2

View Details

Elder Moraes @elderjava

3 days ago

So the senior read on JDK 27: the header and GC defaults move real production numbers the day you upgrade, with no code edits. The Vector API stays a feature to keep watching while it incubates. Know which column a JEP sits in before you build a roadmap around it. 7/7

0 0 0 84 0

View Details

Elder Moraes @elderjava

3 days ago

Now the contrast: JEP 537 takes the Vector API into its twelfth incubation, with no substantial changes since JDK 25, after eleven rounds across JDK 16 through 26. Twelve incubations and still not standardized. That is the 'almost here' column. 6/7

1 0 1 83 0

View Details

Elder Moraes @elderjava

3 days ago

JDK 27 reaches general availability on September 14. Two of its JEPs change your memory footprint and GC behavior with zero code change. A third headline feature is entering its twelfth incubation. Telling those two groups apart is the actual senior-dev read. 1/7