I was going to ask what major cities have changed names, but we are on the brink of WWIII.
Comment on Modern Windows in a nutshell
LodeMike@lemmy.today 3 days agoNew cities in world clock probably
Duamerthrax@lemmy.world 3 days ago
untorquer@lemmy.world 3 days ago
What happened? I can’t find New Amsterdam.
LodeMike@lemmy.today 3 days ago
There’s thousands and thousands of them around the world. And other countries are developing faster than the U.S. too.
Duamerthrax@lemmy.world 3 days ago
Developing country or not, major cities don’t just change names without major conflicts anymore.
LodeMike@lemmy.today 3 days ago
New major cities, or smaller ones that weren’t previously listed.
Like in the U.S, major cities are usually actually a dozen or more cities making up a metro area. I distinctly remember in the 2010s a lot of world clocks would only list the name of the metro area and maybe one or two others for a given metro area.
SpaceCadet@sopuli.xyz 3 days ago
So why does that need a whole new clock app? That would just be an update to
tzdata
on a Linux system.LifeInMultipleChoice@lemmy.world 3 days ago
I remember seeing this update and wondering the same. It occurs the first time the clock app is launched, and the “update” is really just pulling the time zone data and setting the clock to what is accurate, seperate from the bios time it was going off of prior to that. It’s really just looks worse than it is.
untorquer@lemmy.world 3 days ago
Yeah but that shouldn’t be so data or read/write intensive that you need an entire splash. Should take less than a second on any hardware capable of running w11.
Is it just doing some weird backend patching to make it compatible with the rest of windows somehow?
LodeMike@lemmy.today 3 days ago
You’re right, it should just cURL a JSON but this is Microsoft
ricecake@sh.itjust.works 3 days ago
It makes sense in a weird way, but it doesn’t feel right for a clock. You need to account for the case where it does take longer than it should to update, because sometimes it will for any number of really weird reasons. So you can’t just design for the best case scenario.
Now that you have a splash screen you need to ask yourself if it’s better to show the splash screen while doing the update, or to just let the app be unresponsive for the common case of a moment and then show the splash if it goes over that.
The answer is to show the splash in the common case too.
Now people are seeing a “weird screen” for a moment before they can process what they’re seeing. So you need to make the screen have a minimum display time to keep people from being confused.
It’s weird, but people can sometimes be more confused by thinking something happened too fast.
LodeMike@lemmy.today 3 days ago
Windows