Interesting point! I did not know that was the origin of their zone oddness. Thanks for that information.

Lots of other places drift west. Like lots of islands that are in the wrong zone for no real good reason. Probably silly reasons like past (or current) country ownership.

Stupid it may be, but there are a lot of places in the world that already do that and are effectively already going permanent DST. In fact, some of these places then also do DST again, making double DST. Don't believe me? Well, let's look at a time zone map:

Time zone map
Places that do DST

Consider the US state of Alaska. It is nominally in time zones -10 and -11 (check the water north and south of the state). But for some reason, the whole state is in -9. And for some reason, despite their high latitude, they also do DST. I guess they have so much, or so little, sun that it doesn't really matter if their clocks align to it, but then why change twice a year?

But a sparsely populated place not very interesting? Then consider China. Despite being 4 time zones wide, the whole country is in a single time zone (+8). The western border of China is in effectively triple permanent DST. Must be annoying to have solar noon at 3 in the afternoon. At least they don't do DST, through, and a lot of China's population is on its eastern side, which is in the right time zone for its longitude.

But maybe an authoritarian dictatorship isn't a great example. Then turn your eyes to France and Spain. They are effectively south of the UK and effectively in the GMT (+0) time zone entirely. But for some reason, they choose to be in the +1 timezone, giving them permanent DST. Then they also do DST in the summer, making it effectively double DST.

Basically, a lot of time zones "drift" to the west. There are probably a lot of reasons for this, some reasonable, some perhaps less so (the cynical part of me thinks it is older leaders trying to get younger people to wake up earlier and stop sleeping in, though it is actually hard to assign that much forethought to country leaders).

Interestingly, if you look at the DST map linked above, it is clearly just a European and US concept. Not to get too political, but I expected the non-thinking, white-things-are-bad, extreme TDS sufferers to loudly call for an end to DST now that Trump supported it so strongly, but so far that doesn't seem to have happened.

I'm still impressed that the Teams web client can't edit a message with an emoji in it without messing up the keyboard controls and often corrupting the message and losing data. It's had this bug for years. It's literally a messaging app where you can't reliably send messages.

"For all they keep doing, the one thing they can't seem to do is make a checkbox to stop being harassed about updates."

You literally post this on every article about Firefox. Aren't you tired yet? I have replied numerous times that they are *NEVER* going to do that. And then I pointed you to using policies, which will disable updates.

So... what you're saying is that you are tired of seeing the same pointless message again and again over something that will never be changed? This has to be the most unintentionally ironic post I've ever seen!

Not disputing your points, but JPEG2000 is used pretty extensively in the remote sensing world (think overhead satellite imagery from companies like Maxar [was Worldview]). These images are often huge (think GB+), benefit well from the compression and especially the inherent res levels J2K provides. It is a common compression format in NITF formatted imagery files. A niche area to be sure, but it is used.

The problem with this argument, from the shop's point of view, is that the UK is in the middle of a shoplifting epidemic. The policing resources simply aren't there to deal with small scale (or even flagrant and much larger scale) shoplifting. It now seems to be rare for police officers to attend reports of shoplifting at all. And so effectively shoplifting becomes legalised, which is obviously hurting the big chain stores financially and potentially devastating for smaller shops.

Shops are trying to find some way to respond to this to protect themselves. They typically tell staff, even security staff, not to get physical with shoplifters as they walk out, not least because the risk of something worse happening and the business becoming liable for it is significant. But then the shoplifters know this and some of them will just walk in and openly empty a shelf into a bag and walk out again without paying because they know no-one will try to stop them.

Shops also know that our court system is completely overwhelmed at the moment and there is little chance of bringing any successful civil action to recover damages from shoplifters who aren't even being arrested by the police and put through the criminal justice system.

So what do they have left? Basically, they're trying to spot the "usual suspects" and refuse them entry in the first place, which is a less risky proposition in terms of potential for physical violence and quite effective because a lot of shoplifting is done by the same people, or they're trying to make it more physically difficult to steal goods, for example by using locking systems or keeping high value items behind counters where customers can't just pick them up. But these systems aren't perfect, far from it, and what we're discussing here today is one of the significant problems.

Obviously this kind of technology can have very bad consequences, as we see here. I don't think it should be used if it's not highly reliable, given the potential harm done in cases where it gets something wrong. But I do have some sympathy with the shops who are looking for something -- anything -- to reduce the threat they're facing because the rule of law has failed in retail settings.

