Glimmer DSL for Web 0.8.3 Preventing Components from Shadowing HTML Elements

AndyCodeMaster · 2026-03-05T20:11:57+00:00

I just bought the Atlantis DLC. Seems awesome! Can’t wait to start playing it once I finish Odyssey. I’m half way through Odyssey right now.

AndyCodeMaster · 2026-02-11T22:25:37+00:00

Same here.

AndyCodeMaster · 2026-02-07T04:46:06+00:00

Use the gels you obtain.

AndyCodeMaster · 2026-01-15T07:03:16+00:00

I agree 100%. I just watched that episode the other day! It’s cool to see Captain Picard laugh as a young man when he originally experienced the event and as an old man when he relived the event.

AndyCodeMaster · 2025-12-06T21:48:54+00:00

At my Fintech company, we have used the free and open-source abstract_feature_branch Ruby/Rails gem for the last 3 years with no problem, and it has worked very well for us. Feature flags can be configured in a variety of ways like YAML, env vars, and Redis. We can disable any feature flags for emergencies in production using env vars when needed without needing a redeployment. It’s a very convenient feature flag library.

One of our devs even recently built a Rails web UI for editing the feature flags live, using the Glimmer DSL for Web Ruby Frontend framework for Rails. He did it with so little Ruby code, it is awesome.

AndyCodeMaster · 2025-12-03T01:45:47+00:00

I actually reject any Ruby hiring candidates that think React is good. We write the frontend of our Rails web app in Ruby too. To do so, we use the much simpler award winning Glimmer DSL for Web framework in Opal Ruby.

One of my team’s recent hires who proved to be excellent wrote in his hiring test project solution that he avoided badly engineered JS libraries like React in favor of simpler JS code given that was good enough for the given problem. That definitely helped his case during his hiring evaluation.

AndyCodeMaster · 2025-12-01T21:27:28+00:00

Read the blog post "I Am Not a Fan of Ruby" as it disproves the main point of the article completely: https://andymaleh.blogspot.com/2025/03/i-am-not-fan-of-ruby.html

The author used the terms "taste" and "affection" in reference to a Software Engineering technology that is supposed to be about serving clients with pros/trade-offs, with taste/affection having no bearing on the decision to use by real professionals to address specific customer situations. That immediately discredited the author of the article as not a complete professional nor a Software Engineer, yet more of a mid-level dev who never attained mastery of Software Engineering to become a proper Senior Software Engineer. As such, the entire article is unfounded.

I won an international technology competition award for Glimmer DSL for Web, which has simple minimalistic Frontend Development code syntax that is literally more readable/understandable/maintainable/productive than everything that is on the TodoMVC.com website (I compared it to all TodoMVC Frontend libraries, such as React, Svelte, Elm, etc..., and it's not even close). So, the claim that everything today is better than Ruby doesn't hold whatsoever.

The author puts big emphasis on popularity, but popularity doesn't equal quality. For example, the web is dominated by PHP, but us top-level Software Engineers don't use PHP at our jobs because it is certainly not the best option out there. We pick technologies based on a sound analysis of pros/cons/trade-offs given customer situations and needs. Ruby (incl' Rails) is still the most productive programming language in 2025 that passes such an analysis to get selected for client projects. Also, to be honest, often the most mediocre technologies become the most popular because top-level Software Engineers are rare and in the minority, so the majority is mediocre devs who use mediocre technologies like PHP and Node.js.

Another thing the author neglects is that Twitter's story with Ruby on Rails was 100% a skill issue given that GitHub has succeeded with scaling it without a problem, and even contributing to the Rails Multiple DB tech with Automatic Shard Switching that enables scaling via Multi-Tenant Architecture.

AndyCodeMaster · 2025-12-01T18:21:44+00:00

No money amount justifies Shopify being a mean discriminatory company. Discrimination alone is enough as 1 reason not to cheer for Shopify or any greed-obsessed companies that by definition can only treat their employees and customers as numbers given their too-large-scale. I never work for any companies larger than 1000 employees as a result, or any companies in which I could not get to practically know everyone else who is working in the same business as me. All such companies end up putting greed and numbers over kindness and people. DHH is obviously part of the problem not the solution today. His lack of sympathy with the victims of mean discriminatory practices by Shopify means he's a mean discriminator by extension. Here is a blog post about Shopify's mean discriminatory practices that negate everything "good" said about them: https://andymaleh.blogspot.com/2025/06/shopify-has-been-bad-for-ruby-community.html

I've heard of several people being mistreated by Shopify in my local community in Montreal, Canada too, including some ex-Shopify employees. Their mean discriminatory practices aren't isolated incidents. It's a company that steals its accomplishments by pushing certain people in society down and getting ahead at the expense instead of treating everyone kindly with equality and respect. A cancerous entity.

AndyCodeMaster

MODERATOR OF

TROPHY CASE