Apple has been doing this with other APIs for a while. If your app links to a way of signing up for an account that could be used to pay for something you'll be rejected. If you mention the existence of such an account you'll probably be rejected.
Personally I don't like being treated like this - as a user or a developer. So I take my time and money elsewhere.
The problem here is that Americans haven't ever experienced a competitive mobile telephony market where all carriers use the same network technology and switching networks is trivial. That's probably why our coverage is terrible and we pay 3-5 times more than people in other countries.
(North) American telco misregulation is a disaster.
I worked for Andy for a few years at Danger. He's a great guy. He's got a great mix of technical skills, business savvy and being a generally nice bloke.
He's also ridiculously generous.
Also, he builds cool robots for fun (or at least used to).
But node.js doesn't have any concurrency. It's single-process, single-threaded and event driven, so by definition it's not concurrent. It's just not blocking.
Also, was someone really trying to run performance benchmarks on a shared machine running on a VM and expecting to get anything meaningful out? Really? Like really? I'm embarrassed for you.
This is why Gtk+ implements icons as a set of vector / raster images to be displayed at various sizes. It makes resolution independence really easy. This has been important to Gtk and GNOME for a long time since it's a big issue for accessibility which is not only important socially and morally, but actually a key legal issue for adoption in large companies and governments.
Comparing the size of Ubuntu 'main' isn't interesting.
A more thoughtful assessment would have examined what packages were installed & used rather than which ones existed. That data is really easy to find: http://popcon.ubuntu.com/
Perhaps we could have modelled these in a REST-like manner, but it seemed simpler to make the functionality available through an RPC protocol - simpler for us to implement and simpler for developers to integrate into their software.
Hiring managers don't list a salary. If they do they're looking to hire really junior engineers who probably can't write a linked list reversal program anyway. In my 13 years working at startups I've never applied for a job that listed a salary range.
Ultimately, within reason, good programmers are worth whatever you have to pay them and bad programmers aren't worth what you pay them. There are way more bad programmers than good programmers and money isn't the way to attract the good ones. You have to attract them with interesting problems and a great work environment. If they're there for the money then they're probably no good anyway.