- ruby-talk - ml.ruby-lang.org

[ruby-talk:444692] Ruby, Rubinius, and AI
by Brian Shirai 01 Dec '25

01 Dec '25

Hello Rubyists! If you're interested in Ruby+AI, you may be curious about some recent developments with Rubinius. I've written them up here: https://vivarium-ai.com/newsletters/0-hello-world-who-is-out-there/ Cheers, Brian

1 1

[ruby-talk:444707] [ANN] DB GUI 0.3.0 & Glimmer DSL for LibUI 0.13.1 Released
by Andy Maleh 01 Dec '25

01 Dec '25

DB GUI 0.3.0 & Glimmer DSL for LibUI 0.13.1 have been released. DB GUI now supports remembering multiple database profiles, including which one was last selected. Glimmer DSL for LibUI now supports combobox items data-binding. https://raw.githubusercontent.com/AndyObtiva/db-gui/refs/heads/master/scree… Blog post announcement : https://andymaleh.blogspot.com/2025/11/db-gui-030-glimmer-dsl-for-libui-013… GitHub Projects : DB GUI : https://github.com/AndyObtiva/db-gui Glimmer DSL for LibUI : https://github.com/AndyObtiva/glimmer-dsl-libui Ruby Gems: db-gui : https://rubygems.org/gems/db-gui glimmer-dsl-libui : https://rubygems.org/gems/glimmer-dsl-libui

1 0

[ruby-talk:444700] The Embarrassing Ruby/Rails Subreddit Chronicles 2025-11-24
by Andy Maleh 25 Nov '25

25 Nov '25

Welcome to another edition of the Embarrassing Ruby/Rails Subreddit Chronicles. Attached are screenshots for another embarrassing incident demonstrating the mean/hateful nature of Ruby/Rails subreddit members and how they downvote without first having a nice and loving patient discourse in case of a misunderstanding or an uninformed disagreement. It hit me the other day that the reason I suffer from mean/hateful behaviour in the Ruby/Rails subreddits despite being a 2-time Fukuoka international competition winner (of awards by Matz, the creator of Ruby), a 4-time RubyConf speaker, and a 2-time RailsConf speaker is because they allow in people who are below the minimum bar of professionalism and respectful conduct that is required for hiring in a Software Engineering job at a respectful ethical company. I mean I wouldn't hire any of them in a million years, not just for lack of technical skills, but more importantly for not having the patient loving nice Rubyist personality. So, why do the Ruby/Rails subreddit mods allow in unnice/hateful people who are below the minimum bar of respectful conduct?! This is a negative reflection on the mods just as much as it is on the trash members of the Ruby/Rails subreddits. I say trash because they're no different from trash criminals and drug addicts I'd encounter on the streets in their behaviour. It's not the behaviour of a member of the Software Engineering community, let alone the Ruby/Rails community. In this screenshot, you can see a Ruby subreddit moderator asking for feedback about new rules, which in my opinion are embarrassingly fascist, even if I didn't say that in my comment about them. https://imgur.com/a/yS0W8z9 Here, you can see my response, and how it was immediately downvoted to 0 within 5 minutes of posting, demonstrating the mean hateful non-open-minded unsympathetic nature of Ruby subreddit members (not sympathizing with someone who says they received hateful behaviour means you are a hateful person). https://imgur.com/a/5aExMUF Of course, fascist rules are a red herring. They're a side effect to Ruby subreddit mods holding on to terrorists that they harbour within their group instead of letting them go as explained in this sentence: "If you worry too much about the rules, it means you have the wrong kind of people in the group, and that’s the real problem not being dealt with (eg allowing in haters of Ruby, people who don’t give Ruby the benefit of the doubt in applications that it’s not common in, people who are below the minimum bar of ethical respectful conduct and professionalism, etc…)." Here is my full comment, repeated here textually: "This group allows a lot of hate on Frontend Ruby. It also literally allows people who don’t truly like Ruby or get it to freely discuss JavaScript as better than Ruby while making true Rubyists who understand and appreciate Ruby’s benefits over JavaScript not feel safe in a Ruby group. This automatically renders the group a bad one. Also, I’ve encountered a lot of hateful behavior in this group against anything that’s novel and outside the box of what’s common in the software development community. 15 years ago, Rubyists were open minded about new novel ideas and patiently listened to them without downvoting. In this group today, such ideas get downvoted to zero in a very hateful unintelligent way without giving the poster the benefit of the doubt or even attempting to understand the benefits of what is shared. That discourages Rubyists from sharing new ideas or exploring them in this group in a respectful intelligent open minded manner. I personally make an effort not to downvote anyone, yet to ask questions and facilitate discussions if I disagree with something. In general, rules that are unethical or do not implicitly respect everyone equally only make the group a bad one. Lastly, politics are off-topic. Honestly, this is not a good group if it allows off-topic things while attempting to shift the blame unto the people who are right about the matter. That’s attempting to get out of responsibility, which is also bad. If you don’t understand this, you’re on the wrong side of this. I’m apolitical and don’t vote by choice by the way, so I don’t care to discuss this further because I don’t like discussing politics ever, especially not in a Ruby group not about politics. If you worry too much about the rules, it means you have the wrong kind of people in the group, and that’s the real problem not being dealt with (eg allowing in haters of Ruby, people who don’t give Ruby the benefit of the doubt in applications that it’s not common in, people who are below the minimum bar of ethical respectful conduct and professionalism, etc…). Update: Exhibit A: I have won 2 awards from Matz in very difficult international engineering competitions, and have spoken at RubyConf 4 times, and yet people don’t respect me, discriminate against me and hate me, unintelligently downvoting my posts out of hate and discrimination not for any intelligent reasons. Of course, this behavior is only an indirect reflection on the mods allowing hateful disrespectful people into a Ruby group without respecting the Ruby luminaries of the Ruby community. I was respected more 10-15 years ago when I wasn’t a very well accomplished Ruby Software Engineer back then because the Ruby group was run better back then." Blog post edition for sharing: https://andymaleh.blogspot.com/2025/11/the-embarrassing-rubyrails-subreddit…

