Earlier quoted context omitted.
A lot of Classic Mac apps just used the resource fork to store all their data. It was basically used as a Berkeley DB, except the keys were limited to a 32-bit OSType plus a 16-bit integer, and performance was horrible. But it got the job done when the files were small, had low on-disk overhead, and was ridiculously easy to deploy. Once you pushed an app beyond the level of usage the developer had performed in their…
The rejoicing was definitely not universal. It really felt like the NeXT folks wanted to throw out pretty much the entire Mac (except keeps its customer base and apps) and any compatibility had to be fought for through customer complaints. Personally, MacOS X bundles (directories that were opaque in the Finder) seemed like a decent enough replacement for resource forks. The problem was that lots of NeXT-derived utili…
The Origins of DS_store (2006)
171–180 of 280 posts
Re: The Origins of DS_store (2006)
#172Earlier quoted context omitted.
>The Finder has so many bizarre quirks and it's so slow to proliferate updates that it's just embarrassing Say what you will about Windows, but the Explore file manager has always been pretty rock solid.
Hmm. Wasn't it completely unreliable for moving around large numbers of files at the same time? Like if file #243 of 400 failed for some reason, you could actually lose data? I don't know any more because I use Total Commander on Windows...
Re: The Origins of DS_store (2006)
#173Earlier quoted context omitted.
Hmm. Wasn't it completely unreliable for moving around large numbers of files at the same time? Like if file #243 of 400 failed for some reason, you could actually lose data? I don't know any more because I use Total Commander on Windows...
I'm not aware of any bugs like that. Got any links maybe?
I prefer the good ole two pane file managers and I actively avoid both the finder and explorer most of the time.
Re: The Origins of DS_store (2006)
#174That's how I see these files. And maybe one day, we can have and edit our own .gitignore -like files for such Inattentional blindness[0].
[0]: Inattentional blindness
Re: The Origins of DS_store (2006)
#175Earlier quoted context omitted.
I credit ResEdit hacking partially for steering my path towards becoming a programmer. I had my Classic Mac OS installs throughly customized, as well as the other various programs and games that stored their assets in resource forks. It was a lot of fun and something I’ve missed in modern computing. Not even desktop Linux is really fills that void. ResEdit and the way it exposed everything complete with built-in edit…
ResEdit and using it to modify Escape Velocity is 100% the reason I’m still in this industry.
Re: The Origins of DS_store (2006)
#176Earlier quoted context omitted.
Explorer uses a hidden desktop.ini file for this.
Negative. desktop.ini doesn't get edited when you switch (for example) from Details to List. Also, I think only the desktop allows moving icons around freely.
I'm pretty sure Windows used to allow you to move icons around, I clearly remember making a mess on some Windows 98 folders. Maybe they removed that feature recently?
Re: The Origins of DS_store (2006)
#177Earlier quoted context omitted.
All file operations have been watched by Spotlight since forever at this point.
Except for ignored file types and folders you marked as private.
Re: The Origins of DS_store (2006)
#178Earlier quoted context omitted.
macOS is tricky now. I just looked via Finder to see if I had any .DS_Store files on my network volumes, and it appeared not. However, when I went to Terminal, sure enough, they were there. I now can't trust Finder's ability to show hidden files, as it only shows the hidden files it thinks a user should care about, rather than all hidden files. Not good. Since my network shares are for a local Synology, it's not a a…
If I remember correctly there is an option in Synology DSM to not let clients create .DS_Store files in network shares.
Re: The Origins of DS_store (2006)
#179Earlier quoted context omitted.
macOS is tricky now. I just looked via Finder to see if I had any .DS_Store files on my network volumes, and it appeared not. However, when I went to Terminal, sure enough, they were there. I now can't trust Finder's ability to show hidden files, as it only shows the hidden files it thinks a user should care about, rather than all hidden files. Not good. Since my network shares are for a local Synology, it's not a a…
My synology NAS drops turds in lots of directories too.
Re: The Origins of DS_store (2006)
#180It's worth mentioning how to turn off the creation of .DS_Store files by default while browsing network volumes - otherwise the directory modified timestamps are updated as you browse using the Finder, which is Just Plain Terrible. https://old.reddit.com/r/MacOS/comments/lvju40/comment/gpc8i...
Personally I make sure mac users do this before they get write access to a network share. It's just a matter of common curtesy IMHO.