Chip's Quips
A tiny spark of wit for a highly flammable world

links for 2008-03-11

March 11th, 2008 2:25:14 am pst by Sterling Camden

Posted in Share the Love | 9 Comments » RSS 2.0 | Sphere it!

RSS feed | Trackback URI

9 Comments »

MyAvatars 0.2
Comment by apotheon Subscribed to comments via email

French fries.

Specifically, one of:

1. “home fries”

2. Del Taco fries

3. “chips” with vinegar in the British style

MyAvatars 0.2
Comment by Sterling Camden

Mmm… British chips with malt vinegar… and greasy, batter-covered haddock in newsprint.

 
 
MyAvatars 0.2
Comment by apotheon Subscribed to comments via email

“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. . . .

MyAvatars 0.2
Comment by Sterling Camden

“…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.

 
 
MyAvatars 0.2
Comment by apotheon Subscribed to comments via email

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.

MyAvatars 0.2
Comment by apotheon Subscribed to comments via email

dammit, I meant to thread this off your last response to me

MyAvatars 0.2
Comment by Sterling Camden

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.

MyAvatars 0.2
Comment by apotheon Subscribed to comments via email

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.

MyAvatars 0.2
Comment by Sterling Camden

True, I won’t be writing any compilers or database managers with it. At least, not for production purposes.

 
 
 
 
 
Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.

Subscribe without commenting

Better Tag Cloud