i would bet a years salaray that you are correct. copilot or some automated process. and then the message is automated with an automated appeal-denial flow.
conspiracy theories are fun and all, but 99.99% of the time it is just incompetence, miscommunication, etc.
It is heavily dependent on the history of your area.
I am near Lyon (12km away), I had 20mb then 100Mb coaxial cable very early because the "département" built a public network and eventually leased it to private companies.
I finally switched to fiber 3 years ago when it became available in my street.
The cell network is fairly bad however (even with 2 cell towers less than 1km from my place).
Every group want to label some outgroup as naively benefiting from AI. For programmers, apparently it's the pointy haired bosses. For normies, it's the programmers.
Be careful of this kind of thinking, it's very satisfying but doesn't help you understand the world.
I personally think that the more appropriate quote from 1984 is this one, because the cruelty is the whole point :
“The real power, the power we have to fight for night and day, is not power over things, but over men.” He paused, and for a moment assumed again his air of a schoolmaster questioning a promising pupil: “How does one man assert his power over another, Winston?”
Winston thought. “By making him suffer,” he said.
“Exactly. By making him suffer. Obedience is not enough. Unless he is suffering, how can you be sure that he is obeying your will and not his own? Power is in inflicting pain and humiliation. Power is in tearing human minds to pieces and putting them together again in new shapes of your own choosing. Do you begin to see, then, what kind of world we are creating?[...]”"
Exactly, there is no need for nefarious intentions, when time constraint et mild incompetence suffice.
The OOXML format is likely a not very deeply thought out XML serialization of the in memory structure or of the old binary format, done under time pressure (there was legal pressure on Microsoft at the time).
> The OOXML format is likely a not very deeply thought out XML serialization of the in memory structure or of the old binary format
it somewhat looks like that, but that old binary format changed with every nth yearly major new version and IMHO it looks like not being far away from a slightly serialized dump of their internal app data structures ;)
but
putting aside that they initially managed to incorrectly implement their own standard OOXML and the mess that "accident" caused
they also did support import and even exports (with limited features) of the Open Document format before even fully supporting OOXML, and even use that as standard save option.... (when edition such a document)
like there really was no technical reason why they couldn't just have adopted the Open Document format, maybe at worst with some "custom" (but open and "standardized" (by MS itself) extensions to it)
MS at the time had all insensitive to comply as bad in faith as they could get away with
and what we saw at that time was looking like exactly that
sure hidden behind "accidents" and incompetence
but lets be honest if a company has all interest and insensitive to make something in bad faith and make it go bad absurdly and then exactly that happens then it's very naive to assume that it was actually accidentally most likely it wasn't
that doesn't mean any programmer sat down and intentional thought about how to make it extra complicated, there is no need for that and that would just be a liability, instead you do bad management decision, like (human) resource starve the team responsible (especially keep you best seniors away), give them all messed up deadlines, give them all messed up requirements you know can't work out. Mess up communication channels. Only give them bad tooling for the task. etc. etc. Most funny thing due to how messy software production often is the engines involved might not even notice ;), means no liability on that side.
and they should have gotten the corporate death penalty for it. I think it should still be done. the sheer amount of crap microsoft has purposely bestowed upon the world should lead to life in prison for many of its decision makers
I happen to live in a rural area. Rural France is not the third world. Small towns are very much alive. Healthcare is organized around "pôles de santé". Now about jobs... that's an interesting point and probably the most important. The society as whole should favor decentralizing work. There is no point in concentrating jobs around big cities.
The vast majority of jobs are not decentralized and will not be for the foreseeable future. You cannot be a steelworker or waiter or actor from a home office or location that doesn't have high in-person demand for those things. There are countless reasons jobs are (and should be) concentrated around big cities. You are lucky and speaking from a position of privilege if this is not something you worry about.
This is not about me and so-called privileges. You forget the large amount of jobs in farming, handiwork, healthcare, and so on. There are certainly ways to decentralize through policies.
I didn't forget about any jobs. Sure, some jobs can be less centralized. But you said "There is no point in concentrating jobs around big cities". This is wrong and I corrected you.
The author has a VERY dim view of Sparta, and of the people who worship Sparta and of the quality of information the legend of Sparta is based upon (second hand roman information, from Romans, at a time where Sparta had become a sort of theme park for bored senators).
Just talking about the last stand of Leonidas and the 300 (+7000 thebans etc). Of course, a society driven purely by millitaristic macho men will implode. I have read about this a bit before (Not from this author)
I'd add that WPF was "don't bother" up until recently when WPF support was added. (Though I don't know if that means stock WPF or that it supports the breadth of WPF controls out there, and whether it requires WPF component vendors to make changes)
We just migrated our massive WPF application to .NET 8 and there are a handful of libraries that are not supported or had to be replaced but overall it was surprisingly smooth. The biggest issue we have is that garbage collection seems to have taken a huge hit and there are bugs in the Microsoft WPF components (any sort of list view in particular) but it's all relatively easy to work around.
Yes, it's partial parity, and is server only. It's also not easy to migrate; the upgrade-assistant tool typically just gives up.
The client libraries only came separately, and much later[1] , and in typical "Fuck your migration path" fashion, doesn't have any .NET standard support.
Some guy somewhere deciding to delegate threat assessment to Copilot or some other automated tool.
reply