XO Ruby joins RubyConf/RailsWorld as Another Exclusive Discriminatory Unexcellent Conference

So, I got contacted by the organizer of the XO Ruby conference (aka Travelling Ruby), Pascal Laliberté, on meetup.com because I organize the Montreal.rb Ruby Meetup and am a Montreal-based Expert Ruby Software Engineer. He said XO Ruby is coming to Montreal and asked me for help with it. We end up meeting in a video conference call. 

To help out, I indicated that I asked my company to consider sponsoring the conference. Furthermore, I volunteered to give a talk as a Montreal-local Ruby Expert (given I have won 2 awards by Matz and have spoken 4 times at RubyConf and 2 times at RailsConf, plus 2 times this year at Ruby conferences in Europe, including this talk that I shared with him); I offered to ask my company's former CTO (who is still with us in a different position) to give a "Founder" topic talk (one of the topics of the conference) about how to be a Tech Founder for a Ruby on Rails project (our previous Montreal-based Fintech company is a huge success story as we got bought by a larger Silicon Valley Fintech 1.5 years ago that is a leader in the Credit Union AI/Agent Conversational Software space); and I offered to recommend other potential Ruby speakers from Montreal. 

After everything I volunteered to help with, Pascal strangely seemed to push back against me giving a Ruby talk at the Montreal-based XO Ruby even though there are empty slots left and I am literally one of the biggest representers of Ruby in the Montreal Tech community today (not many Ruby Software Engineers from Montreal present at RubyConf like I have in 2022/2023/2024, and no one from Montreal as far as I know has won awards by Matz, the creator of Ruby). I've also put in many many hours and days into keeping the Montreal.rb Ruby Meetup going, including giving extra presentations myself whenever needed, and that's in addition to the many many hours and days I've put into Ruby Open-Source Projects. Honestly, if an interviewee at a job interview I am conducting had reacted with that sort of apathy after hearing my accomplishments, they'd be cut immediately from the interview process due to being apathetic instead of passionate, and due to not appreciating excellence, as only unexcellent people don't appreciate excellence. Truly excellent people always appreciate excellence and excellent accomplishments, while maintaining an attitude of curiosity about them.

