Sorry if this reads already 'chatty' ...

> "machines that do not move":

From the beginning I had all my machines running on UTC (if it only was for getting rid of the silly daylight saving time), had the date set to ISO format (which tended to annoy people beyond imagination), and the software installed in English (to participate from a much larger user base).

But that still posed problems later, e.g. when

-- I couldn't use the full functionality of any banking software due to their servers refusing to connect because of the 'unacceptable time difference', -- a major known accounting software completely refused to function (or even to install) because the Windows platform was not installed in German and variables like date were not set to the format according to German locale (viz dd.mm.yyyy).

I also remember my astonishment when I had bought my first mobile phone (some time in the mid-eighties) and realized that the displayed time was still wandering around based on a cheap quartz oscillator (while we were regularly using GPS already (with a small handheld box) as backup for navigation on long range flights).

Even the famous Siemens S35 I acquired later (and still use until this day) has not been equipped for having the time set by the service provider. Which somehow suited me, so we had a GMT reference; people who wanted more comfort they wore a second time piece (showing local time).

On the Samsung Galaxy A40 I've had access to there was the choice between manually setting the timezone (or region) to GMT or have date and time automatically set by the network, which then tossed me back to CEST (GMT +02:00). (Wouldn't know about the options with a recent custom ROM.)

-M

At 2022-06-13 21:31, you wrote:

Environmental variables are inherited by a process from the program
which spawned it.

So, the information supplied in environmental variables must be
supplied before the process launches.

This is fine for the timezone for machines which do not move. It's
inadequate for machines which do move.

That said, security (or, more specifically, the concept of "attack
surface") is a commonly used "catchall rationale" for tossing
unnecessary or malfunctioning mechanisms.

--
Raul

On Mon, Jun 13, 2022 at 3:06 PM Martin Kreuzer <i...@airkreuzer.com> wrote:
---> snip <---
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to