I shared positive feedback about Glimmer DSL for Web (Ruby-in-the-Browser Frontend Framework for Rails) in the quoted post (you can read it if you haven't yet), but not negative feedback. That's because I didn't get any negative feedback by the end of my Glimmer DSL for Web workshop at wroclove.rb 2026. Attendees were excited about having a new effective way of doing Frontend Development with Ruby inside Rails web applications. One of the attendees said it was promising. Another told me he thinks React.js is horrible (I'm glad there are other smart devs in the Ruby community who are aware of React's issues and weaknesses), and normally uses Vue.js for Frontend Development, but is excited that Glimmer DSL for Web is even better than Vue due to using Opal Ruby (that enables unique things through Ruby DSL syntax not possible with straight JS and HTML).
That said, on the 3rd day of wroclove.rb 2026, someone played around with Glimmer DSL for Web in a new Rails web project and gave me one piece of negative feedback. He said it was difficult to set up Glimmer DSL for Web manually in a Rails web app, indicating that he would have expected instructions to just involve adding the glimmer-dsl-web Ruby gem to Gemfile and running 1 Rails generator command to generate the opal Frontend code directory (albeit the project requires about 5 steps to be followed to set it up).
I heard you loud and clear! I will work on implementing automation of setup instructions, hopefully in the near future. I am sorry I didn't automate setup instructions yet even though i was aware they are cumbersome. At my job, the project is already set up, so I have been more consumed with adding features to it that we need at work; I didn't get a chance to focus on automating setup instructions. But, this will definitely be a top priority for the upcoming version 1.0.0 release.
#glimmer #dsl #web #ruby #rails #rubyonrails #frontenddevelopment #frontend #dev #programming #softwareengineering #deletejs #deletereact