Speak for yourself. I'm going to migrate all of my 22-bit RSA keys to a longer key length. And not 24 bits, either, given that they're probably working on a bigger quantum computer already. I gotta go so long that no computer can ever crack it.
64-bit RSA will surely be secure for the foreseeable future, cost be damned.
They did PR campaigns against Linux and OpenOffice for quite some time – until cloud computing took off and it turned out they could earn more money by supporting Linux than by fighting it.
In fact, Microsoft weren't happy about FOSS in general. I can still remember when they tried to make "shared source" a thing: They made their own ersatz OSI with its own set of licenses, some of which didn't grant proper reuse rights – like only allowing you to use the source code to write Windows applications.
True, although that has happened with F/OSS as well (like with xz or the couple times people put Bitcoin miners into npm packages). In either case it's a lot less likely than the software simply ceasing to be supported, becoming gradually incompatible with newer systems, and rotting away.
Except, of course, that I can pick up the decade-old corpse of an open source project and try to make it work on modern systems, despite how painful it is to try to get a JavaFX application written for Java 7 and an ancient version of Gradle to even compile with a recent JDK. (And then finally give up and just run the last Windows release with its bundled JRE in Wine. But in theory I could've made it work!)
Note that this specifically talks about proprietary platforms. Locally-run proprietary freeware has entirely different potential issues, mostly centered around the developer stopping to maintain it. Locally-run F/OSS has similar issues, actually, but lessened by the fact that someone might later pick up the project and continue it.
Admittedly, platforms are very common these days because ~~the web is an easily accessible cross-platform GUI toolkit~~ SaaS is more easily monetized.
The main issue was that Vista asked for admin rights all the time. One of the first things they addressed with SP1 was to require admin privileges for fewer operations, cutting down on the number of UAC prompts.
And I wouldn't know where to start using it. My problems are often of the "integrate two badly documented company-internal APIs" variety. LLMs can't do shit about that; they weren't trained for it.
They're nice for basic rote work but that's often not what you deal with in a mature codebase.
Like every time there's an AI bubble. And like every time changes are that in a few years public interest will wane and current generative AI will fade into the background as a technology that everyone uses but nobody cares about, just like machine translation, speech recognition, fuzzy logic, expert systems...
Even when these technologies get better with time (and machine translation certainly got a lot better since the sixties) they fail to recapture their previous levels of excitement and funding.
We currently overcome what popped the last AI bubbles by throwing an absurd amount of resources at the problem. But at some point we'll have to admit that doubling the USA's energy consumption for a year to train the next generation of LLMs in hopes of actually turning a profit this time isn't sustainable.
Depends. On Linux or older macOS where light mode typically means a comfortable light gray? Light mode is the way to go. On Windows where light mode means an eye-searing onslaught of #FFFFFF? Dark mode is the only sensible choice.
And that's why copyright infringement is a crime, just not the same crime as theft.
In my experience rear-mounted sensors are the most accurate, closely followed by under-screen sensors. Side-mounted sensors are utter garbage.
Accuracy isn't even that much of an issue, it's that the side-mounted ones are far too easy to accidentally trigger just by handling the phone. I can't count the number of times my last two phones told me I had three incorrect fingerprint attempts after I had just pulled them out of my pocket.
Then I got a Pixel and I have no more such issues and virtually perfect accuracy. Same on a Samsung tablet. Same on an old phone I had where the power button was on the rear and had a full-size sensor.
Basically, I'm perfectly happy with any front- or rear-mounted full-size sensor. Those tiny side-mounted ones suck.
It happens on Linux – after your package manager has updated Firefox. Which typically means that you told it to. So it's not really a surprise.
Milky oolong. It has just the right amount of sweetness and just evokes feelings of coziness for me. Sometimes I add a little bit of jasmine as well.