Shoes – An easy little GUI toolkit for Ruby
shoesrb.com
shoesrb.com
I miss you, _why.
I’ve found a similar feeling in the javascript community. There’s a few characters who have changed the way we even recognise the language these days. It’s not quite _why’s beautifully artistic approach, but it has been genuinely exciting working with JavaScript in the last decade.
> Shoes 4 is a total re-write of Shoes. It's being done in JRuby with best practices. It re-implements the original Shoes 3 definition of Shoes in a pure Ruby friendly way whereas Shoes 3.x is more difficult for Rubyists to modify since it has C and Objective-C components and a build process that is less than easy to understand. Shoes 3.2 also has hardware costs and web hosting costs which makes if difficult for many developers to duplicate.
http://shoesrb.com/manual/Shoes.html
Nobody Knows Shoes link, follow the redirect, then second link from the bottom
I'm sure I have a copy but this should be the source. I'm actually on the Shoes maintainer list, so if nobody knows why, I know who to ask at the least...
This link got me there
https://www.google.com/url?sa=t&source=web&rct=j&url=http://...
Here's to you, _why - wherever you are.
> Pretend that you’ve opened this book (although you probably have opened this book), just to find a huge onion right in the middle crease of the book. (The manufacturer of the book has included the onion at my request.) So you’re like, “Wow, this book comes with an onion!” (Even if you don’t particularly like onions, I’m sure you can appreciate the logistics of shipping any sort of produce discreetly inside of an alleged programming manual.)
Additionally, has anyone used it for more complex applications or UIs? I'm just curious how easy it is to customize. Could be a nice alternative to Electron as I prefer Ruby to JS and Rust doesn't seem to have great UI support yet (from what I can tell, which is admittedly not much).
I know this is not meant to be a leading statement or a subtle dig, but it's left open enough for interpretation that I think it's probably why you got downvoted.
If you want to get performance out of your Ruby application and it needs to be multi-threaded, I think you usually switch to jruby. I've never had to do that, this is just what I've heard... how I personally read your statement is basically the opposite, as in "JVM is dragging you down, man" - whether that interpretation is warranted or not is left as an exercise for the reader
I am really not a fan of drive-by downvoters, by the way...
https://blog.qt.io/blog/2018/05/04/hello-qt-for-python/
I have very little experience with both outside of tinkering, but they will probably be gratifying and practical enough to build something that works to encourage him further.
More info: https://www.martinfowler.com/bliki/TwoHardThings.html
There are only two hard things in Computer Science: cache invalidation and naming things.
-- Phil Karlton
It's supposed to look like writing HTML, if your HTML writing was done in a builder syntax on a domain language in Ruby blocks. (But that's gibberish compared to the explanations found in NKS guide to Shoes.)
Edit: the book link