I asked him how many talk slots are left in the conference. He said there are about 9 slots and about 4-5 are left, including empty slots for the "Open-Source Projects" topic. Then, he started trying to explain that he wanted a very technical Ruby talk (it's a weird note given Glimmer DSL for Web is one of the most technically interesting and innovative Ruby projects ever with its ultralight, expressive, and minimalistic DSLs). So, I told him I've given talks at many Ruby/Rails conferences and meetups on a variety of topics, including Domain Driven Design, Design Patterns, Object Oriented Design, Desktop Development, Frontend Development, and DSL Engine Meta-Programming, plus I have literally won an award from Matz, the creator of Ruby, last year for my Open-Source Project, Glimmer DSL for Web (in addition to winning another award a few years ago for Glimmer DSL for LibUI), so I can easily give a strong Ruby technical presentation. The weirdest and creepiest thing is Pascal's face was so apathetic when I was recounting all my Ruby accomplishments as if they don't matter. That's not the reaction of a strong ethical Software Engineer who cares about the fact that past Ruby accomplishments have benefited many customers and continue to benefit customers directly or indirectly today. 

Then, Pascal said he could not guarantee a slot for me despite having empty slots, believe it or not, without providing any valid reasons! I told him given that I am 100% qualified to give a talk at the conference, this is discrimination! After all, if I wasn't qualified, or even had some competition, I could understand not being guaranteed a slot. But, I am the only one in the Montreal community who has won awards from Matz, my new innovative open-source project has no competition, and no Software Engineers in Montreal have represented Ruby as much as I have in recent years through continued effort in fostering the local Ruby community with running the Montreal.rb Ruby Meetup. Meaning, this is 100% discrimination. 

To give a point of comparison, I was literally hired instantly at my current company a number of years ago (when we were still a small startup before acquisition) because my boss appreciated all my Ruby accomplishments and knew that I had a large enough body of work in the Ruby community (many RubyConf/RailsConf talks and Ruby open-source projects) that demonstrated my Ruby skills beyond the shadow of a doubt and warranted instant acceptance of me. My boss back then who was the CTO at the time is a Super-Duper Ultra Strong Software Engineer/Architect/CTO by the way, so he knew what he was doing. 

Any normal competent ethical strong Software Engineer would have been absolutely excited to have me talk at their Ruby conference (like the organizers of wroclove.rb and RubyConf Austria), especially that I have won an award from Matz himself, the creator of Ruby. They would have been 100% curious to learn what the award-winning project is all about and would have wanted me to share that knowledge with others in the Ruby community for the benefit of customers (not for selfish reasons). 

I responded to Pascal further by telling him that his conference practices discrimination and is an unexcellent garbage conference that is way below my standards for how a Ruby conference should be (it should be non-discriminatory and appreciative of excellence that wins awards from the creator of Ruby).  So, I don't want to participate in it anymore nor help it. The fact that the conference doesn't immediately accept a talk by someone who won awards from the creator of the programming language that is the reason for the conference existing means it is a trash conference. It can't possibly be sharing top-level Ruby excellent knowledge, yet lower-level mediocre knowledge. I told him I was ending the video conference call because discrimination is not acceptable anywhere in Canada. It's funny how this creepy unethical guy was trying to act as if he's "more important" than me when in fact he probably doesn't have half my accomplishments. This reminds me of this blog post about entitled people in the Ruby community, which applies to him as well.

The crazy thing is he tried to interject and say things about "my behavior" towards the end of the video call when in fact his behavior was already bad through discrimination and lack of appreciation for excellence, so if his behavior is already bad, he is in no position to judge anyone else's "behavior"! My behavior is exemplary in the Montreal Ruby community over many years.

One other thing worthy of note that relates to discrimination is that at one point, Pascal tried to focus the conversation on the pronunciation of my last name, which felt uncomfortable and felt as if he was trying to pigeon hole me into whatever "country of origin" my heritage belongs to instead of just treating me as a 100% equal Canadian (as I am a 100% Canadian after all). I have just completed my employer's yearly training for workplace prevention of abuse, harassment, and discrimination. And, such behavior came up in the training as "discrimination based on the country of origin". When he asked about how my last name is pronounced, I told him my last name is just pronounced like it's written in English, with the end being silent, similarly to the pronunciation of the word "melee" (meaning a skirmish). To be honest, over the years, I have received that sort of discrimination from a number of people in Canada. It's disappointing that some people in my country, Canada, discriminate against others based on their country of origin, sometimes in very subtle ways with plausible deniability (this was blogged about as covert discrimination). I had less experience of that discrimination when I lived in the USA in the past during the first 10 years of my career. It's ironic that the international stereotype of Canadians is that they are nice people, but in actuality, some of them (not all) apply "niceness" with a double standard (which is not nice), treating people in their in-group nicely and treating others in their out-group not nicely at all. That's something I have experienced by some of the people who work for Shopify in the past (this blog post by Paul Battley and this blog post by André Arko confirm my experience of Shopify being mean). Fortunately, I work with very nice people at my company's Montreal branch and I have a very nice French Canadian girlfriend too.

Another thing worthy of note is that this XO Ruby conference is associated with Jim Remsik who runs Falgrant. In a past RubyConf that I presented at, at which I met Jim Remsik, I literally saw swag/stickers by Flagrant that included the F word, which were very unprofessional and disrespectful. Professional Software Engineers who don't make it a habit to drop F bombs at work would not use that sort of language in business marketing material as that immediately reduces a company like Flagrant into a trash company that spreads unethical trash with every interaction they have with others. I removed Jim Remsik from my LinkedIn in the past after I noticed that just as I removed Pascal Laliberté from my LinkedIn today after our video call.

I have mentioned this before; from the perspective of discriminators who have an unconscious or conscious in-group/out-group bias, it doesn't matter if someone from the out-group has launched rockets to the moon successfully with excellent effort, as they would still get treated as if they are unequal unimportant people and as if their accomplishments don't matter (in spite of having practically benefited many customers directly or indirectly with their accomplishments). 

In conclusion, to avoid enabling discrimination and unexcellence in the Ruby community, avoid attending, sponsoring, and presenting at XO Ruby. Also, know that it is a mediocre garbage conference that is way below the high quality standards of Ruby Experts like me for excellence and ethics. 

P.S. Of course, as with my other blog posts, to prove that I'm on the right side of things, I acknowledge that nobody is perfect and everyone makes mistakes. Meaning, I am always open to the idea of forgiving people if they redeem themselves. So, if Pascal was to apologize about his discrimination/lack-of-appreciation-for-excellence and allow the most active Expert Ruby Software Engineer in Montreal to present at a Montreal Ruby conference, I'd be happy to retract this blog post. Otherwise, if I am wrong about something and it was kindly, patiently, and respectfully explained to me with genuine loving intentions, I'd be happy to reverse my position too. 

RubyConf Austria 2026 Talk Video: Frontend Ruby on Rails with Glimmer DSL for Web — Andy Maleh

My RubyConf Austria 2026 talk has been published on YouTube! What if your frontend was just... Ruby?

https://www.youtube.com/watch?v=qTukq5AcSK0

You can find the talk slides over here:

https://andymaleh.blogspot.com/2026/06/rubyconf-austria-2026-frontend-ruby-on.html

A Supporter Sympathizes with My Discrimination by RubyConf 2026

I am thankful to the Software Engineer who shared a very supportive comment regarding my experience of discrimination by RubyConf 2026. 

RubyConf 2026 Is Not a Safe Environment for Everyone

RubyConf 2026 is not a safe environment for everyone. They have an in-group and an out-group. If you're in the in-group, they will treat you well and accept talk proposals by you even if you don't have top-level skills in Software Engineering. If you're in the out-group, it doesn't matter if you launch rockets to the moon successfully on your own or win the approval of Matz himself, you will be excluded and discriminated against: 

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

If that weren't true, then RubyConf's folks would not be afraid to address the issue of feeling discriminated against for the benefit of keeping their reputation clean. Alas, like all discriminators out there, they cower and hide instead of addressing the issue because the discrimination is 100% real. A discriminator usually discriminates because they don't see everyone as equal or because they're frauds and don't have the energy to treat everyone equally, so if discrimination is brought up to them, they won't take it seriously. 

Respectful treatment means to treat someone well and fairly for what they have accomplished and what they offer. I realize I could buy a ticket to the conference, but rejecting a talk by me that won the approval of Matz, the creator of the Ruby programming language that is the reason for the conference existing means I have earned the right to talk about the subject that I won an award from Matz for. Otherwise, I am being robbed and discriminated against. This is no different from how the MLB (Major League Baseball) used to mistreat Afro Americans and relegate them to playing in the Negro league instead of the Major League. Telling someone who can perform at the major league level they are unaccepted as a player there, but could attend if they want is most definitely discrimination 100%. 

By the way, under other circumstances, if I had no project to talk about, I would be 100% OK with attending RubyConf instead of presenting as I would normally want to support other speakers and learn from them. But, in 2026, the issue is if they rejected a talk by someone who won an award from Matz at a near impossible international competition to win, it means they probably rejected a lot of top-quality talks and accepted many subpar mediocre quality talks. I don't want to go to a conference in which I become mediocre by attending mediocre talks. Excellence and unexcellence are infectious. The next thing I know after hanging out with unexcellent speakers at RubyConf 2026 is I'll become unexcellent and subpar like them. This is no different from entire mediocre communities like the React.js comunity and others where the blind are leading the blind into a pit, but everyone is celebrating the popularity of mediocre ideas and technologies (meaning they only perceive themselves as being smart, but objectively, they're all performing suboptimally for customers and don't provide the best smartest work). No thanks!!!

RubyConf 2026 is a cesspool of discirmination and exclusion:

https://andymaleh.blogspot.com/2026/07/reminder-that-rubyconf-2026-is-cesspool.html

One might think that RubyConf's folks are too busy to look into the discrimination claim. But in fact, I contacted them about the perceived discrimination about a month ago. They had all the time of the world to look into the discrimination and lack of appreciation of excellence (an equally serious matter). Also, if they claim to be "excellent", "inclusive" and "diverse", then looking into discrimination and lack of appreciation of excllence would be the top priority of RubyConf, alas they're a mediocre discriminatory conference in 2026 that doesn't put excellence and lack of discrimination at the top of their priorities, just like any dictator at a third world country would act. They're no different. It's a fraud of a conference in 2026.

The fact that it doesn't bother them to have these blog posts published as to want to contact me and settle the issue of discrimination against me proves they are discriminators 100% because discriminators aren't bothered by having discrimination reported to them, but real non-discriminators put ethics and good equal treatment of everyone first above everything else.

I have talked extensively about covert discrimination in the Ruby community in the past, including microdiscrimination / personal discrimination (meaning discrimination against a single person, which makes the discrimination escape protections available for minority groups). Ignoring someone without attempting to resolve things amicably definitely falls under covert discrimination:

https://andymaleh.blogspot.com/2024/12/how-to-spot-covert-discrimination-in.html

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 Ruby 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

Reminder that RubyConf 2026 is a Cesspool of Discrimination and Exclusion

Just a reminder that RubyConf has become a Cesspool of Discrimination and Exclusion. In 2026, it doesn't matter how well accomplished a Ruby Software Engineer is in the Ruby community as even if they win awards by the creator of Ruby himself, if they propose a topic that is taboo with the organizers of RubyConf, they are excluded and discriminated against, without even providing a valid reason for the exclusion. It's one thing if there was an intelligent rational reason. It's another when the organizers just run away in cowardice from addressing the discrimination, which is an act of discrimination/exclusion as ignoring someone is a form of exclusion too. 

The bottom line of RubyConf is that if you are one of the "favored ones" that RubyConf give preferential treatment to, then even if you haven't won any awards from the creator of Ruby or lack complete mastery in Software Engineering, due to discrimination, you are given more importance over someone with more skills and experience. 

That means RubyConf mostly has subpar and suboptimal talks. Intelligent well-accomplished master Software Engineers can't trust that they would receive top-level talks at RubyConf anymore in 2026. 

Basically, RubyConf discriminates against people by seeing them in multiple groups (unlike normal non-discriminatory conferences that always recognize and reward excellence):

• Excluded ones: those people can build a rocket that reaches the moon and win awards from the creator of Ruby, but their efforts are not appreciated by RubyConf or respected as to give them a speaking platform if they propose a topic that is deemed too novel, outside the box, or taboo by RubyConf (like Frontend Ruby Development)
• "Favored ones": those people are liked not always for top-merit or rational reasons, but often for emotional reasons too, a form of discrimination by not seeing everyone as equal, yet deeming some people as above others even without having the best or top-level accomplishments.

Meaning, the "favored ones" will be allowed to "have fun" at the conference and think it is "diverse and inclusive" when in fact it's all a lie. They do it with a double standard offering that to some people only, but not offering well-deserved respect to everyone who earned it, and without even being loving enough as to explain why a talk about an open source project that won an award by Matz himself at a very difficult international competition is getting rejected at the conference as to help the person follow a "better path" in their career if they're truly wrong.

Part of the reason why this is a big problem is because the project they excluded offers an amazingly simple Ruby solution to a very complicated and divisive problem in the Ruby on Rails community. Then again, perhaps it is knocking JavaScript around too much for the liking of fake Rubyists who work at RubyConf and that's the true reason why they "didn't find the project interesting" when in fact Matz the creator of Ruby who's smarter and more accomplished/important than all of them didn't just find it interesting, but was willing to give it an award at a difficult international competition along with other smart judges. 

By attending RubyConf, you're supporting this kind of discrimination and exclusion, plus lack of appreciation of excellence, which means RubyConf is unexcellent and is mostly sharing dumb "yet popular" talks with the public. If anyone has any shred of ethics, self respect, or excellence, they would boycott RubyConf and contact them about this grand discrimination offense committed by them. 

Funny, I told my girlfriend about this a while ago, and she recently asked me if any of the RubyConf folks reached out to me to apologize or explain themselves, expecting that normal people would do that. I told her no, they're just unethical discriminatory cowards (their guys aren't real men) who don't care to explain this or apologize about it. Though, I personally am always open to forgiving someone if they are willing to apologize or explain what I might have done wrong to deserve this. Any other reaction shows apathy and more discrimination (ignoring someone is exclusion, so another form of discrimination). 

