Daleus - who's your ISP? I'm with Telus and scored a lowly 15  :(

Check out the current leadling IP, though - an 86!

151.199.53.145 (86)

-Darwin (June 25, 2008, 12:12 PM)

Darwin,

I *may* be cheating.  This is my IP at work, University of PEI (www.upei.ca).  We were the first assigned domain in the ca group, so we have an entire class D address tree ;) Or do I have that backwards?

regardless, I apparently have alot of Prime number thingies in my address, which ramped up the score.

My favourite so far is still mediaguycouk at -2

d00d, yer so l33t yer nega!

While I hate to say something that would be interpreted as being "biased against", I agree with a lot of others here that the best way to include MAC and *nix users is to *not* segregate them.

Fundamentally, any problem or solution for a computer is a problem or solution for users of all varieties of OS/hardware.  So I'd say, for discussion purposes and all of the stuff that comes *before* the coding, we should not break out into little groups that have a high potential for fracturing the community.  It's worth pointing out that I've seen little to no "camp-ism" or what others have termed fanaticism, here at DC.

Perhaps it would be worth a discussion forums for coders, once they get down to the brass tacks of coding, but even then, I see that as a method of segregation.  Like others, I'm always interested in hearing how others implement ideas on other platforms - quite often it sparks creative approaches I might have not otherwise thought of, or an exercise in Google-fu to find something new and interesting!

If you feel the need to skip less than relevant topics, we could always try a message header procedure where a simple [MAC] or [DEBIAN] or whatever style slug at the beginning of a subject line when posting, could help others winnow what they are not interested in.  But frankly, in my mind that's still a type of segregation that I think we could do without.

 Cheers!

I hate to beat a dead horse even more, but I think Adobe Reader has long since taken the deep plunge, and is just gathering more speed with every iteration.

Twice in the past month I've come across applications designed in earlier versions of Adobe (and I mean earlier by one or two) that simply don't function in the latest versions of the Reader.  In one case, the app rendered a document with blank squares in random sections, and printed nothing but blank paper.  In the second case, the app caused Reader to crash.

The Solution? Foxit pdf reader, one of the so-called lightweight readers.  I've been using Foxit for over a years now (I have no affiliation) and it hasn't peeped croaked or farted even once.