5 5

[ruby-talk:444697] [ANN] minitest-server 1.0.9 Released
by Ryan Davis 21 Nov '25

21 Nov '25

minitest-server version 1.0.9 has been released! * home: <https://github.com/seattlerb/minitest-server> * rdoc: <http://docs.seattlerb.org/minitest-server> minitest-server provides a client/server setup with your minitest process, allowing your test run to send its results directly to a handler. Changes: ### 1.0.9 / 2025-11-20 * 1 bug fix: * Loosen dependency on minitest to work with MT6.

1 0

[ruby-talk:444696] [ANN] minitest-sprint 1.4.1 Released
by Ryan Davis 19 Nov '25

19 Nov '25

minitest-sprint version 1.4.1 has been released! * home: <https://github.com/seattlerb/minitest-sprint> * rdoc: <http://docs.seattlerb.org/minitest-sprint> Runs (Get it? It's fast!) your tests and makes it easier to rerun individual failures. Changes: ### 1.4.1 / 2025-11-18 * 1 bug fix: * OOPS! I'm using Data so I need to use ruby 3.2+

1 0

[ruby-talk:444695] [ANN] cel 0.4.0 released
by Tiago Cardoso 18 Nov '25

18 Nov '25

cel 0.4.0 has been released. cel is a pure Ruby implementation of Google Common Expression Language, https://opensource.google/projects/cel. The Common Expression Language (CEL) implements common semantics for expression evaluation, enabling different applications to more easily interoperate. ```ruby require "cel" # set the environment env = Cel::Environment.new(name: :string, group: :string) # parse ast = env.compile('name.startsWith("/groups/" + group)') # check prg = env.program(ast) # evaluate prg.evaluate(name: Cel::String.new("/groups/acme.co/documents/secret-stuff "), group: Cel::String.new("acme.co")) #=> true # or do it all in one go env.evaluate('name.startsWith("/groups/" + group)', name: Cel::String.new("/groups/acme.co/documents/secret-stuff"), group: Cel::String.new("acme.co") ) ``` Here are the updates since the last release: ## [0.4.0] - 2025-11-18 ### Features `cel-ruby` supports the defined set of [CEL extensions]( https://github.com/google/cel-go/blob/master/ext/README.md) math, string, bind and encoders. ```ruby Cel::Environment.new.evaluate("math.bitShiftLeft(1, 2) ") #=> returns 4 ``` ### Improvements When the `tzinfo-data` gem is loaded, expressions will support human-friendly timezones, such as "US/Central", for timestamps. ## [0.3.1] - 2025-08-01 ### Improvements * Support for depth protection, using the defaults from the spec (ex: recursion depth of 32, nesting depth of 32), and supporting API to override them (ex: `Cel::Environment.new(max_recursion_depth: 42))`). * lazy-evaluating bindings to avoid upfront costly transformations of ruby objects into cel objects which are ultimately not used in expressions. ### Bugfixes * `has()` macro correctly works for maps.