In a way, I am very happy I won an award from Matz in 2025 because it exposed the Ruby community for all the discrimination it has against certain people/topics in the community, which even reached RubyConf eventually.

RubyConf has joined RailsConf & RailsWorld as another exclusive discriminatory unexcellent conference

RubyConf has joined RailsConf & RailsWorld as another exclusive discriminatory unexcellent conference by discriminating against any speakers who submit talks that cover Frontend Ruby technologies or dethrone React/JavaScript in any way. In 2025, I won an award for a highly innovative and outside-the-box Ruby open-source project at an international Japanese tech competition that Matz, the creator of Ruby himself, presided on in addition to other judges. My project really impressed Matz, who is the reason for all the Ruby-related conferences existing in the first place, but in spite of that, both RailsConf and RailsWorld rejected my talk about my award-winning open-source project in 2025 despite the Ruby on Rails community sorely needing a Frontend Ruby solution that would fill a gap not handled by Hotwire; that is true Frontend Development in Ruby (to build frontend-local apps like a UML Diagrammer for example). Given that I am the most qualified person to talk about Frontend Development in Ruby on Rails using real Ruby in the Browser, and no other Frontend technologies rival my project in either productivity or simplicity/maintainability, the rejections came across as discrimination/exclusion and mediocrity/closed-mindedness/lack of appreciation for excellence. After all, if you reject an open-source project that won an award by Matz, your action is sending everyone the discouraging message that it doesn't matter how hard Software Engineers work to produce a unique innovation; they will stil be rejected because of discrimination and lack of appreciation for excellence if it comes from outside the core group behind Rails and some of their sponsors/friends. The reason this is also discrimination is because I was not rejected due to being unqualified (as I won an award after all) or due to the project not providing great value to the Ruby on Rails community (it impressed Matz) as the project saves Ruby on Rails Software Engineers who previously used JavaScript libraries like React.js/Angular/Vue/Svelte 6 months of Frontend work every year by switching to Frontend Ruby. I don't know many talks at RubyConf in general that can offer the same benefit. And, I am sure that nobody working for either RailsConf or RailsWorld has won a similar award to mine at the same international Japanese tech competition that was judged by Matz (and I have done it one other time previously too in fact). 

