Today's free Phlex on Rails video is all about rendering, which is very polymorphic in Phlex. Partials, strings, values, components, component classes, and collections all Just Work™ when passed into the `render` method.

I shared a bit more detail about the morphing algorithm in Morphlex here. I also released Morphlex 1.0. joel.drapper.me/p/morphlex/

I’ve fully switched to Jujutsu and don’t see myself ever going back to Git. github.com/jj-vcs/jj

Today's rant: ismaelcelis.com/posts/2025-1...

Morphlex now has a new algorithm that produces extremely optimal DOM morphs for inserts, removals and sorts. github.com/yippee-fun/m...

That's how you lead with integrity.

Wow, what a stark contrast against Ruby Central. pyfound.blogspot.com/2025/10/NSF-...

If your logo is still on the Ruby Central website, what are you doing about it?

the former maintainers of Bundler and RubyGems have a proposal: we want to move Ruby forward andre.arko.net/2025/10/26/w...

today we landed a @svelte.dev feature i'm pretty stoked about — we call it 'forking', and it lets you run state changes offscreen and later choose whether to commit them (e.g. user hovers on a link, preload data in case they click) - docs svelte.dev/docs/svelte/... - demo svelte.dev/playground/a...

What comes through loud and clear from Shan is the lack of respect for open source authors. She actually says it’s none of my business why I was removed from rubygems. I don’t know where you got the audacity but you should put it back. youtu.be/nKpo68g9dEk?...

We just got the basics of method overloading working in Empirical! I’m feeling good. Not going to read the latest Ruby Central stuff tonight. When you title your press release “source of truth”, that’s a red flag. 🚩

I’ve used this a bit today and my god it’s so good to be able to quickly see the shape of a method just by looking at it. The documentation factor alone is *huge*, let alone the other benefits.

Apple Loses UK Antitrust Lawsuit Over App Store Fees, Faces £1.5 Billion in Damages

Haven’t read this yet but I already know it’s going to be great.

Joel and I have made fantastic progress on our Ruby enhancements gem that brings rich runtime type assertions into your Ruby projects and Rails apps. Joel recorded a short demo of how to add type constraints to method definitions: www.youtube.com/watch?v=G9r...

I recorded a quick demo of my latest project, Empirical, a pre-processor for Ruby that builds on Literal’s runtime type system. youtu.be/G9rxcepewas

We need this. github.com/orgs/communi...

Tip: you can is this element in GitHub READMEs.

Maybe I can finally upgrade after this.

I wrote about the designing the perfect type signature syntax in Ruby.

Official launch article for the Phlex on Rails video course. Huge thanks to @joel.drapper.me for creating @phlex.fun. It was fun making the course for it. I hope this inspires more people to use Phlex so we can all benefit from building UIs with components without React JS bloat. 💪🚀

2 kinds of 🐞: Bug of Omission: The system refuses to proceed. It raises, crashes, or otherwise stops doing anything. Bug of Commission: The system does the wrong thing. It silently deletes records, returns incorrect results, or processes invalid inputs.

just discovered that my spam folder is full of messages from ruby central and I'm glad to see the system is working as designed

I genuinely can't believe people are boosting the "ruby core has taken ownership of bundler" thing like it's supposed to smooth everything over. all it does it reinforce the fact the bundler team had their project stolen with ruby central acting as a fence

it still wasn't Ruby Central's to give away ownership of. it was the maintainers to give away. Ruby Central could've forked it and continue on their own path and been fine. Woulda taken 30 seconds in GitHub and saved y'all so much time.

Ruby Central was a questionable organization with zero transparency even before all the drama started. I deeply care about the ruby ecosystem, but still give RC zero $. I would always actively advise against providing any funds to RC. Better spend that cash to improve the gems company relies on.

Bugs of Omission and Bugs of Commission joel.drapper.me/p/omission-c...

Building on Literal’s dynamic type system, we’re making it easier to add runtime assertions with method signatures via a Ruby pre-processor. We’re using Prism to parse valid Ruby syntax with different semantics and then pre-processing into regular Ruby on load.

If the Rails Foundation tried to take Rails from its maintainers, I would stand up for the maintainers, despite my political differences. Rails is not owned by the Rails Foundation in the same way RubyGems projects were not owned by Ruby Central. And neither are legitimately owned by Ruby Core.

The two most effective ways your company can support open source: 1. Let your developers have time for open source work. 2. Give each of your developers an annual budget to allocate to whatever OSS projects they think are important.

I joined Errol Schmidt at @reinteractive.bsky.social to talk about the RubyGems takeover by Ruby Central. This was recorded before the transfer of RubyGems to Ruby Core. youtu.be/_H4qbtC5qzU

I wrote about some of my thoughts on the lessons we can learn from the RubyGems situation and how we can move forward. blog.peterzhu.ca/open-source-...

Let’s see what Chad Jippity says about this…

“use bundler from engine yard to install your gems from gemcutter by thoughtbot” sure is pretty far away from “ruby central has always managed these projects”

So this was nothing to do with operator agreements. The original RubyGems maintainer team would have been the right group to decide upon and figure out this transition.

It was stolen by a member of ruby-core, hsbt. What can we do when ruby-core feels entitled to take projects from the people that have maintained them for years?

Why would anyone do open source with Ruby anymore? Fuck this.

Ruby Core accepts stolen RubyGems projects that their own insider HSBT stole from the maintainers through Ruby Central. www.ruby-lang.org/en/news/2025...

Hanami 2.3 beta2 is out! Here we introduce a `hanami run` command, improve action formats config, bump our minimum Ruby, and bring a range of other fixes and improvements. This will be our last beta for this cycle, and we’d love your help with testing! hanamirb.org/blog/2025/10...

😔

I stand by my reporting on this.

I updated the article at allaboutcoding.ghinda.com/ruby-on-rai.... Thanks to @joel.drapper.me for sending me this tip about how to use RubySchema.

I appreciate that gem.coop is taking governance seriously out of the gate. mikemcquaid.com/bootstrappi...

YAML is weird. And not in a good way That’s why I maintain Ruby Schema, a collection of config schemas for the Ruby community. Our i18n schema prevents this boolean problem, helping the YAML LSP show errors. github.com/yippee-fun/r...

My team at Plane is hiring experienced full stack engineers. We use Rails, Postgres, Phlex, Vite, TypeScript and Svelte. I don’t have a full job description yet, but drop me a DM if you want to know more.

As of right now: 1. Ruby Central is *still* in possession of the GitHub organisation and gems that it stole. 2. It hasn’t published any kind of justification for this. 3. It has threatened an ex employee for responsibly disclosing that it left him with root access to live production systems.

What if gem hosts had NPM-like scopes & your Gemfile could be: source "https://gem.example" gem "@duckinator/jim" OR: gem "https://gem.example/duckinator/jim" ... what if a PoC patch was 25 lines, and a 1-line kludge meant you can test it against a production server? github.com/gem-coop/gem...

Who would ever contract for Ruby Central in the future after this obvious smear campaign against a former employee? I’ve never seen a postmortem like it. Incredibly unprofessional. If I was trying to destroy RC’s reputation to justify a takeover by another org, this is what I’d be doing.

Periodic reminder: @rubycentral is smearing Andre in public so they can justify their hostile takeover of the rubygems/rubygems repo after the fact. An actual community-focused organization would have followed the RFC process which was already in progress.