links for 2008-03-11
Sterling Camden
-
“One person who is not an idiot hit this page and read it.” I’d like to think I’m a second, and you’ll be a third. Apropos of these thoughts.
-
Onion rings
-
Chad Perrin: SOB » No, stupid, that’s not the problem.
The customer is always wrong
-
Thanks, Avinash.
-
Addicted to Comics ~ Chris Pirillo
Some good ones here
-
Don’t trust that check for advertising on your site. Thanks, Eric.
-
1888 photo depicts Helen Keller, teacher – Yahoo! News
Earliest known photo of Keller with her teacher, Anne Sullivan. Thanks, Jason.
-
Seth’s Blog: That noise inside my head
“…It’s a noise that keeps them from being rational, that forces them to avoid the simple truths sometimes, that makes them unable to take a shortcut when a long (more emotional one) is available.”
-
…or guess the letters on Wheel of Fortune
-
Universe Today » A One-Way, One-Person Mission to Mars
As the first member of a permanent colony? Thanks, John.
-
A very simple and readable overview
Posted in Share the Love |
9 Comments » RSS 2.0 | Sphere it!





French fries.
Specifically, one of:
1. “home fries”
2. Del Taco fries
3. “chips” with vinegar in the British style
Mmm… British chips with malt vinegar… and greasy, batter-covered haddock in newsprint.
“The customer is always wrong” might have been a better title for my Pidgin development team hit-piece. It just seems like the core developers of a popular open source project have so lost track of what they were doing that they started taking cues from Microsoft. It’s . . . disgusting, even infuriating at times.
The Ruby/DBI overview is interesting, by the way, at first glance. I’ll be giving it more of a look. Until now (thanks to the generally abysmal state of module documentation in the Ruby world) I’ve been operating on the assumption that the best way to figure out how to work with a database from within Ruby is to use documentation for Perl/DBI, and troubleshoot when that causes problems. This might give me some better insight into how it works.
Now, if only someone provided something like this for the Ruby/Postgres module. . . .
“…the generally abysmal state of module documentation in the Ruby world…”
Hey, what’s your problem? Just read the code!
I agree with you — I’ve mostly used trial and error myself.
Aside from some minor issues with performance of the implementation, poor documentation is my only real problem with Ruby. Within its niche, of course, Ruby’s performance is generally quite acceptable — but it is limited to that niche in large part by the fact of its performance limitations. Library documentation is a somewhat more significant problem, though.
dammit, I meant to thread this off your last response to me
No problem.
Yes, the human factors in computing are always the more difficult problems to solve, one of which is our inability to read code and grok its intent. Better docs would be a big improvement.
I have heard murmurs about Ruby’s performance, but I’ve never encountered anything myself that would make me drop the language for performance reasons.
Me neither — but I won’t be using it for some performance-intensive purposes where C is more commonly used, either.
True, I won’t be writing any compilers or database managers with it. At least, not for production purposes.