As a Linode customer, this post was news to me and cause for concern.

But then I saw that Rackspace had 12:
http://www.spamhaus.org/sbl/listings/rackspace.com
and I was glad to have left for Linode after Rackspace bought Slicehost.

And saw that others were worse, with Dreamhost at 25:
http://www.spamhaus.org/sbl/listings/dreamhost.com

If you're someone who spends all their time creating things, spending your life fighting about those things is a soul-sucking, wretched process that takes you away from doing what you love.

I've had work ripped off, sometimes in high-profile ways. But there's a choice to be made: do you keep creating new things and move on, or do you spend your life in litigation, calling people out, and dealing with discussions like what we see here. Being ripped off is bad, but the latter choice is truly awful, and means you're not making newer things and getting better at it.

Sounds like a really good idea, so that Canonical can put actual numbers behind the number of users they have. Also good for the Linux community, so that Canonical can publish those numbers to show more people using at least one major distribution.

On the other hand, the "at least for now" part of "That's all that canonical-census does" is so pathetic. Why is that necessary? Having found nothing nefarious, why still insinuate that Canonical might in the future do something bad? I'm obsessive about privacy too, but you might argue that Canonical has done enough good for the community that they deserve the benefit of the doubt. What's with the community fighting its own?

I run an open source project that reports similar information when checking for updates. It's enormously helpful for us to understand what versions our users are running, and on what platforms. It also helps to have real numbers (rather than "downloads", which are arbitrarily high) when we're trying to make the case for the project, or funding, or whatever.

...or Apple could remove the approval process, and they wouldn't even put themselves in the position of making blown calls.

The reviewers and their 10,000 app workload has nothing to do with it, especially when Apple is charging $100/yr for the privilege of having your work put through this idiotic process.

You mean like PDF? And TIFF?

Thanks, Captain Anecdote, but you've left out even the anecdotal evidence. What's all this exclusive writing you're doing with Ruby? I've been doing all my grocery list work in Ruby too, and it's *totally* fast enough.

I think Ruby is a fantastic language, but then I see comments like this modded up to 5 that are completely nonsensical. This makes Ruby fandom seem more like Java 1999, which makes me think twice about my positive opinion of it.

Nader, is that you? Dude, the election is *over*...