https://nitter.cf/t.co/Vfbxo6yzUw Rails Specialist. Open Web Communities. he/him
Raleigh, NC
Joined March 2009
- Tweets1.6K
- Following5
- Followers3.2K
- Likes260
Sam Ruby retweeted
Programming languages that bring meaningful design choices to the forefront and hide the noise are just as good for agents as they are for humans. Semantic compression matters. Using the right tool for the problem at hand has never been more important.
Not sure I understand the comparison. Why would you compare a Ruby app to a Ruby app transpiled to C and not to a clean implementation of the same app in C?
I honestly don't think that would change the conclusion. rubys.github.io/roundhouse/p… shows the meta-programming free version of the blog application in Ruby, C (clean or otherwise) would be more. intertwingly.net/blog/2026/0… goes into more depth.
Read this if you want to know why high-level languages aren’t going away.
Bad abstractions will die and languages will change, but we’ll still have layers of architecture.
I don’t think Ruby will stay the same, but it will be around in some way, shape, or form as a substrate.
Not Claude loops, but take a look at this page: rubys.github.io/rubyconf-202… ; where you see a programming language you like, click on that name and you will download a tgz with a README. Try it.
What I have is a compiler, built by Claude under my guidance. The compiler is an executable, deterministic, uses no tokens. The compiler can be compiled to wasm and run in your browser: rubys.github.io/roundhouse/p…
> その意味でRailsこそが仕様だと言っていると読み取った
Exactly. Go to github.com/rubys/roundhouse and look at the "about". You will see it in the image below:
I go the other way. SQL is the best example. Sure you don't need a database, you can generate the code to replace it, but why? Databases are battle tested and optimized.
Try different apps and different targets on rubys.github.io/roundhouse/p… ; the expansion is significant. Whether human or LLM, it is easier to reason about and make correct code that is an order of magnitude smaller. Context windows matter.
I really wonder where this goes. Why not Crystal? My only pet peeve with it is compile times and the ecosystem. I think fighting Ruby c extensions and Spinel will be a no go.
Some benchmarks: rubys.github.io/roundhouse/b…
Sam Ruby retweeted
Sam Ruby's Roundhouse transpile Rails app to plain Ruby (or other languages) without metaprogrammig. And Spinel can compile transpiled Ruby code. Not all Rails apps yet, but at least we can compile Campfire and Lobster. See github.com/rubys/roundhouse
I got invited to speak on a panel at Deccan Ruby and I said warning I’m going to say that Ruby and Rails are ded ded ded.
Lovely language obsolete runtime. In a world where you can pick any language with zero tradeoffs there is no reason to pick Ruby. DX was the only reason to pick Ruby and that reason has been obsoleted.
Wish @dhh had picked elixir though.
Previous Deccan Ruby or next one? What if you could keep the language and replace the runtime? Explore Blog and Campfire here: rubys.github.io/roundhouse/ ; try Elixir: rubys.github.io/roundhouse/b…
If we're not looking at the code any more, what's the argument for sticking with Rails? Library support? Honestly I don't see much of a future for Ruby or Python (or any interpreted language). I think everyone's going to start throwing Roundhouse at old Rails projects anyway, and the new projects will use other languages to start with. They aren't just faster, they require fewer nodes, and will ultimately save your company money.
Daniel (dB.) Doubrovkine (parody of myself)@dblockdotorg
Sep 23United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
It’s less code. Much more readable and more business logic per line. Excellent ecosystem of dedicated libraries so each has less scope for change, fewer bugs.
Not so far. We see enterprisey talks. But in Euruko, everyone talked about Spinel (and Roundhouse) though.
A PR against Campfire, merged by @rosapolis, and Campfire on Spinel now passes 300 out of 300 model and controller tests: intertwingly.net/blog/2026/0…
TruffleRuby specializes the interpreter to the program at runtime; Roundhouse specializes Rails to the app ahead of time. I'm now, for the first time, starting to measure the impact of each separately and together: intertwingly.net/blog/2026/0…
So Matz is saying you can make Campfire (a Rails app) 5 times faster and use a twelvth of the memory by using github.com/rubys/roundhouse + github.com/matz/spinel
#EuRuKo @euruko
there's no single answer, because a gem's layers have different fates. Pure-Ruby subset → compiles as-is (on Spinel). Rails-coupled DSL → expanded at build time. Native ext → a typed binding package (libvips, bcrypt). Interpreter-shaped (puma, bootsnap) → evaporates under AOT
Some pointers: intertwingly.net/blog/2026/0… ; rubys.github.io/roundhouse/p… ; github.com/matz/spin-index (look at the pull requests too)