i've always given the advice "program in english, comments, variables, function names, everything", and "always use a uk/us keyboard unless you absolutely have to enter localised strings, and even better get someone else to do that"
The smart projects that are going for L10N will collect all the UI strings into a file or set of files, separate from the code, and indexed so that the app can just switch language and then begin using a new set of localized strings. This also makes for easy translation where you don't need to rebuild the app, just expand the data files that it's using. Is this not the only way to build apps today, or are "localized strings" still being hardcoded??
As someone who's spoken English since 5, I'm perplexed by this question. I'm genuinely unfamiliar with any perceived downsides and I would love to hear more of your thoughts
This is neat! People who like this might be interested in the awesome Hedy language[0]. It's purpose is education, but it's a single programming language with lots of localisations. Always suprised this idea isn't pursued more elsewhere.
This is a nice idea but while the home page was correctly localized in French as my browser is, I couldn't find a way to see "teaching" or "learning" parts of the website in French. At least on mobile, there's no way to tell the site to change language, and it doesn't properly do that on its own based on the browser's preferences. This defeats the whole idea…
18 comments
[ 4.1 ms ] story [ 43.5 ms ] threadSeeing code in my native language makes me laugh, I can't take it seriously.
https://dev.to/finanalyst/creating-a-new-programming-languag...
i'llll get my coat
[0] https://www.hedy.org/