So, I see this as rationalization.

The fact is, you took a leadership position, and later turned your coat for reasons that perhaps made sense to you. But they don't really make sense to anyone else. So, yes, everyone who supported you then is going to feel burned.

You also made yourself a paid voice that was often hostile to Free Software, all the way back to the SCO issue. Anyone could have told you that was bound to be a losing side and you would be forever tarred with their brush.

So nobody is going to believe you had any reason but cash, whatever rationalization you cook up after the fact. So, the bottom line is that you joined a list of people who we're never going to be able to trust or put the slightest amount of credibility in.

And ultimately it was for nothing. I've consistently tried to take the high road and it's led to a pretty good income, I would hazard a guess better than yours, not just being able to feel good about myself.

Meh, it's easy to find people with skill. With values, OTOH...

You have a point.

At the ice truck? ARE YOU INSANE?

That path leads to MADNESS!

A lot of people that show up are not prepared and mooch off of everyone in the name of "community"

We would hide our resources and tell others "nope dont have any" on a lot of occasions and those we could tell were in real need and not just lazy potheads we would share.

When poor people buy phones, they choose the free model. and all the windows phones are the free model as nobody in their right mind would intentionally pay the $399 premium phone price for one.

IT will be, it will probably be as horrific as the LG, Motorola and Samsung crap.

If the Watch can not do 2-3 days on a charge , it is a complete and utter fail.
If the watch does not have an open API so apps can easily be written for it, it is a complete and utter fail.
And honestly, from what we have seen from Microsoft for mobile devices over the past 3 years, it will be a complete and utter fail.

No, constructing something impossible, like a perpetual motion machine, is impossible. Science quite often says "definitely" or "definitely not".

Constructing something highly unlikely but not provably impossible, like cold fusion, is highly unlikely, especially if you're doing stuff by accident instead of actually understanding theory, but what science says about cold fusion is "everybody assumed it wasn't possible, but somebody did it, and then we showed that what they did was bogus but interesting, so we're back to assuming it's probably not possible so you'd better do a really good job of explaining what you're doing if you want us to spend our time looking at it again."

This was the negotiations that led up to the Treaty of Guadalupe Hidalgo; Santa Ana really didn't want to be stuck with the not-really-conquered tribes if he was going to lose the good land north of them.

Oh, right, I never owned a 90s car :-) My wife's 1985 car lasted until 2001, my 1987 van lasted until 2012 (with one engine replacement), and I never played with the digital busses on either my 2012 car or my wife's 2001 car (which IIRC only had the dumber version of OBD, not the current CAN bus.) I suppose I should try that some time. Both of those cars have the electronic speedometer with analog readout you refer to.

Many of the remote management applications I used to do with X are being replaced by HTTP interfaces, optionally with AJAX, or sometimes REST APIs, but there are still a number that aren't.

• - Remote logins to run Unix shell - xterm really rocks for this (these days usually with X over SSH), as long as I'm using a Linux desktop, and it's a bit lame but workable from a Windows desktop (usually using Xming.)
• - Windows Remote Desktop Protocol remote logins to Windows servers - RDP mostly works, though running any sort of video over it is painful, and audio's worse, even over Ethernets. VNC would be similar, if I were talking to a Unix machine.
• - VMware console access to Unix or sometimes Windows VMs - the biggest problem here is that too many different applications are carving away chunks of the screen, so there's only 800x600 or maybe 1024x768 left; and I'm usually accessing the VMware server from a web browser on a Windows machine accessed by RDP through a firewall, so there's no real way to compare video speeds or get audio.

We definitely have to dumb down protocols to run on mobile phones with 1024x768 screens and only 1 GHz CPUs and 1GB RAM, because they can't possibly run anywhere near as fast as they did on 1152x900 screens with 10 MHz CPUs and 4 MB RAM running X10, or 640x480 screens with 25-33 MHz 386 CPUs and (I forget how much, but not enough) RAM and X11 with Motif.

And yes, there were really good reasons for running NeWS instead of X, because some changes in which work you did on which end of the wire could make a huge difference in responsiveness and speed, and using Postscript meant that what you saw was really what you'd get, and it let you deal with problems like mouse tracking latency a lot better.