Live data from Hacker News

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

poignant.guide

131–140 of 213 posts

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

#131
post #11

Earlier quoted context omitted.

Where did he go? I know he likes anonymity, but it's really sad that he just left.

Rather than think of leaving as a sad thing, think of it as an affirmation of the other things in his life.

It's not so much that I'm sad that _why is gone, as that I'm sad that there aren't more people like him. We went from having one _why-like force in programming to having zero. And that is the shame.

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

#132
post #128
post #125

I'm pretty sure it was _why who set up the first darknet I was ever on. You had to set up your /etc/hosts and do some other tricks, to browse to hidden pages. Unless I'm confusing with another similar thing around the same time, there was some JS involved and you could find hidden features layered on regular websites.

yep, "mousehole". it was used to effectively add a hidden comment section to random pages.

I remember that too, but I thought it was called hoodwinked or something close to that.

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

#133

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

Broad generalisations incoming:

I don't see a lot of new and exciting things being done in Ruby, and I don't think it's a popular choice for highly technical companies any more; even if you find one company doing cool stuff with it, do you want to be looking for a job in 5 years' time having spent 5 years in Ruby?

Rails is still the fastest way to bang out a CRUD webapp, and there's a lot of companies who use those webapps for critical parts of their business - but those also tend to be companies that are not primarily technical, for whom this is more of a cost center than a profit center (and who may well have outsourced the original creation of the app and then barely maintained it). So while you could probably make a career as "the tech guy" at that kind of company, it's likely to be an unrewarding position with limited opportunity for growth. (On the other hand, it might be a stable position, particularly with a big company in a lucrative industry like finance). Consulting for companies like that has more potential, but only if you're good at negotiation, as you'll likely face a lot of clients who want to nickel-and-dime you.

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

#134
post #53

Earlier quoted context omitted.

I saw it as more of an art piece than a practical learning experience; the latter being more exemplified by books such as K&R and the like.

"Well Grounded Rubyist" and "Why's (Poignant) Guide" make an excellent combination for learning Ruby.

"Eloquent Ruby" is one of the best technical books I've ever read. Such a delight.

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

#135

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.

TBF, input is generally linear; prior to experiencing both, one will be better suited to go first. Usually because it makes the broader concept-space - and thus the second - more generally accessible.

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

#138
post #56

Earlier quoted context omitted.

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

I left python for ruby A dozen years ago. I always missed the simplicity of Python. Ruby community was just awesome. Pushing at the bleeding edge of getting stuff done fast, if a bit magical. Been debating about going back. Cleaning up 8 year old magical ruby apps is getting old.

Definitely worth a shot.

I've really enjoyed working with FastAPI in Python for web apps.

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

#139
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.

Making fun of Garfield cartoons might as well be a Monty Python reference.

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

#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

Post reply on HN