Ruby Open-Source Innovation Process Expectation vs Reality

Expectation regarding the Ruby open-source innovation process:

1- I stumble upon a problem at my job in our Ruby application

2- I build a solution for it in an open-source project (e.g. the ability to write the Frontend with a Ruby Frontend Framework instead of using an inferior JavaScript library like React)

3- I win an award for my open-source project by Matz, the creator of Ruby.

4- I get accepted to present my open-source project at Ruby conferences

5- Ruby Software Engineers adopt the new highly innovative open-source project, benefiting themselves and their customers greatly.

Reality regarding the Ruby open-source innovation process:

It doesn’t matter how innovative an open-source project that you build is in your free time as a free beneficial contribution for the community. Even if your open-source project won an award from the creator of Ruby himself at an international tech competition that very few devs won, the project will get rejected from RubyConf due to discrimination and lack of appreciation for excellence from everyone equally. If you’re in their discriminatory out-group instead of their in-group and/or you cover a topic that might upset RubyConf folks who aren’t 100% for Ruby (e.g. unseating React/JavaScript with Ruby), you are excluded (even if your talk’s project has zero competition), to the detriment of the Ruby community at large.

Learn more:

https://andymaleh.blogspot.com/2026/06/rubyconf-has-joined-railsconfrailsworld.html

Originally published as this blog post:

https://andymaleh.blogspot.com/2026/07/ruby-open-source-innovation-process.html