31–40 of 127 posts
For git users: echo ".DS_Store" >> ~/.gitignore git config --global core.excludesfile ~/.gitignore If you spend many man hours dealing w/ .DS_Store files in source code repos you're doing something wrong.
Nobody individually spends too much time on dealing with them. It the global accumulation of man hours having to deal with them that is a travesty.
Forgive if it's not exact, I'm on a mobile device. But that should save you effort.
When zipping files on OSX, the common way is to right click on your directory of choice in Finder and select “Archive as…”. This creates a Zip file, with the unwanted addition of a _macosx folder. According to this [1] article, the folder is used for thumbnails, cache data, and other meta data. I have seen these folders work their way into github repos, and I am reminded of their uselessness almost every time I open a zip archive. In the past it may have been justified (to reduce cpu load generating thumbnails and cache files while unzipping), but just like .DS_Store, the time has come to abolish these folders from zip archives.
[1] http://floatingsun.net/2007/02/07/whats-with-__macosx-in-zip...
WOW - the best feature here is that Total Finder enables cut-and-paste to move files! This is the one thing I have missed terribly from Windows. It boggles my mind that Apple thinks all that clicking, rearranging windows, dragging, shifting, and dropping is a sane way to move files. Intuitive yes, but more painful than typing it out at a command line. Sometimes Apple gets stuck in "make it pretty" and forgets "make i…
Earlier quoted context omitted.
Nobody individually spends too much time on dealing with them. It the global accumulation of man hours having to deal with them that is a travesty.
Find . -name ".DS_Store" | xargs rm Forgive if it's not exact, I'm on a mobile device. But that should save you effort.
But it's still something, when I shouldn't have to do anything.
It's definitely time for these to go.
Earlier quoted context omitted.
But Apple doesn't actually make hardware, and their OS and hardware designs are meant to be paired together. OS X has some flaws, but I think it's better than the alternatives in the market.
>Apple doesn't actually make hardware I don't understand this comment. Apple absolutely makes their own hardware. They pride themselves on the A4/5 series processors and took meticulous care in designing the unibody styling that their laptops have.
The first important step of developing a tool is to look around to see if there is something that you can just use or modify slightly to fit your needs.
That's interesting... The PC equivalent is thumbs.db, which can be disabled through a simple OS option. One of those rare occasions where a PC is actually more user-friendly than a Mac. Oh wait, did I just open Pandora's box?
I think desktop.ini is more like .DS_Store than thumbs.db is.
desktop.ini is closer from a functionality point of view, but in practice I see much less of it compared to Thumbs.db.
That's interesting... The PC equivalent is thumbs.db, which can be disabled through a simple OS option. One of those rare occasions where a PC is actually more user-friendly than a Mac. Oh wait, did I just open Pandora's box?
OSX - supposed to be simple to use and the defaults are supposed to "just work" and make sense to most people (drag an "icon" to the "trash" to "uninstall" it made no sense to me)
Linux (old-school) - made for users who care about the details and will take days or weeks to set up their system. Arch is still like this. Stuff adheres to philosophical standards and POSIX.
Linux (new-school) - trying to be like OSX with the "sane defaults; just works in most cases" but also tweak-able as much or as little as you like. Fedora 16 is my current weapon of choice for work/dev.
Windows - the "bloated swiss army knife". It's trying to have the "sane defaults" of OSX with the configurability of Linux, but the architecture is all stupid and you get error codes in hexidecimal that say "an unknown error has occurred!". Going back to Windows after OSX or Linux is pretty awful, honestly. Really the only thing it has going for it would be "it's popular", so it's likely that someone else also had error 0x8BADF00D and knew how to fix it. Hating aside, Windows being not open-source really hurts when you're trying to fix/debug something -- you can tail the error logs until the cows come home, but unless you're a Microsoft developer, it'll probably be pretty opaque (OSX is sometimes bad about this too -- ever have fun with KEXT bingo?)
The solution, obviously, is to just have a damn cache of these somewhere ELSE on the system (but not the registry, because the registry was one of the worst software ideas OF ALL TIME. What other critical system database lets anything write to anywhere at any time? Smart, guys, smart...)
That's interesting... The PC equivalent is thumbs.db, which can be disabled through a simple OS option. One of those rare occasions where a PC is actually more user-friendly than a Mac. Oh wait, did I just open Pandora's box?
Having said that, your example is bad because: - your "simple os option" is hidden in an advanced administrative tool called "Local Group Policy Tool" (or previously Registry) - OS X has the same disable .DS_Store option hidden in a similar administrative interface (Terminal + defaults write ...)