<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>csharp on Isak Sky&#39;s blog</title>
    <link>https://www.isaksky.com/tags/csharp/</link>
    <description>Recent content in csharp on Isak Sky&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 20 Aug 2026 08:00:07 -0700</lastBuildDate>
    
	<atom:link href="https://www.isaksky.com/tags/csharp/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>DripSharp: Building a Java-to-C# source converter with AI</title>
      <link>https://www.isaksky.com/posts/dripsharp-java-to-csharp-source-converter/</link>
      <pubDate>Thu, 20 Aug 2026 08:00:07 -0700</pubDate>
      
      <guid>https://www.isaksky.com/posts/dripsharp-java-to-csharp-source-converter/</guid>
      <description>A few months ago, Jarred Sumner ported Bun from Zig to Rust with AI, largely processing one file a time. While it was a cool thing to try, and I&amp;rsquo;m sure there are many reasons why this made sense for him to do it this way, it didn’t strike me as a great general way to tackle this kind of problem.
I am definitely for using AI where possible, but my instinct was that a better way to do this is to just create a program that walks the syntax tree of the source and applies a bunch of rules to transform it node by node.</description>
    </item>
    
  </channel>
</rss>