plots2 VS JRuby

Citizen science! It's great when people realize they can answer their own questions with observation and data, and for activism because data is a powerful story. One friend of mine started https://publiclab.org to feed this, and another is doing data journalism to highlight holes in the government's environmental data. https://www.muckrock.com/project/

My first contribution ever was to PublicLab's plots2 back in 2018. I had no idea what I was doing or what plots2 was. What attracted me was how welcoming they were (and still are) to first time contributors. With them: I opened my first PR, discussed in PR's conversation, and pushed the changes requested. Back then, that was a lot!

Hmm so to your first question: That pattern of selecting from a pre-populated list is often used with a tag or chip system where you can select and deselect one or more items from the list, something like this: https://github.com/publiclab/plots2/issues/6026 in this case the search CTA acts as the final decision to search while the selections are populating the search criteria. It sounds your system design is a bit different though. Sounds to me like an issue of heuristics of UI https://www.nngroup.com/articles/ten-usability-heuristics/ the third heuristic states:

Maybe public lab would be a good home? https://publiclab.org/

https://github.com/publiclab/plots2 A collaborative knowledge-exchange platform in Rails; we welcome first-time contributors! balloon

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/

Chris: Yeah, that's exactly right. So I was working at Sun at the time. I remember the JRuby guys. I saw them speak at one of the Java conferences, and they came to work for Sun. Just listening to them talk about JRuby...and then a lot of it was obviously about Ruby on Rails at the time. And I was like, wow, this was just mind-blowing the way they talked about it.

In fact, I built its GUI twice with two different approaches, one using the up and coming Glimmer DSL for LibUI on CRuby relying on a multi-canvas-grid (LibUI area) approach, and one using the very mature Glimmer DSL for SWT on JRuby by relying on a button-grid approach.