I upvoted you, but mostly because I hate downvotes for unpopular stances.
But please answer this question: how does using Github make you "less free"? All parts of Github (even parts of the web interface, like the wiki) can be used stand-alone. All your data can be easily dumped, most of them in a ready-to-reuse form (the git repositories, the wiki and github pages). So, from lock-in perspective, gitorious and github are quite alike. What exactly is it that makes you, as an individual, less free then using gitorious? Sure, the software is less free, but your data: not so much.
The point that the article makes is that OddMuse makes a horrible project hosting system. It's easy enough to store a link to github, or bitbucket, or gitorious (and in all reality, they all speak git, so it's just another remote) as the official project location in whatever new wiki-system emerges.
So in order to "support github and bitbucket" you have to keep copies of your project at both sites? That makes less sense than the original post. The OP uses and when including bitbucket the only way your explanation of "support github" makes sense is with "or bitbucket."
Note, to those that wonder: It moved to git.php.net as github only contains a mirror. And other parts of the PHP project are still in transition. There's also a mercurial mirror. The PHP source module is named php-src.
I've been building this in my spare time over the past 3 weeks.
I had the idea after many experiences of having difficulty trying to find good startup names with various co-founders. I always thought a central place for us to log suggestions would help tremendously.
I finally decided to build it after attending my first Startup Weekend and experiencing the same problem again.
Sounds like he wants a distro agnostic Ports system, one that hides the dirty work of watching compile time crap fly across the screen and just gives the user a suitable package for their distro.
Either that or he's essentially suggesting we move to static compiled packages, which while tremendously inefficient from a space and security standpoint would alleviate at least some of the headaches of trying to do cross distro binary offerings.
I first rooted mine back in January. It's a very easy device to root and you have a lot of options on how to do it now. You can run off an SD card of you still want to use it as a nook sometimes (like getting your free hour at B&N.)
You can run Froyo, Cyanogen, or a Honeycomb version. And it's very hard if not impossible to brick.
If you are serious about wanting to root yours, I'd suggest putting Cyanogen on your EMMC, with it overclocked to 1.1. Very easy to do now that you can download ClockworkMod on an SD card and install Cyanogen, or anything else for that matter using it.
I think the answer for this is different for fiction and non-fiction. If I don't finish a non-fiction book, I still sometimes consider it "read", if I have gotten the gest of it. This is especially true if the author goes into more detail towards the end of the book after making their point. Non-completed fiction books I usually don't recommend to friends.
It depends on the book. Take "On the Origin of Species". The core idea can be summarized in a few sentences. So why was it written? The reason you make something like that a full book is to recount experiences, anecdotes, speculation, experiments, etc to further support your core ideas. Unlike math, many fields are based on ideas that cannot stand on their own, and once upon a time there were no journals to publish in.
Many of them are an expansion on a good long-form magazine article, and the material doesn't really merit book length. But the author certainly is not going to say that. So you end up with an uncut version of the article, plus some chapters on related stuff to pad out the page count.
I find the length field redundant. Two character emotions could be null padded, making three the standard length. This would save a byte for angry and evil. If evil and angry were removed (merged with sneaky and frustrated), emotions could be two bytes. Better yet, a lookup table could be used with a single byte. One other idea, which applies to all cases where 7bit ASCII is packed into 8bit bytes, is to have the eigth bit aroused on the last character