<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sorbet on @zhisme :: signal over noise</title><link>https://zhisme.com/tags/sorbet/</link><description>Recent content in Sorbet on @zhisme :: signal over noise</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://zhisme.com/tags/sorbet/index.xml" rel="self" type="application/rss+xml"/><item><title>You Don’t Need Types in Ruby</title><link>https://zhisme.com/articles/you-dont-need-types-in-ruby/</link><pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate><guid>https://zhisme.com/articles/you-dont-need-types-in-ruby/</guid><description>&lt;p>There was a lively discussion on Hacker News &lt;a href="https://news.ycombinator.com/item?id=43938400">here&lt;/a> about &lt;a href="https://sorbet.org/">Sorbet&lt;/a> and static typing in Ruby that inspired this post.&lt;/p>
&lt;p>It’s fascinating how people try to make Ruby &lt;em>look&lt;/em> like a statically typed language. But this isn’t the first attempt — and every time, it ends up fighting against what Ruby fundamentally is.&lt;/p>
&lt;p>Turning Ruby into Java isn’t progress. It’s a step backward.&lt;br>
Let me explain why.&lt;/p>
&lt;h2 id="how-ruby-deals-with-types">How Ruby Deals with Types&lt;/h2>
&lt;p>Ruby is a dynamically typed, object-oriented language designed around message passing — an idea borrowed from &lt;a href="https://en.wikipedia.org/wiki/Smalltalk">Smalltalk&lt;/a>.&lt;/p></description></item></channel></rss>