On the contrary, I think most of your comment is as relevant as ever. A carefully designed UI is still better for almost any specific task than what "agents" will produce. It will probably be more efficient to describe what you want precisely enough to get it right. It will not be undermined by problems like non-repeatability, non-determinism and hallucinations that are inherent in LLM-backed agents.

Agents can be quite effective at getting something that seems about right, as long as you don't care too much about the details. And of course they get there much quicker than doing it manually as a human. This is useful for some tasks, and why they have become popular.

Unfortunately, it turns out that for many of the things we really care about, "about right" doesn't cut it. Right now, today, the software industry is already being overwhelmed by AI slop. It's hard to believe, but it's still only been a few months since agentic development processes arrived on the scene. And yet after just those few months of management trying to replace real developers with agents, we can see the slow-motion train wreck happening right before our eyes. And in return, where are the new applications that radically improve on what we had before thanks to all this added "productivity"? If this tech is going to change the world as the AI tech bros and the sycophantic CxOs kneeling at their feet would have us believe, where's my flying car?

Imagine a Beowulf cluster of AI-generated cybersecurity nightmares...

It is. The fact that our dominant desktop operating systems are still using security models from last century is probably the #2 disaster of modern tech security, coming in just behind so much software with potential security implications still being written in languages like C and C++ at #1. And the understandable yet still deeply regrettable reason for both disasters is the same: momentum.

I normally connect to all online conference calls via their web UIs. At least then it takes both a screw-up in the communications system and a screw-up in a browser security sandbox that is independently developed to allow something like an RCE or data leakage vulnerability to be exploited.

People have called me crazy for not wanting to install native apps from the likes of Microsoft, Google and Zoom in the modern era of remote working, but every now and then, there's another story like this one that reminds me why I am extremely careful about what native software I install on anything these days.

What, specifically, do you mean by "personal Windows installations"?

Are you suggesting that any business of any size should only ever use Enterprise editions of Windows?

No, I read the details explicitly quoted at the start of the discussion and responded to them.

Are you saying that this episode has not in fact resulted in (a) unplanned software being installed on end devices that will (b) automatically read data that is stored on those devices without the proper approvals? Either of those things alone can easily become a compliance problem if you operate in a regulated environment, whether or not things ultimately go any further on this occasion.

It was obnoxious enough when Microsoft started pushing this kind of unwanted "feature" on home users, then small businesses and professionals on Pro editions. There are real legal and regulatory concerns over this kind of change that businesses have to take seriously. If they've screwed up so badly that even their large corporate customers have been hit by the same thing and there isn't even a good way to undo the damage at the moment, this could lead to meaningful lawsuits from their customers and/or interventions by regulators.

I suspect GP's point is that every malware blocker in every browser is likely to treat this kind of script as hostile, except for Chrome because Google are currently nerfing the ability for blockers to intercept hostile scripts in one of the most blatantly user-hostile changes they've ever made.

If Apple play along with Safari then every other browser and its malware blocking plugins are about to be toast in a huge retrograde step for Internet privacy. But not even Cloudflare is going to get away with blocking every iOS device if Apple continues to allow blockers to intercept this kind of script.

Did anyone mention recently that simultaneously controlling both the most popular web browser and several of the most popular ad-supported web properties might be a little anticompetitive, and that it's about time that Google was broken up? It's probably time for that drum to start beating a bit louder again.

DST works by tricking people to wake up and get to their daily activities an hour earlier than they normally would. And it is sold as "giving" people an hour extra in the evening. They could do that without changing their clocks by just waking up at 5 instead of 6 and working 7-4 instead of 8-5, but most people don't want to wake up earlier. So we use DST to trick them into doing it.

Doing DST as a whole society also helps for people who don't have flexible hours for their daytime activities.

But i realized a while ago that the twice a year time change is the PRIMARY reason why DST even works. Because without the constant change, people would just adapt to the new timezone. Daily activities (like school and work) would shift to starting an hour later. Lunch would start being eaten from 1-2 instead of 12-1, as the new time would be when the sun is at its highest. Dinner would be 6-7 instead of 5-6, because that is closer to when the sun is setting. It would take several years, but eventually, society would shift its schedule to closer match the sun. And the way that DST "tricks" people into getting up an hour earlier would stop.

btw, your preference (and mine) for year standard time is the way most of the world works. Gray countries in that map do not do DST. It's really only US, Canada, Europe and a few other places. And I'll never understand DST in Alaska, which is already entirely in the wrong time zone.