Slashdot Mirror
Why's (Poignant) Guide to Ruby
Colonel Panic writes "Why the lucky stiff has written one of the most unusual (and poignant) books about programming that I've ever encountered. The best description for it so far (seen on comp.lang.ruby) is that it's sort of like 'The Little Prince meets SICP'. However, it defies all attempts at description (at least in this small space), you've got to read it for yourself. Like SICP, the full text is available for free. This one is destined to become a classic - it will likely be known to future generations of jobless American computer scientists as 'The Fox Book.'"
So did anyone actually not read the paragraph titled "But Don't Read This One!"?
:)
I'm proud to say that I skipped it.
I read the first bit, something about a dog... I think the author is on crack.
Mirror in case the site gets slashdotted
If you're religishitty, KILL YOURSELF!
Decimal numbers are called floats in Ruby.
Baaaaad name. Decimals are not floats. Floats are binary, decimals are decimals.
How do you call decimal numbers (full presition) in that lang.? Currency? Digits? Anyone?
...for the code for the book.
The list archives are here and the project site is here.
The Army reading list
It's amusing. I laughed several times. It's definitely different. Obnoxious, sometimes, but different in a cool sort of way.
... ?
Ruby seems like Perl, written to be a lot less obscure and much more object-oriented. Cool. And the style reminds me a bit of Mr Bunny's Guide to ActiveX. If you liked his book, you should read that too, whether you're interested in ActiveX or not.
But the non-existance of Chapter 4, just after the book started to get into the meat of things, was a bit of a non-starter.
I guess it will be ready for Slashdot in, well, six months.
Or twelve?
Or
I guess it's up to the LuckyStiff. Maybe he's doing luckier stuff nowadays.
D
Children could be taught to program early in their school years.
Yes, and that's what we have languages like Logo for. Or, if you want something readable and more adult, Smalltalk (and the Squeak.org environment). Python, of course, originally also was designed for education.
Ruby is a nice language, but I don't think it comes out of an educational background. It syntax is cleaner than Perl's but doesn't seem like it would be all that intuitive to non-computer users either (both Smalltalk and Logo seem better in that regard).
Altogether, Ruby just seems like an odd choice when it comes to really caring about teaching people to program. Not a bad choice, but not clearly better than the more obvious choices either.
OK, I'm definitely a curmudgeon. Still I think I'm right.
Nifty, but this is about three chapters too premature to be posting it on Slashdot.
Seriously, the author is biting a LOT off and while one chapter is a good start, it remains to be seen whether the author is biting off more then they can chew.
Truthfully, many programming languages are easy but even in this introduction there are signs that this isn't going to go down as well as the author would like, like the "symbols" discussion which I understood perfectly but is likely to make, say, my zoology-trained wife go "huh? so what are they good for? why not just use strings?"
You can also over-simplify Perl or Python this way too but when you start discussing @ISA or __metaclass__es, you're in trouble, and there is often just no way around those things, esp. if you're trying to read the code of others.
I am hopeful this will turn out well; it looks like a lot of fun and is full-unto-overflowing with personality, which can certainly reach out to a new audience. But it is also extremely ambitious and will be time consuming, so I must confess to a little bit of pessimism that that quality of output can be sustained all the way to the end of the book.
Oh, and entirely seperately, comparing a single chapter of an otherwise-unfinished book to the SICP disrespects the SICP. You do neither work a favor by comparing the two.
So painfully self-aware, cutesy, and po-mo-ironic that I think it gave me a stomachache.
Otherwise, it's pretty good.
While reading the text "i" was reminded of "Godel, Escher, Bach" by Douglas Hofstadter. Of course, this text was more "Poignant."
:while
"I" think.the difference was that Hofstadter wanted to talk to "computers" as if they were "old_wizened_demigods,"
here "Why_The_Lucky_Stiff" wants to talk to the "computer" as if it were an "Enraptured_Infant" called "Ruby."
and "I" mean it in a good way.
.
To see a world in a grain of sand, and then to step back and see the beach where the sand lies
Most serious programmers have tons of studying to do. So many tools and interacting technologies that change so rapidly....
A "classic", to me, is a book that puts the maximum amount of useful and usable knowledge in my head with the least amount of effort. This doesn't necessarily mean the shortest book. A "terse" book can take more time and effort to read than a longer book with better explanations.
But a book like this, with such a low useful_stuff/useless_fluff ratio, is not my idea of a classic.
"Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
There was Mr. Bunny's Big Cup 'O Java, too, which I ran across when a guy I worked with got a pre-publication review copy.
It was... entertaining, from what I recall, but I wouldn't recommend it for learning Java (well, it's out of date now anyway). But the main problem was that the book often sacrificed precision and accuracy for humor, and would have led to some strange misconceptions about Java, for a beginner reading it.
This book looks interesting, though I only skimmed the beginning (gotta get back to work) -- I'd be interested to hear a review from someone who really knows Ruby. Would it really be useful for someone learning the language, or is it better for getting people interested (...and convincing them to find a book with a more direct approach to actually learn the practical stuff)?
Here's the Mr. Bunny home page, anyway.
There are only 10 types of people: those who understand decimal, those who don't, and, uh, 8 other types I forget.
I'm already proficient in Ruby, and therefore learned nothing new from the Poignant Guide, but it was an amusing read nonetheless. I greatly enjoyed it, and have already recommended it to my coworkers and my wife. Even if you don't like Ruby, the available chapters are worth reading. I'm looking forward to the completion of the remainder of the book.
Like more robust libraries and some better documentation. I know mr. stiff has contributed to that end and I hope he doesn't waste more of his time on silly story books!
.. WOW, code just flowed from my fingers and I was constant amazed at how little effort it took to make a well-written program.
When I moved from Perl to Python for big projects, it was pretty cool. I could read my code, and it was a lot more consistent because of the built-in object support. Python doesn't exactly register high on the "elegance" meter but it works.
Then I tried Ruby
But, Python has all the docs and libs. So at work I use Python. I enjoy the new features that are being bolted on here and there, but it's got all the signs of a language that peaked in popularity before the design was finished.
So I don't use Ruby for much except code generation and other little tasks. I want to though.. I'm waiting until somebody writes better libs and docs, or at least until I have the time to contribute.
So please, less pretentious web sites, more English documentation.
This is amusing, but it could be more accurate, and better for the complete novice it's apparently aimed at.
Eg: "a variable is like a nickname". Meh. A variable is a box. The name of the variable is the label on the box. The value of the variable is the contents of the box.
Or again: the author says words starting with a colon are "lightweight strings". And then fails to say what a string is, or how much it weighs. I bet your average punter believes a string is a length of twisted fibre.
Having said that, if the author could keep on track with the intended audience, I would try this out on my daughter (aged 8).
regarding: "The one advantage that Ruby has over Smalltalk and Logo is that it's included with every copy of OS X. So is Perl, but please, please, please nobody teach children to program using Perl. It could doom us all!", I would like to say
That's even funnier than the emails I'm getting from the man who's causing me to smile those creepy "i'm thinking about a man" smiles at work these days.
Free Java games for your phone: Tontie, Sokoban
This mystical foutain of libraries. It's called CPAN.
Chunky.
Bacon.
I like the comics, they are sometimes funny and make concepts easy to remember. They may be silly, but people will remember them because of that. Hopefully, they will remember the concepts too.
"When God kisses Satan and the Incarnations applaud." "Death is dead. Long live Death!"
Normally, very little is lost by skipping ahead in a technical book. You're in a rush, and you just want to know how the new language maps into other languages you know. It is probably a mistake to read in this skip-ahead way, but in many cases the writing is so unengaging that we cannot stomach reading it all.
Well, the defining characteristic of this "book" is that some readers will find it enormously engaging, so much so that they will read all the words, starting at the start. This is quite an accomplishment for the writer, and it might be very beneficial for readers who enjoy the style, since Ruby is probably not best learned by analogy to the other popular languages.
The book is aimed at newbies, but experts might also find it amusing or perhaps even insightful.