1 0

[ruby-talk:444694] [ANN] minitest-sprint 1.4.0 Released
by Ryan Davis 18 Nov '25

18 Nov '25

minitest-sprint version 1.4.0 has been released! * home: <https://github.com/seattlerb/minitest-sprint> * rdoc: <http://docs.seattlerb.org/minitest-sprint> Runs (Get it? It's fast!) your tests and makes it easier to rerun individual failures. Changes: ### 1.4.0 / 2025-11-17 * 1 minor enhancement: * Added multiple line number support: eg test.rb:42,50-100 (multiple files too) * 3 bug fixes: * Fixed exception raised when requiring default test that wasn't actually there * Fixed shebang on bin/minitest for linux * Set minimum ruby version to 3.1.

1 0

[ruby-talk:444693] [ANN] minitest 5.26.2 Released
by Ryan Davis 18 Nov '25

18 Nov '25

minitest version 5.26.2 has been released! * home: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 5.26.2 / 2025-11-17 * 5 bug fixes: * Bumped minimum ruby to 3.1. * Alias Spec#name to #inspect for cleaner output in repls. * Fix pathing for Hoe::Minitest initialization to be more generic. * Fixed refute_in_epsilon to use min of abs values. (wtn) * Improved options processing and usage output to be more clear.

1 0

[ruby-talk:444691] [ANN] minitest 5.26.1 Released
by Ryan Davis 08 Nov '25

08 Nov '25

minitest version 5.26.1 has been released! * home: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 5.26.1 / 2025-11-08 The Ocean Shores, Slightly Less Tipsy Edition! * 3 bug fixes: * Add links to API doco in README. * Add missing require thread. * Bumped ruby version to include 4.0 (trunk). (hsbt) (see also 5.14.2)

1 0

[ruby-talk:444690] [ANN] minitest 5.26.0 Released
by Ryan Davis 08 Oct '25

08 Oct '25

minitest version 5.26.0 has been released! * home: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * vim: <https://github.com/sunaku/vim-ruby-minitest> * emacs: <https://github.com/arthurnn/minitest-emacs> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 5.26.0 / 2025-10-07 The Seattle.rb Nerd Party, Slightly Tipsy Edition! * 2 minor enhancements: * Added extra documentation to Minitest::TestTask options. * Make parallelize_me! a no-op when n_threads=1. * 9 bug fixes: * Bypass parallel_executor entirely when n_threads=1. * Don't require rubygems in Rakefile... it is 2025. * Ensure that minitest exits non-zero on Interrupt. (tavianator) * Fix Minitest.run sequence rdoc to include loop vars and read consistently. * Fix call to parallel_executor.shutdown when it isn't defined. * Removed some 1.8/1.9-based code from the assertions and expectations. * Still fighting with rdoc? Yup. Still fighting with rdoc... * Switched assert_equal's diff from Tempfile.open to Tempfile.create. * Use Regexp.escape for BASE_RE in case pwd has special chars. (astra_1993)

1 0