Goodbye Aston Martin. Goodbye Jaguar. Goodbye Land over. Goodbye BMW. Goodbye Rolls Royce. Goodbye Bently.
BYD is going to come for your car industry, where even the Japanese can't compete. To cut the costs, all car parts will be from China. There is no escape in the race to destruction of local manufacturing.
I quite like my BMW. There is approximately zero chance I will be replacing it with anything Chinese.
their relative robustness vs ICE will be under-appreciated by sellers for a long time.
Only so much robustness is required before the rest of the car simply falls apart around the drivetrain. Ask people who drive old cars now and it is not so much keeping the engine running or the brakes stopping but more of keeping the climate controls working and the windows rolling up and down. Around here we have rust to contend with as well.
All the electronics in moderns cars make this problem worse, and BEVs are no better in that regard.
This moment does not include future new demand.
It also does not include future new production.
https://www.reuters.com/busine...
It's a question of priorities. If the exploit requires you to be in the network, install a special usb device on the server, interrupt the boot process, flood a specific port with malformed packets, do it on February 29th at 11:59.59 pm, and call your mother first, it's gonna bubble down on the priority list.
That is why it requires so many tokens.
And then you do an once-over over all time zones each year to check which standard they are following and if and when they are switching
You know these things happen randomly and not on a schedule right? We have had 5 new IANA tzdata files so far this year. There is no once a year.
People work after sunset and before sunrise all over the place. Some places are open 24/7. And yet, people manage it just fine.
Indeed you would think the snowflakes would prefer the dark so they don't melt as fast.
I did love the recent headline in The Beaverton (our version of The Onion).
No one in Canada knows what time it is anywhere else in Canada
I'll admit I don't, but it will become more clear when the dust settles. The new PQ government in Quebec may be changing soon from the sound of it, which might cause Ontario to have another look...
Unless the change occurred within a couple of day, there was no excuse.
You've never worked in an enterprise, have you?
The changes to Canadian timezones didn't happen on short notice, they were established months ago. Microsoft had more than enough time to adjust all the timezones, meaning this screw up is intentional. Adding to the increasing list of things Microsoft can't manage, telling time . . . maybe they should visit an elementary school, I'm sure a Jr K teacher could help them.
My province of MB was definitely short notice, becoming official in mid-September. That change is included in IANA 2026e tzdata. Changes for Inuvik were in IANA 2006d, and British Columbia had the longest notice, with changes are in IANA 2026c.
Can't we define the timezone as a UTC offset? I thought WIndows, macOS and Linux all allowed that?
On Linux in this case you can use the Etc/GMT+5 timezone (note the POSIX inversion is not a typo), which is a permanent UTC-5 with no DST changes.
As if interstate/international business doesn't already involve keeping track of which timezone the other party's in?
I'm in Canada and there have been so many provinces changing lately I'm no longer clear on any of their timezones, but I'm sure once it settles it will become second nature again. There are indeed not really many situations where it matters anyway.
Myself, I'm super happy to have not changed the clock back this morning. I prefer the permanent DT, but would have been fine with permanent ST too. I was part of the huge majority who wanted to simply pick either one and stick with it.
There are no data that cannot be plotted on a straight line if the axis are chosen correctly.
