5 ms·
I wouldn’t say I work with files a lot, but when I do, Finder seems to work ‘fine’. What do you find ‘appalling’ about it? If I’m missing the option to make my
by tokamak-teapot 5y ago
I wouldn’t say I work with files a lot, but when I do, Finder seems to work ‘fine’. What do you find ‘appalling’ about it? If I’m missing the option to make my life much easier by using an alternative I’d like to at least try something else out.
- johnvaluk 5y agoYou know those completely useless files (.DS_Store, ._foo.bar, etc.) that you see whenever you expand an archive or clone a repository from a developer who uses a Mac? Finder drops those turds.
- laumars 5y agoYou can’t input paths for starters. That means you can’t open dot files or navigate dot directories. Of which there are a great many in FOSS. The answer is to open up a terminal and run ‘open .blah’, which is just an appalling work around to a simple problem. Even Windows handles this use case better and that’s saying something.
- qwytw 5y agoYou can input paths with “Go To Folder” (Command+Shift+G by default) but it's a bit cumbersome.
- deleted 5y ago[deleted]
- 1764927 5y agoCMD+Shift+. reveals hidden files in Finder.
- laumars 5y agoGreat, another non-discoverable key combination I need to memorise. You can guarantee I’d have forgotten that by the time I next need to use it. GUIs are meant to be simple for discovering features. I really dislike how Apple hides away all the useful features. It doesn’t need to be this way and it makes working with macOS a real pain in the arse.