I agree this is a bit annoying and I'd really like to see it changed,
here are a few caveats and ideas:
* The "easy" solution would be to detect the timezone on each startup,
possibly asking the user if the change makes sense
* I believe changing the timezone right now requires a restart, since we
can't easily propagate the timezone to every date instance that might be
saved in different parts of the program.
* If the timezone detection is wrong, the user would be annoyed.
Allowing to ignore certain changes would make things overly complex though.
* We have no easy way to detect if the system timezone has changed
without a restart of Lightning (i.e standby mode). I guess some trickery
could be applied that periodically checks the javascript timezone and
then re-runs detection if that timezone has changed. Not sure how
reliable this would be, and its another periodic timer that might slow
down the application or be annoying if something goes wrong.
That said, maybe someone wants to start working on the problem. In the
meanwhile, I guess one could create an extension that detects timezone
on startup, compares, prompts the user and then changes the zone and
restarts Lightning.
Philipp