be extremely reluctant to default encoding. It is almost never a good idea.
If Writeln and so on is used, is there another way?
Writeln's floating point output is rarely used in applications, since it goes to exponential notation too quickly.
And because functions like Str() (used in the DMath unit) ignore the Defaultsettings "en" or "us" conventions are in many cases the easiest and securest way.
Then have DMath fixed. Buggy existing code is no excuse to make everything buggy then.
For a limited local set of scripts, it is of course ok, and I'd be lying if I would say I never would for limited own use scripts.
But as a general rule? Not even close. Don't let a little tech bubble misguide you. There is a real world out there.
It is just lingua franca in the world.
And the Frankish language is Dutch (or alternately Afrikaans or Luxembourgish). But certainly not English :-) (*)
Or think about "CSV" comma separated values, a format that is still widely in use.
Everybody says "CSV", but rarely ever means that in the CSV standardized way. Rather, in such informal talk whatever Excel outputs is what is considered "CSV", and for locales with comma as decimal separators, Excel exports files semicolons as field separator.
This ambiguity btw makes it extremely hard to have e.g. a "csv" file export from a webpage and have it open reliably in Excel (or at least it was 15 years ago, when I last tried).
(*) Dutch Linguist joke, please do not take seriously.