I now nearly agree with Fagonella.
Given that technology changes over time, I definitely want to see subdomains instead of subfolders. But I don't see where anything is lost! In fact, that provides an easy way of changing languages...
simutrans.com - should try to detect language, and redirect based on the detection. Regardless of detection, a menu at the top with available languages should exist for manual redirection by the user. The redirection should be to XX.simutrans.com, where XX = language code.
XX.simutrans.com - should be the language equiv of simutrans.com
get.simutrans.com - should, as simutrans.com, detect the language and redirect to (GET).simutrans.com, where (GET) represents the translation of that word into the relevant language. Again, get.simutrans.com should have a language selection bar.
In both cases, the sites should attempt to set a cookie with the language preference, so in cases of incorrect or undesired language detection, if cookies are allowed, it will remember the choice.
In fact, we could attach the cookie to simutrans.com and privately distribute information about how to access variables to subdomain maintainers, so that anyone who would like to detect languages may also use it.
So in other words - I support the idea of simutrans.com and get.simutrans.com appearing in the user's detected language - but I strongly suggest subdomains instead of subdirectories, for ease of maintenance, among other reasons.