HN user
This is a bit iOS centric. Not to bash on Apple, but on a stock Android ICS device there is a clear distinction between "all the apps" and the launcher, which is more like a desktop. Metro seems to take a similar approach.
At least in Germany (possibly in the EU in general), that's no longer true. There has always been a market for OEM license resales, but recently there was a ruling that gave it a legal foundation. Microsoft wouldn't tell you it's okay, but they are no longer allowed to prevent it.
Let's consider the "obvious" choices by examing the TIOBE top 10:
1. C - Not really the target audience of a tool like this.
2. Java - See above, plus plenty of competition.
3. C++ - See C.
4. Objective-C - See C, also arguably a bit of a niche (iOS).
5. C# - See Java, VirtualStudio dominates.
6. PHP - Yeah, right.
7. (Visual) Basic - Who are you kidding?
8. Python - Oh, right.
9. Perl - Only ranks high because of sys admins.
10. JavaScript - Already covered.
11. Ruby - Like Python, see below.
Basically your question seems to boil down to either of these:
1. Why was Python picked over Java/C#?
2. Why was Python picked over Ruby?
As for #1: the answer should seem obvious if you consider the category the three languages (JS, Clojure and Python) share. Plus, the market is very different and the competition is very strong and established.
As for Ruby: It's probably personal preference. There really isn't any objective reason to pick Python over Ruby or vice versa. The two are more similar than either of them would like to admit and they are perfectly interchangeable in most situations.
I can sympathize with your argument, but your comparison is a strawman, really. We don't have a defecation problem. We do have a harrassment problem.
There'd be no point in creating a code of conduct that explicitly bans defecating in the hallways because it's simply not an everyday problem. How women are treated in tech, however, is.
I'm saying this as a guy who is a strong believer in egalitarianism but highly sceptical of feminism, mind you.
If we had a defecation problem, yes, we should have a binding code of conduct for that. And as soon as the problem is gone, we should re-evaluate it, too.