Fortunately, this year, my award-winning open-source project got accepted at RubyConf Austria 2026 (30-minute talk) and wroclove.rb 2026 (3-hour workshop). Those conferences are much better run than RailsConf and RailsWorld in welcoming innovation and being inclusive! wroclove.rb 2026 literally says on their website that they "want to confront ideas", in contrast to RailsConf and RailsWorld running away from ideas that don't come from the Rails core devs and some of their sponsors/friends (a form of discrimination). RubyConf Austria & wroclove.rb don't discriminate against Frontend Ruby projects and aren't offended by a talk that dethrones React/JavaScript, especially if already approved by Matz, the creator of Ruby. They welcome the excellence and hard work that went into creating my award-winning open-source Ruby project and winning an award from Matz. In other words, they encourage the Ruby community to be excellent and follow my example in innovation and thinking outside the box. In fact, I met Chad Fowler at RubyConf Austria 2026, and he attended my talk, then told me "good job" afterwards. For those who don't know, Chad Fowler founded RubyConf back in 2001. 

So, I submitted my award-winning open-source project's talk to RubyConf in 2026 thinking they might be less averse to Frontend Ruby, especially if the speaker won an award from Matz, given RubyConf is typically more open-minded about Ruby innovations outside of core Rails. Well, I got rejected despite being accepted by Matz, the creator of the language that conference was founded upon. I asked by email for the reasons for the rejection and for feedback to help improve myself in case they want me to do better before getting accepted (though to be frank, I won an award from the creator of Ruby himself, and there isn't anything that can top that). They never responded. 

I want to clarify that I have supported RubyConf in the past by giving talks/workshops at it and by donating my speaker stipends/hotel-pay (over $1000 or $2000 for all the conferences I spoke at) back to RubyCentral for the benefit of the Ruby community as a whole with everyone in it. So, it's not much to ask for a response as to why I encountered behavior that came across as discrimination when I have gone above and beyond in the past in supporting RubyConf and RubyCentral.

Eventually, I remembered that I have 2 RubyConf/RubyCentral people as LinkedIn connections, Jason Swett and Freedom Dumlao, so I contacted them asking the same question. I also pointed out to them that I am a former RubyConf speaker who donated his speaking stipends from the last 3 RubyConfs back to RubyCentral for the benefit of the Ruby community at large (that's over $1000). So, being treated with respect and non-discrimination is the least I could expect from RubyCentral.

Jason Swett chose the coward's plea and just never responded, which is how true discriminators handle discrimination when it's raised to them. The reason this incriminates him 100% is because if he truly wasn't involved in discrimination, he would have at least responded by saying he sympathizes with me perceiving discrimination and by indicating he is shocked that a project that won an award from Matz (when many other RubyConf talk projects didn't win any awards from Matz) got rejected at RubyConf. Honestly, Jason reminds me of employees that my employers fired in the past. Lack of presence and visibility is usually the sign of an unreliable employee who is never there for others. So, I advise against hiring Jason Swett (unless he responds to me and clears up my experienced discrimination).

Freedom Dumlao didn't respond to my first message, but at least responded to my 2nd follow-up message. He gets some points for that. Otherwise, his response was very weird and defensive. He claimed with a very unfriendly tone that I didn't know him even though him and I met at RubyConf 2024 and sat at the same eating table multiple times while having conversations that eventually led to connecting on LinkedIn. In fact, it sounded like he was trying to get out of responsibility by claiming I did not know him enough (a very unnice unfriendly thing to say from a Rubyist) even though the world is a meritocracy anyways, meaning people are known through their actions in day to day interactions, whether ethical or unethical. The way he said that came across as immature and irresponsible, not the way someone at RubyCentral should be talking. After all, a responsible person would have not focused on that, yet focused on my experience of discrimination and how strange it is that a project that was approved by Matz in a very difficult international competition and got a "good job" remark from Chad Fowler (the founder of RubyConf) got rejected at RubyConf, which would indicate RubyConf's staff are unqualified and do not appreciate excellence, in addition to having discriminatory biases, like the bias against Frontend Ruby and biases for React/JavaScript that cause offense if they are dethroned (shameful at a Ruby conference that is supposed to make Software Engineers feel safe about loving Ruby more than other languages). None of them have won similar awards from Matz, most likely in fact. A person in Freedom's position should have been sincerely concerned and should have noticed the problem and then promised a solution without making any excuses, just like how excellent organizations behave. Given that he didn't respond that way, even if I didn't know him, his reaction told me and everyone everything about him that we need to know about who he really is. He showed that he's part of the problem not the solution.

