I can kill you with my mind.

Exactly. I've got the same problem at home ... having already given my local Bell land-line provider the finger, my cell is my only phone.

Many providers are leaning toward 3G micro-cells ... which provide a similar service with less complexity on the phone, but rest on the somewhat shaky stance that the FCC is OK with consumers running what are equivalently low power 3G towers all over the place.

Anybody know if this device has UMA support on it?

Skype is not the win imo ... I'd rather just have my cell communicate directly to my carrier over my household broadband connection and not mess with an extra "skype" address to hand people for when I'm out of cell coverage area ... UMA is preferred since I don't need any special network hardware (other than a wireless access point) to support it.

T-Mobile supports UMA pretty well ... I'm using it with my BB 8900 at the moment.

Exactly correct. Language docs, depending on the situation, rarely to never. My exception is javascript. I can never seem to remember all of its quirks for creating custom objects.

Library docs, all of the time. Which is where dev environments with built-in syntax helpers are invaluable (visual studio, komodo, eclipse, ...).

Its a good thing that "MY" terms of service (written down on a bar napkin years ago, and may be subject to blurring due to beer spills) bar any restriction on my ability to seek restitution or damages from any service provider whose terms of service require arbitration and/or prevent participation in class action lawsuits against them.

I gave all my service providers 1 year to make known any problem they had with my terms of service ... from when i first scribbled them down and made them public by vocalizing them to anybody at the bar who cared to listen.

I should also mention that my terms of service require arbitration and prohibit my service providers from participating in a class action law suit against me. Oh. And they have to bring me the number of that cute barmaid from across the room, too.

Can you translate that into rods/hogshead for me?

I beg to differ. Case in point: Ultrix. I think it is safe to pronounce DEC Ultrix as D E A D. *grin*

Not entirely sure, no. Just like now, back then I was a lowly developer ... not fit to bathe in the glory of Sun reps or gawking VPs.

I'm just glad I was close to the right number ... it was a mixed house of e250, e450, e4500 ... i think there were a few e6500s and one or two e10ks floating the data center also.

... and for some reason, with all that hardware, I seem to remember complaining about disk space on a daily basis.

What you talkin 'bout Willis? Oracle's primary development platform has been Linux for years now. I think the vague "runs better" test is pretty much a wash when you compare optimized code builds running on similarly powered hardware.

I think Sun hardware is really more of a vanity thing in business nowdays ... so "company a" can look down their nose at "company b" and say "we dont use Dell servers, we're a Sun house"...

OMG! THANK you for making me post this! I NOW understand the Oracle-Sun merger! They're both "vanity" business models! Its been bothering me since the merger was announced ... but now I see the synergy plain as daylight. Its all about super large corporate businesses and absurdly high maintenance contracts.

Wow. That is some kind of evil genius. I'm going out to buy some Oracle stock.

I had enough exposure to Solaris in the 90s ... I remember when a Sun install team put in the 1st e4500 16 processor high availability box at my employer ... they had powered it up and had a bunch of our company VPs standing around the cold room oogling it ... the Sun rep was giving an executive overview of its HA features, full hot swap of processor boards, power supplies, yadda yadda yadda. My (then) boss, a lowly manager in the VP crowd, walks up to the e4500 and pops a processor card out ... the whole system seg faults an UGLY death. Ahhh ... good times.

If operating systems are weapons, Solaris is a World War II German railway gun with a cracked breech block.
- Charlie Stross

RFC2549 seems to be a perfect fit here.

Hot Pockets. All you got. Seriously.

Lesson learned? C code written by people who have programmed Fortran for 20+ years runs slower than Fortran code written by people who have programmed Fortran for 20+ years.

It is incredibly easy to write inefficient C code, and only years of exposure will give you the understanding necessary to write truly efficient C code.

Unlike your typical /. post, I present evidence, Duff's Device, of what an efficient C coder can do.

Awwww c'mon. This is just plain silly. Since the late 80s, "Fortran" on most major computing platforms has been nothing more than front end language parser for a multi-pass compiler system ... just like "C" and "Pascal". Whatever language you choose, they all pass their assembly output to the same back-end assembler, and binary machine code generated is pretty generic.

Back when I was in college, I maintained a Fortran77 program that was a custom built TCP/IP client-server system. But wait! F77 didn't know what a socket was! right. The network code was written in C and compiled into object code which was directly linked into the F77 project.

Great. So there are these massive libraries written in Fortran to do wonderful things. Best case scenario is you can link them directly into your language of choice. Worst case, call them from the scripted language of your choice with a wrapper ... Swig anyone?

Bottom line? Program in what you are comfortable with. Would your peers would frown on your efforts if you learned anything but ALGOL? Fine. Use ALGOL. There are valuable lessons to be learned in any language. Strong vs weak typed, functional vs object oriented, structure, best practices ... hell, how to write "fast" code. I've been a programmer for near 20 years and I'm still learning that lesson on a daily basis.

We are living in a world today where lemonade is made from artificial flavors and furniture polish is made from real lemons...
- Alfred E. Newman