Live data from Hacker News

Why's (Poignant) Guide to Ruby (2004)

poignant.guide

141–150 of 213 posts

Re: Why's (Poignant) Guide to Ruby (2004)

#141

Earlier quoted context omitted.

There are two kinds of people who are trying to learn code: Those who already think like a programmer, and those who don't. K&R is for one of those. _why's guide is for the other.

And those of us who are not dumb enough to be locked into a single narrow mindset will enjoy them both.

...or else!

Re: Why's (Poignant) Guide to Ruby (2004)

#142
post #56
post #32

Aside from the book, this brings back all those fuzzy feelings of learning ruby. Boolean functions end in ?, in-place transformations end in ! each, unless. It's just such a beautiful language.

Yes. In a perfect world Ruby would have left Python in the dust and enterprise software would be written in Clojure.

I'm more and more convinced Rails has caused much of the demise of Ruby. As well as make it big in the first place.

I love Ruby. And with a decade of fulltime Rails development, know and like both Rails and Ruby very well. But 'sharp knives' have caused just too many rails projects to become mudballs over time. This makes teams or companies 'move to language X'. When it really was (their use of) Rails causing the mudballing. Let alone Ruby.

'Performance' is often cited, but I'm certain hardly anyone ever had severe performance issues in practice with Ruby. Maybe with Rails, probably activerecord and quite likely their own implementation thereof. But hardly Ruby the Language

Re: Why's (Poignant) Guide to Ruby (2004)

#143
post #140
post #12

I've always felt this was a singular achievement, one which perfectly captured the spirit of its author, the community he inhabited, and a particular zeitgeist in programming and on the internet. The need for various other authors to attempt to replicate it for other languages by creating rambling, twee books with wacky titles and comic characters of their own, I've frankly found a bit sad and underwhelming. It's a b…

> And yet the joke is replicated endlessly as if each time it's possible for it to be new. Quite the opposite. It's replicated because it's now become a trope. "Repetition is the essential comedic device": https://en.wikipedia.org/wiki/Comedic_device#Repetition

The essence of comedy is confounded expectations, and it’s true repetition can set this up, and in some cases itself be the joke, especially in standup where a comedian will stretch out a bit beyond people’s comfort zone. But it would be difficult to achieve that with Nouny McNounface at this point. Just making a callback isn’t funny. It’s only funny if it takes time to actually dawn on an audience that that’s what’s happening.

Re: Why's (Poignant) Guide to Ruby (2004)

#144
post #3

Does anyone know if this site was recently put together or if it's been around all along? WHOIS says the domain was registered back in '14. I love _why's writings and largely credit him with getting me excited about using Ruby back when I was in college. Really nice to be reminded of his work.

_why actually deleted all of his stuff at one point- I don’t think any of his content is actually hosted by him these days.

Re: Why's (Poignant) Guide to Ruby (2004)

#145

Ruby is an appealing language for sure , but is it worth learning it in 2020, with the intention of getting paid for one’s work? It is an honest question and in no way am i trashing the language. Just curious what others have to say about it

Shopify (along with its millions of shops) is probably the biggest user of Rails (with Ruby) in production. Aside from them, not sure who uses Ruby at that scale.

Re: Why's (Poignant) Guide to Ruby (2004)

#147
For me, this is one of those quintessential software books. Reading it takes me back to 2005, when I was in college — not studying CS but still building for the web as I have been since I was 13 — and feeling so seen to see a book/collection of essays/language introduction written in an original and irreverent style much more akin to Dave Eggers than anything else of the genre.

I never really embraced Ruby — though I always admired it and adopted TextMate like all the other cool kids — but this and _why’s other work stuck with me as sticks with me now.

Re: Why's (Poignant) Guide to Ruby (2004)

#148
post #54

Earlier quoted context omitted.

Which of course, we shall remember comes from our beloved Scheme. :)

.... and Perl and Smalltalk, the latter arguably being the greater influence.

Smalltalk did not have the ?/! delineation that GP is specifically talking about. Not that Ruby used it consistently (it was largely just for enumerators e.g. Array#push rather than Array#push!).

Re: Why's (Poignant) Guide to Ruby (2004)

#149
post #22
post #12

I've always felt this was a singular achievement, one which perfectly captured the spirit of its author, the community he inhabited, and a particular zeitgeist in programming and on the internet. The need for various other authors to attempt to replicate it for other languages by creating rambling, twee books with wacky titles and comic characters of their own, I've frankly found a bit sad and underwhelming. It's a b…

This about sums up most Monty Python and Rick & Morty references as well. A lot of nerd/hacker culture falls into this kind of recognition of unique humor and wit, then squeezing every little drop of joy out of it until it's as empty as a Garfield cartoon.

Garfield has gone beyond joy and is now nightmare fuel: (CW: body horror) https://www.reddit.com/r/imsorryjon/

Re: Why's (Poignant) Guide to Ruby (2004)

#150

For me, this is one of those quintessential software books. Reading it takes me back to 2005, when I was in college — not studying CS but still building for the web as I have been since I was 13 — and feeling so seen to see a book/collection of essays/language introduction written in an original and irreverent style much more akin to Dave Eggers than anything else of the genre. I never really embraced Ruby — though I…

I've tried Ruby (and RoR, which, while I've never used it professionally, has had a huge impact on the whole realm of web application development that I'm into), but I never fully understood it. Made a first RoR app from a book, but when trying to deploy it I ran into a minor issue (probably wrong database configuration), apparently I had to restart the application but the webhoster I used did not give access to restart the thing so I just sighed, gave up, and went back to PHP.
Post reply on HN