Huh? Windows XP was the first NT-based release for home users. It was a milestone in stability.
It was also far more secure, but it was still not nearly secure enough.
> ”Upon its release, Windows XP received critical acclaim, noting increased performance and stability (especially compared to Windows Me)…”
> It was also far more secure, but it was still not nearly secure enough.
That's one way to say "plagued by a decade of botnets."
> https://en.wikipedia.org/wiki/Windows_XP
Now google XP blue screen of death. Still alive and well then.
If the bar is Microsoft's most loathed release, then I guess you could call it stable and secure.
Weird that contemporary articles praised its stability then.
> That's one way to say "plagued by a decade of botnets."
No, it’s a way of saying that it introduced real identity-based security isolation to the OS. Prior to this every user had full access to the entire system incisions everyone else’s data who shared the system.
Unfortunately Windows XP was not hardened to the reality of the internet. (Nor were any of its predecessors.)
What most people remember of XP now is what it became after a couple of years of fixes and improvements, and the contrast with Vista.
Yes, it became more stable with the service packs, but it was a significantly more stable OS out of the gates than anything consumer users had been getting.
Rampant malware was a separate (and very significant) issue.
That much is true.
> It was mostly a wash vs Windows 2000.
No, not really. They did some empirical testing at the university I went to and the conclusion was that they kept the Windows boxes on 2k almost until Vista.
None use the file system in anything like the way their unix underpinning would have files be understood or organised for users. Hard to even know where your files are without asking the app to deal with them one by one. Predated phones and even Spotlight doesn’t do a good job of showing/knowing where your files are.
Files aren't physical.
import the images from both libraries (https://support.apple.com/en-us/119920)
View > Utilities > Duplicates
or use jdupes or czkawka on both directories.
This makes it a pain where you want to have a custom configuration. Like moving the cache to a ramdisk. My NVME disk is plenty fast, but rarely I want my browser cache to persist across a reboot. It's a pain to move the cache to /tmp/firefox-cache as an example (/tmp is a ramdisk on my laptop). Also a pain to backup profiles.
It started with the Ipod and the weird mp3 system, to the Ipad not shipping with a real file manager and is all so very obviously deliberate.
Is the core the database(the filesystem) and the apps roam around in it, or is the core the apps each with their own database.
I grew up with noun focused operating systems, which is probably why I prefer them. Here are your things and you can use various actions on them(some valid some not). And as such find the verb focused ones unpleasant to use. Here are your actions each includes it's things. But where are my things? It does not matter, each action knows where it's correct things are. But I want my things, I know they are in there somewhere. (fights the phone for a while)
The first option is evidently better for the user. The filesystem is a neutral entity with a well-defined interface, whereas each app is on its own journey. For a period of time that journey may align with the user's workflow, and both are happy. But there inevitably comes a time where the app and the user diverge, and for the user, it is imperative that they be able to switch to another app without losing access to their data.
To a user, the data matters most, and the filesystem, because of its neutrality, is the best model for access.
Reading your comment earlier, while trying to make dinner now, made me realize that the reason I hate the layout of my house might be the same reason I never got into Vim...
To get to the kitchen, I have to walk through the dining room, where all the plates, bowls, glasses are. But I can’t grab what I need yet, because I haven’t seen the food. I first need to get to the kitchen, look at what’s there, and decide what I’m going to make... Only then do I know which tools I need.
My house verb first, but my brain works noun first.
But Vim can also operate noun-first: just press `v` to go into visual mode. Then you drag out a selection, and press the command. No need to switch editors and relearn all the places where they differ. (If you're already used to Vim, of course, which might not be the case for you).
Which is why I've never tried Helix or Kakoune myself. Because the big selling point, noun-first operation, is already in Vim, just one keystroke away. Multiple cursors are a neat idea, and when I have to use VS Code I find them quite useful for doing things that I would have done with Vim macros. But I've already learned Vim macros, and there are few cases (though not none) where multiple cursors would have made something easier than the macro-based approach.
Anyway, point is, for anyone else who might stumble across this comment somehow, that Vim allows noun-first operation too: just go into `v`isual selection mode, select text with motion commands, and then press the operation command key.
Years ago I bumped into Sublime Text, which introduced me to multi cursors. I ended up becoming quite good at using regex for search, then pressing Alt+Enter to select all the matches. That satisfied my multi-selection needs, and although I tried getting into Vim later, I felt that the effort was too much and my setup already made me quite fast at editing code in multiple places.
I use Bash via Git4Windows as much as possible, but even there... `cd ~/git; cd ../Downloads; cd ../git` doesn't work because `..` from `~/Downloads/` is `~/One Drive/`.
It's... non-Euclidiean.
It reaffirms the distance I’ve put between myself and that tinker toy OS over the last decade, every day.
You should not throw your laptop because of the specifics of how the onedrive integration works. You should throw it because the onedrive integration is invasive and obnoxious.
Yeah because Apple has broken that idea over and over and over. The anti-unix unix.