JRuby VS glimmer-dsl-swt

Another way to look at it based on coming across it in enterprise:

How did he build something adopted by so many enterprises?

It does some things at scale very well and has been afforded the performance improvements of very smart people for 30y.

It’s not to say the language isn’t verbose, one of my favourite features was the ability to write code in other languages right inside the a Java app pretty well in-line by using the JVM, thanks to JSR-223.

It was possible to write Ruby or Python code via Jruby or Jython and run it in the JVM.

https://www.jython.org/

https://www.jruby.org/

https://docs.oracle.com/javase/8/docs/technotes/guides/scrip...

As someone who has looked at Shoes several times but never dove in, it's confusing how Shoes 4 has been the "preview version" of Shoes for, like, a decade or more. It made me actively avoid getting invested in Shoes 3 (the release promoted on the linked website) because Shoes 4 requires JRuby and I am happy with CRuby (the Ruby interpreter most people think of when they hear "Ruby").

https://github.com/shoes/shoes4/

http://www.rubydoc.info/github/shoes/shoes4

No disrespect to the developers but to me it feels like taking over a GUI toolkit created "to teach programming to everyone" (to quote the Shoes 4 readme) and making it depend upon a super-complicated enterprise-focused Ruby was sort of Missing The Point™ in a huge way.

Heck I couldn't even switch to JRuby if I wanted to because I <3 Ractors and JRuby still lacks CRuby 3.0 feature parity: https://github.com/jruby/jruby/issues/7459

__callee__ now properly returns the name under which a method was called, which will be the new name in the case of aliased methods. #2305, #7702

Issue tracker: https://github.com/jruby/jruby/issues

rdoc has been updated to 6.3.3 to fix all known CVEs. (#7396, #7404)

Altering the visibility of an included module method no longer changes what super method gets called. (#7240, #7343, #7344, #7356)

It looks like the readme is copy pasta from jruby: https://github.com/jruby/jruby

Homepage: https://www.jruby.org/

Well, I am happy to announce that the same single line of code that data-binds a table does even more now as of the latest release made yesterday! In Glimmer DSL for SWT v4.24.3.0, that line of code also data-binds the following additional table cell properties without any change to the view code:

There are various limitations, no doubt. I don't mean to imply otherwise. And I am not sure if it is equivalent to shoes (though glimmer-swt may be equivalent, check it out here: https://github.com/AndyObtiva/glimmer-dsl-swt although it also uses java so it's not identical to shoes either).

Glimmer DSL for SWT v4.24.0.2 has been released with the following changes:

SQLite is the simplest relational database to use from JRuby desktop applications, it is built-in on all platforms (Mac, Windows, and Linux), and it can be utilized conveniently via ActiveRecord, the Rails object-relational mapping library following the Active Record Enterprise Application Architecture Pattern. In fact, I have used it a few years ago to build Are We There Yet?, a small project management app, using Glimmer DSL for SWT and bidirectional data-binding. In this blog post tutorial, I cover how to configure a SQLite database and connect to it using ActiveRecord from within a Ruby desktop application, data-binding the ActiveRecord Model to the GUI View bidirectionally.

Native Executable Packaging for CRuby (Glimmer in JRuby already has Native Executable Packaging support for building Mac APP/DMG/PKG files, Windows EXE/MSI files, and Linux DEB/RPM files)

Happy Glimmering!