As someone who back in the day worked on plenty of Dell ultralights running 4200 RPM drives and 5400 RPM drives at best, yes, yes it was "so bad". [And these devices were on the REDMOND domain!]
Anything else is rose-colored glasses, the same glasses people wear when they reminisce about the glory days of Windows 2000 or XP, absolutely forgetting what a security nightmare they were, or the boot times of Windows 2000 (when we used to regularly shutdown rather than suspend), or the not-so-uncommon BSODs, either from native Windows components or 3rd party drivers, etc.
It uses React Native, via https://github.com/microsoft/react-native-xaml. This is probably mixed with "native" XAML components, but it's still firmly in the "buggy React app" category in my book: a framework that works well with React probably has the same design flaws that lead to React-esque crashes.
It's very difficult to find information about this online: https://news.ycombinator.com/item?id=46471701 is the only thing that remotely smells like a secondary source, with most of the rest of the search results being obvious ChatGPT output. (That, too, is Microsoft's fault.)
Disagree. If the path is shrouded behind key presses and commands which are unpublished by MS (and in some instances routes that have been closed), it may as well be.
Im going to shoot you unless you say the magic word - and technically Im not even forcing you into it, you could have said the magic word and got out of it!! Whats the magic word? not telling!
Anyway Microsoft and any software developer can be compelled to practically do anything, you don't want to be blocked in some jurisdictions (even less the US) and the managers do not want to go to jail to protect a terrorist, especially if nobody is going to know that they helped.
Some even go that far that they push an update that exfiltrates data from a device (and some even do on their own initiative).
And even if you are not legally compelled. Money or influence can go a long way. For example, the fact that HTTPS communications were decipherable by the NSA for almost 20 years, or, whoops, no contract with DoD ("not safe enough"...)
Once the data is in the hands of the intelligence services, from a procedure perspective they can choose what to do next (e.g. to officialize this data collection through physical collection of the device, or do nothing and try to find a more juicy target).
It's not in the interest of anyone to prevent such collection agreement with governments. It's just Prism v2.
So seems normal that Microsoft gives the keys, the same that Cloudflare may give information about you and the others. They don't want to have their lives ruined for you.
The original Windows 2000 guidance for AD was corp.example.com, from my recollection. The silly .local thing (which does predate mDNS) happened as a result of the Small Business Server refresh for Active Directory.
The entire point of Macintosh is that you don't need to know anything about it (and Apple used to actively try to hide things you didn't need to know about). Or at least that is the user it has always been targeted at since the original Mac OS was released.
Windows used to be known as the OS you'd "have to" tinker with.
Early versions of OS X allowed more freedom in what you could do with the OS. As soon as SSV/SIP entered, that cut off a lot of freeform access.
This is standard, especially when the size of the company grows. Actually, Microsoft might be a rare exception.
Extensions are full of malware of various sorts, so it makes sense that they take them away. Allow list vs. block list makes sense as a block list is impractical to maintain.
Only thing you can do is complain to management and prove with real #s how this is impacting productivity.
But if you're a webdev, it's super unlikely today that you need local admin and cannot work within an allow list of applications. If you're a driver dev, sure I can see how it might be a blocker.
I know who runs that blog, but that's a really exaggerated take.
Notepad has had nearly identical UX from Windows 1.0 until 10. Sure, there's a search feature that appeared at some point, ditto with the status bar, at some point they made it able to open files larger than 64K, and apparently you can open files from URLs directly?
Five or so noticable changes in an extremely lightweight and utilitarian application in thirty years is not at all like completely redesigning it into an AI slop machine.
Tabs are fine I guess but also: it's NOTEPAD.EXE. Its purpose to be super primitive and launch in 2 milliseconds and give you a place to paste or type some text real quick. Anyone who needs a good text editor with actual features will just download the good text editor of their choice.
Simple example of the newly poor UX. I try to start notepad to jot down some scratch. It sluggishly reopens whatever it previously had open (e.g. from before a reboot)...and in doing so, doesn't actually create a new document for me.
As someone who back in the day worked on plenty of Dell ultralights running 4200 RPM drives and 5400 RPM drives at best, yes, yes it was "so bad". [And these devices were on the REDMOND domain!]
Anything else is rose-colored glasses, the same glasses people wear when they reminisce about the glory days of Windows 2000 or XP, absolutely forgetting what a security nightmare they were, or the boot times of Windows 2000 (when we used to regularly shutdown rather than suspend), or the not-so-uncommon BSODs, either from native Windows components or 3rd party drivers, etc.
reply