> The concept of "filesystem" is an increasingly weak concept.
Yeah because Apple has broken that idea over and over and over. The anti-unix unix.
> The concept of "filesystem" is an increasingly weak concept.
Yeah because Apple has broken that idea over and over and over. The anti-unix unix.
Windows shows my Desktop folder in four distinct locations in the native file manager. Some representations of my home folder have more files and folders in them than others.
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.
I still don’t really understand exactly how that bullshit supposedly works, and it makes me want to throw my shitty Windows work laptop.
It reaffirms the distance I’ve put between myself and that tinker toy OS over the last decade, every day.
Install MSYS2, and use its Bash, for a better overall experience.
[dead]
It is the age old conflict, what is better a verb focused or noun focused world.
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)
> 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.
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.
But that leads to a thing where an app has a file format that contains a bunch of its data, and it acts like a mini-database anyway, except now the user needs to remember where it is located. Then if there's data that links between multiple files and doesn't belong to a particular one, it is blurred again.
Yup it's not perfect, but in the filesystem model, the file continues to exist until an alternative solution emerges. In the app model, the file (and associated data) may be locked away forever.
These are all relatively trivial problems, or (in the last case) essential risks of increased power.
No, that was just Apple and others realizing that (1) the file system needed some type of wrapper for security purposes, and (2) the move to the cloud didn't work very well with local file systems (they still don't... most of my data in the cloud isn't a "file").
Actually, macOS isn't Unix. It's in the name of its kernel: XNU: X is Not Unix. Don't let the fact that it's a certified Unix confuse you.
It's nothing to do with evil old Apple and everything to do with phones being hard to type on, and search becoming better.
It is everything to do with Apple. Everything.
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.
I remember it like this. Windows XP and earlier was a horrible era for stability and security and the world was overall less connected. Phones were always on and always connected. The iPhone was honestly the first stable internet device, that didn't sleep or pause, and the first internet device many people had that wasn't infected by viruses.
> Windows XP and earlier was a horrible era for stability and security
Huh? Windows XP was the first NT-based release for home users. It was a milestone in stability.
It was more stable after the SP2, but initially it was undermined by buggy drivers and rampant malware, NT kernel or not. True, it was better than ME…
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.
It was hailed for its improvements in stability from the time it was released. My recollection was that it was a massive improvement over 98/ME lineage. It was mostly a wash vs Windows 2000.
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.
Sure, but there were also multiple points in time (even after SP2) when you had to unplug the network to install it, because in a couple minutes of being online or in a large LAN it would get infected during the setup and shutdown. You also needed all updates and a third-party firewall on a CD. Win+R shutdown /a is still in my fingertips after all these years.
XP was godawful for years security- and stability-wise until the release of SP2.
No it wasn’t. XP was quite solid in terms of stability, miles beyond its predecessors. You have to remember that its mediate predecessor was Windows ME.
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)…”
https://en.wikipedia.org/wiki/Windows_XP
It definitely was.
> 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.
> It definitely was.
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.)
Compared to W98SE, the actual OS for home users (almost no one used ME), Windows XP was a godsend.
Security maybe, but not stability. XP SP1 was rock solid, and even RTM was nowhere close to "godawful".
iPhoto. iTunes. iCloud. iMovie. Notes.
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.
And why should they? I don't know where my browser cache is either. Or my rows in my sqlite database. Or the system clock configuration. Actually I do know: They're stored on the hard drive.
Files aren't physical.
Diff two iPhoto libraries to check if they contain the duplicate photos
Create a new library,
import the images from both libraries (https://support.apple.com/en-us/119920)
View > Utilities > Duplicates
or use jdupes or czkawka on both directories.
Great tip, but also: exactly.
On the phone itself?
On the filesystem-enabled device called Mac commonly used for semi-pro operations like file management and backup.
> And why should they? I don't know where my browser cache is either.
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.
i know where mine is, so i can clear it myself if i care.
So which is it? Is Apple not responsible for ditching the filesystem, or is it a good thing that Apple has ditched the filesystem? You can't have it both ways.
First came proprietary file formats, and they were evil. Now, un-find-able files in proprietary formats.