The video of the Jan 2024 Montreal.rb Ruby Meetup A.I. talk "Building an AI
Medical Scribe in Ruby" by Jean-Sebastien Boulanger (CTO of Circle Medical)
has been posted. Description: "In this talk, I'll share insights from our
experience creating an AI medical scribe using Ruby at Circle Medical, a
hybrid primary care provider seeing over 50,000 patients monthly. We
leveraged Large Language Models (LLMs) to create a scribe to enhance
clinical documentation and save doctors' time."
https://www.youtube.com/watch?v=BJwILlX0svw&list=PLRAf4zt5oEjc2mqmEN9m_O0Jo…
minitest version 5.21.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.21.2 / 2024-01-17
* 1 bug fix:
* Fixed bug in Minitest::Compress#compress formatting w/ nested patterns. Now recurses properly.
ruby_parser version 3.21.0 has been released!
* home: <https://github.com/seattlerb/ruby_parser>
* bugs: <https://github.com/seattlerb/ruby_parser/issues>
* rdoc: <http://docs.seattlerb.org/ruby_parser>
ruby_parser (RP) is a ruby parser written in pure ruby (utilizing
racc--which does by default use a C extension). It outputs
s-expressions which can be manipulated and converted back to ruby via
the ruby2ruby gem.
As an example:
def conditional1 arg1
return 1 if arg1 == 0
return 0
end
becomes:
s(:defn, :conditional1, s(:args, :arg1),
s(:if,
s(:call, s(:lvar, :arg1), :==, s(:lit, 0)),
s(:return, s(:lit, 1)),
nil),
s(:return, s(:lit, 0)))
Tested against 801,039 files from the latest of all rubygems (as of 2013-05):
* 1.8 parser is at 99.9739% accuracy, 3.651 sigma
* 1.9 parser is at 99.9940% accuracy, 4.013 sigma
* 2.0 parser is at 99.9939% accuracy, 4.008 sigma
* 2.6 parser is at 99.9972% accuracy, 4.191 sigma
* 3.0 parser has a 100% parse rate.
* Tested against 2,672,412 unique ruby files across 167k gems.
* As do all the others now, basically.
Changes:
### 3.21.0 / 2024-01-15
* 18 minor enhancements:
* (internal) Added simple RubyLexer#comment.
* (internal) Removed RubyLexer#comments and #ignore_body_comments.
* (internal) Removed RubyParser#comments.
* (internal) Renamed files from lib/ruby##_parser.* to lib/ruby_parser##.*
* (internal) Renamed lib/ruby3_parser.yy to lib/ruby_parser3.yy
* (internal) Renamed lib/ruby_parser.yy to lib/ruby_parser2.yy
* Added tentative 3.2 support. (torrocus)
* Made `rake compare` a multitask (28s -> 10s!!).
* Made `rake compare` depend on `generate` (from clean: 28s -> 18s).
* No longer package versioned .y files.
* Overhaul of parser/lexer comment processing.
* Parser productions for k_class/k_module/k_def carry their comment with them.
* Restructured build tasks to utilize Hoe's .yy support! 8.5s -> 1.2s!!!
* RubyParser new_(class|module|defn|defs) handle comment processing via sexp.
* RubyParser new_(class|module|defn|defs) handle normalizing production sexps.
* RubyParser#next_token clears out lexer's comment when applicable.
* Simplified parser productions for defn_head, defs_head. No more normalizing.
* Updated `rake compare` steps for lrama in ruby 3.3+.
* 6 bug fixes:
* Cleaned out cruft from `rake compare` code.
* Fixed compare/normalize.rb for lrama differences.
* Made `parser` task depend on `isolate` task to pick up racc generator.
* Made racc a runtime dependency (was dev only) now that ruby 3.3 doesn't ship with the racc runtime. (wildmaples)
* Updated README.rdoc updating instructions to match current filenames.
* Updated compare versions and added 3.3.
sexp_processor version 4.17.1 has been released!
* home: <https://github.com/seattlerb/sexp_processor>
* rdoc: <http://docs.seattlerb.org/sexp_processor>
sexp_processor branches from ParseTree bringing all the generic sexp
processing tools with it. Sexp, SexpProcessor, Environment, etc... all
for your language processing pleasure.
Changes:
### 4.17.1 / 2024-01-15
* 1 minor enhancement:
* Added 3.3 to pt_testcase.rb
This release fixes a very annoying restriction for doxygen and improves and extends
Wx::ComboCtrl support.
wxRuby3 is a cross-platform GUI library for Ruby, based on the mature wxWidgets GUI
toolkit for C++. It uses native widgets wherever possible, providing the correct look,
feel and behavior to GUI applications on Windows, OS X and Linux/GTK. wxRuby aims to
provide a comprehensive solution to developing professional-standard desktop
applications in Ruby.
wxRuby3 also provides extensive and complete reference documentation.
What's changed in this release:
- the (very annoying) restriction on more recent doxygen versions has been
removed (thanks go to the wxPython Phoenix team for working this out); it
is now possible to build using the most recent versions of doxygen (this
should make it possible to build on any recent Linux distribution without
problems)
- improve and extend support for Wx::ComboCtrl and user defined popup controls
and update documentation
- add regression tests
If you are interested check this out:
Documentation: https://mcorino.github.io/wxRuby3/index.html
Github: https://github.com/mcorino/wxruby3
Rubygems: https://rubygems.org/gems/wxruby3
Last September, I gave a talk titled "Intro To Ruby in the Browser" about
how to use Ruby for Frontend Development in Rails as a complete replacement
for JavaScript as per Matz's RubyConf 2022 Keynote Speech. I concluded the
talk by mentioning a then up and coming project called Glimmer DSL for Web
that would make Ruby in the Browser the simplest, most intuitive, most
straight-forward, and most productive Software Engineering experience in
Frontend Development in any Programming Language or Technology. Well, The
future is now! Glimmer DSL for Web (Ruby in the Browser Web GUI Frontend
Library) just had its 0.2.2 Beta Release!
Continue reading blog post article at :
https://andymaleh.blogspot.com/2024/01/glimmer-goes-web.html
GitHub Repo for Glimmer DSL for Web ( Ruby in the Browser Web GUI Frontend
Library ) :
https://github.com/AndyObtiva/glimmer-dsl-web
RubyGem ( glimmer-dsl-web ) :
https://rubygems.org/gems/glimmer-dsl-web
minitest version 5.21.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.21.1 / 2024-01-11
* 1 bug fix:
* Rails' default backtrace filter can't currently work with caller_locations, so reverting back to caller.
minitest version 5.21.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.21.0 / 2024-01-11
* 10 minor enhancements:
* Add include_all kw arg to assert_respond_to and refute_respond_to.
* Added --quiet flag to skip ProgressReporter (prints the dots). Minor speedup.
* Added Minitest::Compress#compress and added it to UnexpectedError.
* Added ability to initialize BacktraceFilter w/ custom regexp.
* Filter failure backtraces using backtrace_filter before calculating location. (thomasmarshall)
* Make BacktraceFilter#filter compatible with locations (still compares strings).
* Optimized Assertion#location ~30%.
* Output relative paths for all failures/errors/backtraces.
* Refactored location information in assertions, now using locations.
* Removed thread and mutex_m dependencies. (hsbt, eregon)
* 2 bug fixes:
* Drop undocumented bt arg in #skip. Dunno why that ever happened, prolly for testing?
* Fix mock to work with ruby debugger enabled. (keithlayne)
This release brings extended and improved configuration support as well as support for
the Wx persistence framework including documentation for both.
wxRuby3 is a cross-platform GUI library for Ruby, based on the mature wxWidgets GUI
toolkit for C++. It uses native widgets wherever possible, providing the correct look,
feel and behavior to GUI applications on Windows, OS X and Linux/GTK. wxRuby aims to
provide a comprehensive solution to developing professional-standard desktop
applications in Ruby.
wxRuby3 also provides extensive and complete reference documentation.
What's changed in this release:
- extend and improve Wx configuration support
- add Wx configuration documentation
- add support for the Wx persistence framework
- add persistence framework documentation
- extend regression tests
- improve nested enum enumerator resolving support
- fix some code generation issues
If you are interested check this out:
Documentation: https://mcorino.github.io/wxRuby3/index.html
Github: https://github.com/mcorino/wxruby3
Rubygems: https://rubygems.org/gems/wxruby3
