I think I might have finally figured out why Ruby on Rails 2025 conferences rejected my talk proposals for my open-source project Glimmer DSL for Web that won a 2025 Fukuoka award from Matz (the creator of Ruby) even though the library provides a 100% innovative and useful tool, is used at my job, has no competition by any other open-source projects, is Matz-approved, and I am the most qualified person to give a talk that unique and interesting due to being the creator, a multi-time RailsConf/RubyConf speaker, and an award winner (meaning, the excuse of other talks winning over doesn't really apply here as they're all inferior if they don't cover a topic that is as innovative and aren't given by someone as qualified as I am due to winning an award by Matz).
I noticed in the past that some Ruby on Rails conference websites were built using React and kinda sucked because they didn't have bookmarkable URLs for when the user clicked on a talk to expand it and read it, preventing users from being able to share direct talk links with others. So, the devs presiding over the conferences were probably insulted by my talk saying that using Glimmer results in writing much less Frontend code as to be able to do 12 months of JS Frontend work in 6 months in much more readable Ruby because they've drank the React koolaid, are biased, and would hate to stop using React no matter how inferior it is to using a Ruby Frontend Framework. In other words, they're devs who are insecure, standing in the way of progress and innovation, attached to inferior technologies for emotional reasons not rational reasons, and hate Ruby, so would rather side with React's folks against real Rubyists to the point of discriminating against me by rejecting my 100% qualified and unique talk that had zero competition.
Honestly, that auto-disqualifies those conferences from being ones that I'd like to speak at due to being run by unintelligent biased haters of Ruby who don't respect accomplishments like winning an international competition with an open-source project by the creator of the Ruby language himself, meaning they discourage innovation and encourage devs to either use outdated tech like JavaScript and React (Inertia is just inside-the-box unimaginative lipstick on a pig and Glimmer DSL for Web already bridges the gap to all JS libraries via Opal) or follow the hero worship anti-pattern by only allowing DHH to "innovate" with Turbo without anyone else in the community being accepted for their innovative idea contributions (a form of discrimination). So, it wasn't a loss for me not to present as I'd be embarrassed to speak at one of those inferior conferences like RailsConf that are now run by unintelligent haters of Ruby in 2025. In fact, I am already embarrassed I spoke at RailsConf twice in the past given how anti-innovation, unintelligent, and downright discriminatory RailsConf has become. But, it is a loss for attendees of those conferences to miss out on a tool that lets them cut down development time and code by half in the Frontend of Rails apps when Turbo isn't cutting it anymore, meaning the selfishness in being biased towards React and JavaScript against Ruby is literally robbing all devs and customers of months of saved costs and time in Frontend work.
Obviously, the Ruby community has a cancer that has invaded it through fake Ruby shops that claim to like Ruby, but use React in the Frontend instead of Frontend Ruby (Frontend Ruby via Opal has been around for 10 years, so no Ruby shop has any excuses not to have adopted it as a standard even before I created my Frontend Framework, Glimmer DSL for Web, on top of it). A while ago, I saw a guy give a talk at a Ruby meetup about how much he liked using Ruby at his startup, but then he mentioned that his team used React in the Frontend, even though React's code and approach completely contradicts and goes against the Ruby way, resulting in very bad maintainability. When I told him and his team after the talk that they could use Ruby in the Frontend via Opal now, their eyes glazed over as if they didn't care for Ruby whatsoever, disproving 100% that they really liked Ruby and proving they were hypocrites that just used Ruby on Rails for the "cool association factor" (that's what they truly liked Ruby for), not for appreciating or understanding the benefits of Ruby. That's the story of 50% of Ruby shops in 2025.
I have no choice but to conclude that those Rails conference rejections are 100% discrimination and exclusion given I am 100% qualified (I have spoken at the last 3 RubyConfs in a row), the topic is very important as it would save companies that do Frontend Development with JavaScript months of work every year, and no other speaker at all in any of those conferences has won a Fukuoka international technology competition award with a Ruby open-source project from Matz, meaning the excuse of "other talks won over" doesn't really apply unless there is discriminatory bias. I mean some of those conferences literally accepted JavaScript talks with Inertia and favored them over using Ruby even though Ruby produces much more readable/maintainable/slim code than Inertia/React while cutting Frontend work by half and allowing the use of any JS library from Ruby (that's infinitely way more innovative than using Inertia), and yet those conferences claim to be "Ruby conferences" (obviously a lie nowadays)!!!
While inferior tools like Inertia think inside-the-box, truly innovative tools like Glimmer DSL for Web in Rails-like fashion totally tear down the box and re-imagine Frontend Development in Ruby. Why did the once-forward-thinking Rails community become so backwards thinking about the Frontend Development story aside from Turbo in 2025? The talk that covered Inertia at RailsConf 2025 didn't even mention Opal Ruby as part of the Rails Frontend evolution at all, nor cover Ruby WASM and how it allows writing Frontend code in Ruby as an alternative to Opal. I personally covered both with a talk at my local Ruby meetup years ago now, proving I'm a more qualified speaker than the guy who mentioned Inertia in his Frontend talk at RailsConf 2025: https://www.youtube.com/watch?v=4AdcfbI6A4c
The Ruby on Rails community cancer of discrimination, bias, and hate of Ruby is very ugly in 2025. Conference organizers could put an end to the discrimination by apologizing for their discriminatory treatment and guaranteeing a spot for me to speak at their conference next year if they want to make things right and prove that the Ruby community isn't run by discriminatory unintelligent biased haters of Ruby.
Honestly, saving 6 months of Frontend work a year via Frontend Ruby provides the biggest improvement to Rails shops in 2025, so this is actually the most important topic at any Ruby on Rails conference in 2025 as I am 100% sure that not a single other talk provides that big a benefit to companies.
No comments:
Post a Comment