Re:Design Principles Behind Smalltalk (1981)
by codetrotter on Saturday June 13, 2020 @11:21AM
(#23510044)
Speaking of Ruby, there is this book that I read a few years ago (five years ago, in fact – time flies), that was using Ruby when explaining the things it was talking about.
Personally I don’t use Ruby and prefer Python instead, but the book was very enjoyable nonetheless so I would recommend that book to anyone, even to people like me who don’t really like Ruby in general and don’t really want to read or write Ruby in general.
Stuart, T., 2013. Understanding Computation: From Simple Machines To Impossible Programs. O’Reilly.
Book website: https://computationbook.com/
Re:Design Principles Behind Smalltalk (1981)
by AdieuToLogic on Saturday June 13, 2020 @05:01PM
(#23512690)
Another good "non-rails" Ruby book is "Enterprise Integration with Ruby"[0]. Unfortunately, it's a bit dated (2006), so I am sure some of what Schmidt details is no longer supported/valid. Still, a cool book IMHO.
0 - https://www.amazon.com/Enterprise-Integration-Ruby-Maik-Schm...
Re:Design Principles Behind Smalltalk (1981)
by joshhogg on Saturday June 13, 2020 @01:00PM
(#23510804)
This books looks super interesting. Did you find any of it applicable to particular problems you are working on or was it good general knowledge?
Re:Design Principles Behind Smalltalk (1981)
by codetrotter on Saturday June 13, 2020 @03:00PM
(#23511764)
As good general knowledge yes
Re:Design Principles Behind Smalltalk (1981)
by zengargoyle on Sunday June 14, 2020 @05:29AM
(#23516260)
I didn't give Ruby a second thought after hearing Matz say something along the lines of being a bit sad that people were using it because it meant that he couldn't change it anymore. It was his toy language that escaped his control and now he had to worry about compatability and couldn't just break things. It's not a good sign when the creator didn't want it to be used that much.
I wish Ruby had taken Python's spot. When Rails exploded ~2006, I thought it'd become a mainstream language. But sadly it has never been very popular for non-web things, if we exclude Japan.
One reason is probably that the standard Ruby implementation (MRI) was really slow till recently. Smalltalk, on the other hand, had extremely good VMs that served as embryo for the JVM.
I've used Ruby for many big projects (but never used Rails!) and it has scaled really well for large and exotic things such as abstract interpreters.