4 ms·
I'm a native German speaker and this localization thing seems like a really bad idea. I can understand where the github folks are coming from but it really is
by hoggle 14y ago
I'm a native German speaker and this localization thing seems like a really bad idea.
I can understand where the github folks are coming from but it really is a thing not worth putting any effort into.
I sympathize with the humanism but programming and programmer communication should be mostly pragmatic.
The open source community is a global thing and English has won a long time ago as the definitive choice for a global language. It seems like it's easy enough to pick up for a lot of people all over the world.
In my opinion it works especially well for technical writing.
- jlarocco 14y agoActually, as far as I can tell, it has nothing to do with "official" GitHub. It's some guy with the GitHub username "letsmake" using GitHub pages [1]. I really wish GitHub would start doing something about people using that feature to make it look like they're part of (or speaking for) GitHub. It's incredibly misleading some times. [1] http://pages.github.com/ http://pages.github.com/
- shabble 14y agoSites that allow users [to have significant control over] personalised subdomains are also problematic for things like NoScript and other whitelisting tools. Since I have github.com permitted, all the subdomains inherit that permission. I'm not even sure what a good model/UI would be to selectively white/blacklist subdomains.
- gsiener 14y agoMaybe github should use a different TLD for pages? Like Githubpages.com ?
- alter8 14y agoThat is a problem only because Github uses the root domain for its own pages. They could rather use www.github.com. To solve your case on NoScript, whitelist the full address https://github.com/ https://github.com/ and that will keep http subdomains out.
- rsanheim 14y agoThe linked site is not authored by GitHub. Just hosted there :).