Regarding my donations to RubyCentral that exceed $1000, Freedom tried to deny the value of my donation by saying he donated more to RubyCentral, believe it or not! What a creepy disrespectful way to talk to someone who gave you money for free without being required to. Invalidating a donation is NOT a way to encourage people to continue donating, yet sends the message that donations are discouraged because in the end, they won't matter anyways as "someone else donated more than you". That was the most unhinged unprofessional encounter I've had from someone who is supposed to be a professional! Honestly, it doesn't matter how much he donated. My donations still have the same value in helping RubyCentral and the Ruby community regardless. Other people's donations definitely don't invalidate mine. 

Freedom also proceeded to claim that there was "no discrimination" because all their talks are reviewed anonymously. EXCEPT, my talk was NOT reviewed anonymously, because it mentions a public project on GitHub (which shows the author as soon as one visits it) and a public award (with the winner's name) that the project won from Matz at a public competition. 

I responded to inform him that my proposal submission wasn't anonymous as that was impossible with the talk being about a GitHub project and having won an award. And, I informed him that my donation is definitely NOT invalidated because he donated more. Freedom then chose the coward's plea and didn't respond. I advise against hiring Freedom Dumlao for any jobs or services as a result. He's the kind of selfish irresponsible excuse maker who is only about protecting his own hide while not caring about encouraging and maintaining excellence in a community, nor respecting people who donate to the community without being required to.

You see what I'm dealing with here!? Total trash! These are the kind of people running RubyCentral today! No matter it encountered issues last year with the Mike Perham vs DHH debacle, in addition to stopping RailsConf. The Ruby community is being run by total clowns who are discriminatory, unethical, and unprofessional!

I have ZERO interest in attending RubyConf 2026 as a result. After all, if they rejected a talk by one of the best open-source Ruby projects to come out in 2025 as to win an award by Matz, the creator of Ruby himself, then they probably rejected many other project talks that are top  quality because of the discriminatory biases and lack of qualification of RubyConf staff in 2026. For all we care, we got the dumbest, but most popular, talks in RubyConf 2026, but smart Software Engineers know that popularity is NOT quality. After all, PHP/WordPress is more popular than Rails, but definitely inferior in productivity and maintainability, which is why Ruby on Rails devs don't use those technologies in general. 

In conclusion, RubyConf in 2026 has become an exclusive discriminatory unexcellent conference, which is where people go to become dumber and/or meaner. 

If I had been working for RubyCentral, I would have provided guaranteed speaker slots for winners of the yearly Fukuoka international tech competition that Matz presides on to encourage excellence and innovation in the Ruby community, and I would have provided guaranteed speaker slots or tracks for owners of long-term "pillar" open-source projects in the Ruby community (e.g. Sidekiq, JRuby, Opal, etc...) to respect and support long-term open-source contributors of the Ruby community.

I have covered the topic of covert discrimination in the Ruby community before. What I encountered at the hands of the RubyConf folks is classic covert discrimination. Spread the word to help stop discrimination and unexcellence in the Ruby community! In the meantime, I'll make sure to only attend and speak at Ruby conferences that don't have unprofessional unexcellent discriminatory staff.

P.S. To prove that I'm reasonable and on the right side of this, I will acknowledge that nobody is perfect and everyone makes mistakes. What distinguishes good people from bad people though is that good people will admit their errors and apologize for their mistakes when they are pointed out to them whereas bad people will act aloof and commit more discrimination/exclusion by ignoring you when that happens. If any of the problematic people mentioned in the article change their mind and decide to respond like real men (not by hiding like cowards) to resolve my concerns about discrimination/exclusion/unexcellence for the benefit of the cheated Ruby community that missed out on all the Matz-loved value provided by an award-winning open-source Ruby project that impressed Matz, then I'll delete this blog post. 

Presentation Slides for RubyConf Austria 2026 Talk "Frontend Ruby on Rails with Glimmer DSL for Web"

My talk “Frontend Ruby on Rails with Glimmer DSL for Web” went well at RubyConf Austria 2026. Especially given that after the talk, Chad Fowler (the starter of RubyConf and famous book author of The Passionate Programmer, among other books) told me “good job”, and Obie Fernandez (a famous entrepreneur and book author of The Rails Way, among other books) told me he will try Glimmer DSL for Web because he doesn’t like React.js. 

Presentation Slides for “Frontend Ruby on Rails with Glimmer DSL for Web”:

https://bit.ly/glimmer-rubyconf-at-2026

I ran a poll at the beginning of my talk, and everyone agreed that they love Ruby and that Ruby is superior to JavaScript, plus the majority indicated that they’d like to write less JavaScript and more Ruby during their Rails web development work. Several attendees told me my talk was great after the talk. 

Charles Nutter had me help him with his JRuby workshop afterwards by showcasing my other Glimmer project, Glimmer DSL for SWT, which runs on JRuby. In about 1 minute, I scaffolded a Hello World desktop app from scratch and then packaged it as a native executable on the Mac. Attendees were impressed. So, I’ve participated in presenting 2 events at this conference. 

I am very grateful for having such a great experience at RubyConf Austria 2026 overall, especially given that it uniquely included several classical/neoclassical/jazz concerts in between talks that entertained us and relaxed us. Chad Fowler concluded the conference with a beautiful Jazz piano and sax performance. Shout out to Hans Schnedlitz, Muhamed Isabegovic, and Zuzanna Kusznir (plus everyone who helped out) for organizing and hosting such a special Ruby conference!!!

Frontend Ruby on Rails with Glimmer DSL for Web (accepted at RubyConf Austria 2026)

My talk "Frontend Ruby on Rails with Glimmer DSL for Web" has been accepted at RubyConf Austria 2026.

Title:

Frontend Ruby on Rails with Glimmer DSL for Web

Elevator Pitch [FOR JUDGES]:

Glimmer DSL for Web is a Ruby Frontend Framework for Rails that won a Fukuoka Prefecture Future IT Initiative 2025 award from Matz. It is the missing piece of the puzzle that finally enables devs to write the Frontend of Rails web apps in Ruby too. This talk will cover its features and demo samples.

Description [PUBLIC]:

Glimmer DSL for Web is an SPA (Single Page Application) Framework for Rails that runs in Opal Ruby and has won a Fukuoka Prefecture Future IT Initiative 2025 award from Matz, the creator of Ruby. It provides a paradigm shift and the next stage of evolution in Frontend Development beyond JS libraries like Angular/Ember/React/Vue/Svelte by cutting down 12 months of JS work into 6 months of Ruby work every year. It has a more intuitive development model than Hotwire that better adheres to Software Engineering principles, albeit Hotwire has its place, and Glimmer can be used once Stimulus controllers grow too large or the need arises for using a Frontend SPA Framework.

It is currently in use at Eltropy inside the Collections 2.0 Fintech Rails web app as a gradual upgrade from React.js. It was able to cut down some React components by 1/10 the code and overall Frontend code by about ~50%, albeit with significantly more readable and maintainable Ruby, the language we all love. As a result, Glimmer DSL for Web should become the biggest difference maker and game changer in Rails development productivity in 2026, completely eliminating the need for directly using inferior JS libraries like React because Opal Ruby supports indirectly using any library in the entire JS ecosystem from Ruby.

Glimmer DSL for Web provides a Ruby HTML DSL, a Ruby CSS DSL (optional or to be used in a hybrid fashion with standard CSS/SCSS/Tailwind when Ruby logic is needed), Glimmer Web Components, Component Slots, Component Custom Event Listeners, ERB embedding glimmer_component Rails helper, Element Property Unidirectional/Bidirectional Data-Binding, Element Content Data-Binding, Element Inline Style Data-Binding, Element Class Inclusion Data-Binding, html_to_glimmer/css_to_glimmer commands for converting legacy HTML/CSS code to Glimmer DSL Ruby code, HTTP REST API Web Requests, and JavaScript library integration.

Using an isomorphic one language approach for both the Frontend and Backend in Rails web apps not only achieves significant productivity and maintainability improvements, but also opens the door to new possibilities, like the ability to reuse Backend Ruby logic directly in the Frontend without making API calls to provide faster response times for users, extending the Rails’ One Person Framework approach by enabling Backend Ruby Software Engineers to handle Frontend work in the same language (cutting hiring costs down by half), and enabling future architectural improvements such as connecting Frontend Ruby Models to Backend Ruby Models by automatically generating Rails REST APIs, thus removing the need for developers to write Rails controllers manually anymore, which would then cut down work in the Backend in addition to cutting down work in the Frontend, providing unheard of productivity benefits in Rails in the future.

Bio [FOR JUDGES] (including why I am the best person to give the talk):

The reason I am the best person to speak about this subject is that I wrote the Glimmer DSL for Web open-source project (glimmer-dsl-web Ruby gem) starting around 2024 and won the international Fukuoka Prefecture Future IT Initiative 2025 award for it in January of 2025 from Matz and other Fukuoka judges. I have spoken at RubyConf (2008/2022/2023/2024), RailsConf (2012/2014), MountainWest RubyConf 2011, MagicRuby 2011, and AgileConf 2008. I am the organizer of the monthly Montreal.rb Ruby Meetup in Montreal, Canada. I have a Master’s Degree in Software Engineering from DePaul University, Chicago, USA and a Bachelor’s Degree in Computer Science from McGill University, Montreal, Canada. I have 23 years of Software Engineering professional experience and 20 years of Ruby/Rails experience.

Ruby on Rails Conferences Are Discriminatory, Unintelligent, and Hateful of Ruby in 2025

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 Frontend talks with Inertia and favored them over using Ruby even though  they are Ruby conferences believe it or not, and 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 RailsConf 2025 Frontend talk didn't highlight how Rails 6 broke its own Convention over Configuration principle by including a configuration heavy library like Webpack in Rails due to lack of intelligence in selecting Opal Ruby as a default instead. Had that happened, the Rails community would be 10 years ahead today, but it is in fact 10 years behind. Just because people aren't aware of that, that doesn't mean it's not true. Smart people think of what the highest potential that could have been achieved over the last 10 years had DHH didn't completely mess up and simp to the JS folks as a pushover instead of confidently sticking as a leader with the superior language he was already using in Rails, Ruby!

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 and incompetence 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. Otherwise, RailsConf 2025 actually provided outdated, incomplete, and inaccurate information about the Frontend story in Rails that neglected a Fukuoka Prefecture Future IT Initiative 2025 Award Winning Ruby on Rails Frontend library (Glimmer DSL for Web), neglected Opal (won an award in 2023), and neglected Ruby WASM entirely! The Ruby on Rails community is worse for it, and more importantly, customers are paying double the fee for Rails Software Development and getting the Software in double the time as a result. RailsConf was a weak conference that degraded developers' skills. Still, everybody makes mistakes, but good people apologize when they are made aware of their mistakes, and they redeem themselves as a result. I do make mistakes and say sorry at work from time to time. I say sorry because if I don't, customers suffer like they're suffering today from terrible React/Inertia codebases. Devs not realizing that doesn't mean the codebases aren't terrible (the Dunning-Kruger effect) when the devs could have done half the work in half the time using Frontend Ruby and contributed to the betterment of Ruby in the Frontend as well. 

Honestly, saving 6 months of Frontend work a year via Frontend Ruby (vs doing 12 months of work in JavaScript) 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 RailsConf 2025 talk provides that big a benefit to companies. 

Video for /dev/mtl 2024 Talk "Frontend Ruby with Glimmer DSL for Web"

The video for my /dev/mtl 2024 talk "Frontend Ruby with Glimmer DSL for Web" has been published!

It is totally mind blowing!!! 🤯

YouTube Video Link:

https://youtu.be/J2VIY9DMJo4

Presentation Slides (including the first 2 slides missing from the video recording due to technical difficulties):

https://docs.google.com/presentation/d/e/2PACX-1vTxzhV5596yjMt3rGVm1hMlsYlByKhW3LIesXdIfADQBAp_vQt6BsOHx24DKe9tFsnWRWrCQz3ByVbF/pub?start=false&loop=false&delayms=3000

Happy Holidays!!!

Glimmer Hangman (RubyConf 2024 Hack Day App)

During the RubyConf 2024 Hack Day Event for Glimmer DSL for LibUI, which was associated with the RubyConf 2024 workshop "How To Build Basic Desktop Applications in Ruby", I started the implementation of Hangman, the word game, in Ruby as a GUI desktop app. Well, I am happy to announce that I finally worked on it again yesterday and completed it, releasing version 1.0.0! And, it's implemented with some of the most amazing Ruby code! Just install the `glimmer_hangman` Ruby gem and run the command `hangman` and you'll have the game running on your machine instantly!

Project GitHub:

https://github.com/AndyObtiva/glimmer_hangman

Ruby Gem:

https://rubygems.org/gems/glimmer_hangman

I am including the project README and code below.

Merry Christmas!

Project README:

Project Code:

app/glimmer_hangman/model/game.rb

app/glimmer_hangman/view/hangman.rb

app/glimmer_hangman/view/hangman_scene.rb

app/glimmer_hangman/view/hangman_guess.rb

app/glimmer_hangman/view/hangman_guessed_letters.rb

Video for RubyConf 2024 Workshop "How To Build Basic Desktop Applications in Ruby"

The video for my RubyConf 2024 Workshop "How To Build Basic Desktop Applications in Ruby" has been released:

https://www.youtube.com/watch?v=TTSqRdTVtDY

This video is not only useful to Ruby Developers who want to learn how to build basic desktop applications in Ruby with the Fukuoka Ruby 2022 Award Winning Glimmer DSL for LibUI (Prerequisite-Free Ruby Desktop Development Cross-Platform Native GUI Library), but also to Rails Developers who want to build Rails productivity tools as Ruby gems (e.g. the rails-gui gem offers a user-friendly fast GUI for rails routes), leverage all the awesomeness of Glimmer in the Frontend of Rails applications 🤯 (in the workshop, I mention a new Glimmer DSL for Web that has all the features of Glimmer desktop gems tailored for Rails Frontend Development), and improve their skills in Object Oriented Programming, Software Architecture, and Software Design in general, like how to apply MVC (Model-View-Controller) & MVP (Model-View-Presenter) correctly to improve productivity and maintainability, instead of doing things the Rails MVC way, which is not completely correct. 

Here are some interesting requests I received from attendees at RubyConf 2024:

• Write a book about how to build GUI Desktop Applications with Ruby (I actually started writing such a book about 4 years ago, but then got pulled into building Glimmer DSL for LibUI and winning a Fukuoka Ruby 2022 Special Award for it; the book is still a great idea! I will keep it in mind.)
• Build a code editor that supports live GUI updates (I blogged more details about this topic here: https://andymaleh.blogspot.com/2024/12/the-dcr-kids-programming-language.html)
• Build a Glimmer DSL for DragonRuby to simplify Game Development with a Ruby DSL

Also, during the follow-up RubyConf 2024 Hack Day Event, we got to build Hangman and a Hockey joke AI app.

Happy learning!

Here is the GitHub repository with the workshop code exercises and test solutions:

https://github.com/AndyObtiva/how-to-build-desktop-applications-in-ruby/tree/rubyconf2024

Here are the workshop presentation slides:

https://docs.google.com/presentation/d/e/2PACX-1vSAaFLYeyolSy2Qe2tW0djv78tA-m120i4DJyaJ4qAHoWpv5Xppn_-yIpg4_IAGntetZkRDkkuT2zXN/pub?start=false&loop=false&delayms=60000&slide=id.g140fe579a5a_0_0

Code Exercises & Slides for RubyConf 2024 Workshop: "How To Build Basic Desktop Applications in Ruby"

Below is the GitHub repo that contains the code exercises and slides of the RubyConf 2024 Workshop: "How To Build Basic Desktop Applications in Ruby". Everyone can go through them at their own time.

GitHub:

https://github.com/AndyObtiva/how-to-build-desktop-applications-in-ruby/tree/rubyconf2024

Slides (Online):

https://docs.google.com/presentation/d/e/2PACX-1vSAaFLYeyolSy2Qe2tW0djv78tA-m120i4DJyaJ4qAHoWpv5Xppn_-yIpg4_IAGntetZkRDkkuT2zXN/pub?start=false&loop=false&delayms=60000&slide=id.g140fe579a5a_0_0

YouTube Video:

https://www.youtube.com/watch?v=TTSqRdTVtDY

Thanks to everyone who attended the RubyConf 2024 workshop and the follow-up Hack Day event.

One of the attendees, Scott Werner, built an AI joke generator desktop GUI app with Glimmer in Ruby.

And, a scaffolding of Hangman was generated at the Hack Day event too (you can star and watch the project to follow its development to completion): 

https://github.com/AndyObtiva/hangman

Glimmer on!!!

Laptop Instructions for RubyConf 2024 Workshop "How To Build Basic Desktop Applications in Ruby"

My RubyConf 2024 2-hour workshop "How To Build Basic Desktop Applications in Ruby" has been added to the RubyConf schedule. It requires attendees to follow setup instructions on their laptops before attending the workshop to hit the ground running at the event. 

The workshop will take place at "Salon A2" in the Hilton Chicago Downtown hotel (Chicago, Illinois, USA) on Day 2 (Thu, Nov 14, 2024) from 11:15am till 1:15pm. 

Full workshop material will be published on the day of the workshop at the GitHub repository below, which in the meantime includes setup instructions that must be followed on your laptop before attending the workshop (please bring your laptop to the workshop):

https://github.com/AndyObtiva/how-to-build-desktop-applications-in-ruby

After lunch, the workshop theme will continue in a Hack Day event at "Main Stage - Ballroom South" from 3:45pm till 5:45pm, in which #RubyConf attendees could continue learning and playing around with Ruby desktop exercises, build desktop applications individually or in collaboration with others, and/or ask me questions about desktop development in Ruby.

Slides & Code for RubyConf 2023 Workshop "How To Build Desktop Applications in Ruby"

Thanks to everyone who attended my RubyConf 2023 2-Hour Workshop "How To Build Desktop Applications in Ruby". 

I am happy the event's large ballroom filled up completely with attendees. For those who missed the event, I posted the presentation slides and code exercises (27 exercises) on GitHub. If you are at RubyConf 2023 and have further questions about the workshop, feel free to hit me up on the RubyConf 2023 Slack group or reach out to me via a Glimmer DSL for LibUI Issue or Glimmer Gitter Chat.

Slides/Code GitHub Repo: 

https://github.com/AndyObtiva/how-to-build-desktop-applications-in-ruby

Embedded Slides:

After the workshop, I hosted a RubyConf 2023 Community Day Glimmer Desktop Hacking event. Thanks to everyone who joined me there too. The product of that Hacking session was the Glimmer DSL for LibUI Game App: Color The Circles, which was produced using Application Scaffolding and a refactoring of the original example included in Glimmer DSL for LibUI.

https://github.com/AndyObtiva/color_the_circles

Happy Glimmering!!!

RubyConf 2023 How To Build Desktop Applications in Ruby (Workshop Accepted)

My RubyConf 2023 workshop submission titled "How To Build Desktop Applications in Ruby" has been accepted! It will take place in San Diego, California, USA on Monday, November 13, 2023 at 10am PT. Workshop seating is limited, so please RSVP for your spot over here! This workshop expands on last year's RubyConf 2022 talk "Building Native GUI Apps in Ruby".

RubyConf 2023 Workshop Details: 

https://rubyconf-2023.sessionize.com/session/531448

How To Build Desktop Applications in Ruby (2 hours):

Learn how to build desktop applications in Ruby with hands-on code exercises! 

Workshop outline (every step will involve a hands-on exercise or more):

1. GUI Basics (Controls, Properties, and Listeners):

2. MVC (Model-View-Controller) Software Architecture

3. Data-Binding and MVP (Model-View-Presenter) Software Architecture 

4. Advanced Data-Binding

5. Area (Canvas) Graphics

6. Drag & Drop

7. Custom Components (Custom Controls, Custom Windows, Custom Shapes)

8. Application Scaffolding

This workshop will be conducted using Glimmer DSL for LibUI, the prerequisite-free ruby desktop development cross-platform native GUI gem that won a Fukuoka Ruby 2022 Special Award after getting judged by Matz, the creator of Ruby.

Rails Remote Conf 2022 Talk Accepted - Ultra Light Wizard

Update 2022-09-12: Correction! the conference will take place February 6-10, 2023, not in September of this year.

My talk proposal for Rails Remote Conf 2022 (Feb 6-10, 2023) titled "Ultra Light Wizard" has been accepted!

Abstract:

Ultra Light Wizard is an approach for building multi-step forms in Rails that avoids issues like code duplication, endless conditionals, and confusing mixing of concerns. That is achieved by adhering cleanly to REST, MVC, OOP, Design Patterns, DDD, and Non-Functional Requirements such as Productivity, Maintainability, Performance, and Security. This presentation will cover common pitfalls in building Rails wizards, how to overcome them with the Ultra Light Wizard approach, and Ruby gems that help with implementing this architectural pattern.

RubyConf 2022 Talk Accepted - Building Native GUI Apps in Ruby

My talk proposal for RubyConf 2022 (Houston, TX, USA / Nov 29 - Dec 1) titled "Building Native GUI Apps in Ruby" has been accepted! It is scheduled as a 30-minute talk on Thursday, Dec 1, 2022 at 1:45pm. Come see it and tell others about it too!

Abstract:

Ruby is an excellent choice for building desktop apps with a native GUI (Graphical User Interface) that looks familiar on Mac, Windows, and Linux. In fact, Ruby pushes the boundaries of developing such apps in brand new ways not seen in web development by supporting very lightweight and declarative GUI syntax including bidirectional data-binding, thanks to Glimmer DSL for LibUI, a gem that won a Fukuoka Ruby 2022 Special Award. In this talk, I will cover concepts like the GUI DSL, data-binding, custom controls, area graphics, drag & drop, MVC/MVP pattern, and scaffolding, with sample demos.

Update 2022-12-02:

Slides have been posted: http://andymaleh.blogspot.com/2022/12/rubyconf-2022-slides-glimmer-dsl-for.html

Update 2023-02-08:

Video has been posted: https://andymaleh.blogspot.com/2023/02/rubyconf-2022-talk-video-for-building.html

Presenting at RailsConf 2014

Update: here are the links to the talk video and slides

My talk "Ultra Light and Maintainable Rails Wizards" has been added to the RailsConf 2014 program

Abstract:

Wizards have been common in web applications since the dawn of the Internet, with the most popular example being the Shopping Cart, yet many struggle with writing wizard code effectively, resulting in a huge untraceable rat's nest of copy/paste code. In fact, many implementations violate REST and include Fat Controllers as well as overly complicated wizard-step management, data, session, and validation code. This talk covers a better way that yields Ultra Light and Maintainable Rails Wizards!

If you have any special requests to include in the talk, please let me know in the comments.

Looking forward to connecting with Rails developers at RailsConf 2014.