I'm not sure software is "english-centric" so much as english being the linga franca of computing, much like diplomacy used to be mostly (if not solely) in french. You need a common language to share, and english was as good as any (better, in fact, since most early research [Church, Turing, Von Neumann, McCarthy] in CS was in english as were pretty much all the early implementations (Colossus, ENIAC, FORTRAN, ALGOL, BASIC, …)
What exactly would be the difference there?
But it does go beyond that. "English-centric software" could be interpreted as "software designed primarily by and for English speakers". And we wouldn't want to advocate that, because that has historically been a problem. Before Unicode, software supported English character sets much better than foreign-language character sets (and Western Europe better than Eastern Europe, and Europe better than Asia...). Even now, a lot of software doesn't support right-to-left languages. This kind of English-centrism is not good. We don't want to perpetuate it.
What the OP is advocating is "English as a lingua franca of software engineering", which is in fact a different thing.
Exactly, that's how I interpreted it (and thought others might interpret it as), and I completely disagree with it (though many softs are indeed english-centric I don't believe software as a field is).
The Japanese are no less insular than Americans when it comes to actual belief in the independent existence of anything off their shores - I find it fascinating to see that reflected in the Ruby project.
Personally, I found that aspect of the article borderline offensive. Oh, people shouldn't speak their native language because... speak English dammit! Oh, and don't release software on Dec 25th. (News flash: the majority of the world population does not celebrate Christmas.)
Some countries do not have this problem, the Anglo-Saxon world can communicate with a common language, they are inflated by the Indian community that generally uses English in their communication as well.
India, with its many official languages, is a living example of how this can be a problem in Science and Technical communities, restricting our problem to programming you'll hardly see an Indian developer starting a project and documenting it in Marathi, Hindi, Urdu, Tamil or Malayalam (or others with more than 10 million speakers).
This can be a problem, so you have to decide very early how you'll approach this problem, Linus Torvalds for example chose English in the beginning instead of his native Swedish. The Lua developers chose a similar route, since they native language is Portuguese, I do not know much about Python, but I expect that Guido also chose English to communicate with developers instead of Dutch. Ruby apparently took another way, some people sees this as a problem, others don't, personally I would not like to work in a project in which I cannot ask some guys directly because we do not know a common language to communicate.
For me English is a easy choice since the majority of people learn some English in school or college, or even playing games.
Nothing offensive about that, as long as it's expressed in a polite manner. To me it sounds like a constructive proposal from someone who has witnessed the problems first-hand, he's not just "ranting from the sidelines".
This is not about imperialism. It's about improving the communications in a project that has long turned international. English is the lowest common denominator. Refusing to acknowledge that simple fact does not help anything.
Also, saying "you may have have time off work anyway" suggests a restricted view of the world.
Think about if we were discussing Apple. Would you really suggest it would be worth making the top performers (including Steve Jobs) do their day to day work in Japanese if it meant more people could participate in the discussions? Or do you want to do everything you can to have the people who really know what they're doing working at their optimum?