<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nicolas Fränkel on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/nicolas-fr%C3%A4nkel/</link><description>Recent content in Nicolas Fränkel on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 04 Jun 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/nicolas-fr%C3%A4nkel/index.xml" rel="self" type="application/rss+xml"/><item><title>Comparing transitive dependency version resolution in Rust and Java</title><link>https://javapro-en.svenruppert.com/comparing-transitive-dependency-version-resolution-in-rust-and-java/</link><pubDate>Thu, 04 Jun 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/comparing-transitive-dependency-version-resolution-in-rust-and-java/</guid><description>&lt;p&gt;You learn by comparing to what you already know. I was recently bitten by assuming Rust worked as Java regarding transitive dependency version resolution. In this post, I want to compare the two.&lt;/p&gt;
&lt;h2 id="dependencies-transitivity-and-version-resolution"&gt;Dependencies, transitivity, and version resolution&lt;/h2&gt;
&lt;p&gt;Before diving into the specifics of each stack, let&amp;rsquo;s describe the domain and the problems that come with it.&lt;/p&gt;
&lt;p&gt;When developing any project above Hello World level, chances are you&amp;rsquo;ll face problems that others have faced before. If the problem is widespread, the probability is high that somebody was kind and civic-minded enough to have packaged the code that solves it, for others to re-use. Now you can use the package and focus on solving your core problem. It&amp;rsquo;s how industry builds most projects today, even if it brings &lt;a href="https://en.wikipedia.org/wiki/Supply_chain_attack"&gt;other problems&lt;/a&gt;: you sit on the shoulders of giants.&lt;/p&gt;</description></item><item><title>Langchain4J Musings</title><link>https://javapro-en.svenruppert.com/langchain4j-musings/</link><pubDate>Fri, 13 Jun 2025 09:10:26 +0000</pubDate><guid>https://javapro-en.svenruppert.com/langchain4j-musings/</guid><description>&lt;p&gt;I’m coming relatively late to the LLM party, but I rarely come very early in the hype cycle.&lt;/p&gt;
&lt;p&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://upload.wikimedia.org/wikipedia/commons/9/94/Gartner_Hype_Cycle.svg" alt="Gartner hype cycle" loading="lazy" decoding="async"&gt;
 
 &lt;figcaption&gt;Gartner hype cycle&lt;/figcaption&gt;
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;For example, I never bought into blockchain, the solution still searching for problems to solve, nor in microservices, the latest in the cargo cult IT trends. Despite my late arrival at the LLM party, I have been a regular user of LLMs. I use OpenAI for non-controversial questions outside my cone of knowledge, &lt;em&gt;e.g&lt;/em&gt;., linguistics or legal; I use GitHub Copilot in my IDE to improve my code.&lt;/p&gt;</description></item></channel></rss>