Which I think we can all agree is more work than what we currently need to.

It’s not just one addition, it’s 2 operations following knowing what time midnight is to understand what the solar time it is: what time is it now, minus what time is their midnight, and then you have to add that back to what your midnight is to get a sense of the time. Or you just start thinking in solar time WHICH IS WHAT WE ALREADY DO.

That’s 2 calculations. Currently we do 0.

Innately knowing what time means in films, talking to people over the phone, going to a new country. It would be a huge pain in the arse.

"They met up at 13:00“ great. So where are they in this film? Forcing exposition where currently you might let it be vague.

People who advocate for one timezone simply haven’t thought it through.

Could you elaborate a little, I’m not quite sure how it’s related to timezones

Because it makes getting an intuitive sense of what solar time it is somewhere harder.

Can I call my grandma in a different country? Hmm what time is average midnight there. Okay 8 (so far, same thing as looking up a timezone), and it’s 18:00 now, so 10 hours after midnight, which is like my 23:00. Needlessly complicated with extra steps for the average person.

Sure, you can say, I’ll call you X and that will mean the same thing everywhere, but does not have any information about solar time. And these days, it’s automatically converted if you use a calendar (which you should). This is the point of programming, to make the USERS life easier, not the dev. The end is more important than the means, I think we can agree.

Or: what time is it where my grandma is? Okay, cool, I have a sense of what that is immediately after knowing the answer.

There are reasons we do things this way. Working roughly to solar times has more benefits than being able to say a time and it mean the same moment everywhere.

I say we leave things the way they are, works okay.

Thank you! Drives me up the wall that when people suggest this and they haven’t thought it through, and that it might make other things worse.

I’d say for everyday usability, what we have is way better. Sure, you deal with timezones, but at least once you know what time it is there you have a good sense of what part of the day they are in.

Currently you look up the timezone, maybe do some maths (but let’s be real, you just search and get given the time) and then you immediately have a good sense of what the time is there, oh cool it’s 7AM.

If we all had the same timezone: you look it up, and then you HAVE to do maths. Why? Oh their midnight is 8, and it’s 15 now, so 7 hours after midnight.

Your mind immediately has gone to oh it’s 7AM, but NO, in this new reality, it’s 15:00 everywhere and where you live midnight is 14:00, so that means where you live it would be like your 21:00.

No matter what time you pick to anchor what time of day that place is, the problem persists. And now you just have replaced the problem of looking up timezones, with looking up when the sun is at some point, and then needing to convert that to get a sense of what time it is there according to the sun.

This would be shit, when you get to a new country when travelling you have to relearn what the numbers “feel” like.

Let’s just keep what we have, this is a solved problem.

As a non-software engineer, feels weird that they’re making this distinction.

I don’t have much to do with engines either.

I take engineer to mean: designs stuff that does some task, involving SOME kind of calculation.

Visual designer: not an engineer

Piping designer: not an engineer (although this one felt weird, that’s what the piping designer corrected me to say, so)

Chemical engineer: ya

Mechanical engineer: yeah

Software engineer: totally different flavour, but still yeah

Language is what we want it to be.

Web designers presumably still need to script things, I reckon that counts 👍

You will snooze for 9 minutes and you will like it.