<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bytecode on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/bytecode/</link>
    <description>Recent content in Bytecode on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/bytecode/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Byte Buddy vs Javassist vs ASM in 2026: Which JVM Bytecode Toolkit Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-11-jvm-bytecode-engineering-byte-buddy-javassist-asm/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-11-jvm-bytecode-engineering-byte-buddy-javassist-asm/</guid>
      <description>&lt;p&gt;Something in your JVM is rewriting class files while your application runs. It might be your mocking library stubbing a final method, your APM agent weaving timers into service calls, or your ORM generating a proxy for lazy loading. Roughly 40% of the libraries in a typical Maven dependency tree touch bytecode at some point, and nearly all of them pick one of three tools to do it: &lt;strong&gt;Byte Buddy, Javassist, or ASM&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
