Hacker News Reader

Comment by gruez | Hacker News Reader

>and you start to uncover Windows annoyances that you never knew existed because you were used to them and conditioned into thinking they were normal for so long

..which promptly get replaced with mac annoyances. Random ones off the top of my head:

* closing a window (using the red x icon) doesn't close the app

* overwriting a folder deletes existing contents, rather than merging them

* weird scroll acceleration that makes clicky scroll wheels unusable

View on HN

>* overwriting a folder deletes existing contents, rather than merging them

Wait. If there truly is not a setting for this then it makes finder unusable as a file explorer and arguably the entire OS. Recursive merge is one of the most fundamental things a personal computer does.

There is in fact a workaround, hold down option while copying the folder. Note that there needs to be at least one subitem in common.

that's the pretty standard behavior on unix. Unless the window manager goes out of its way to override it, mv'ing a folder to a place where one already exists will replace the old folder with the new one.

You can go out of your way to do it manually with rsync and similar tools, of course, but by default you're moving directory pointers around, not merging trees.

How many Unix graphical OS distributions are there even, let alone how many are installed?

Nautilus, the default file manager of GNOME (and by extension Debian and its children such as Ubuntu) handles recursive merge. This isn't an issue on Linux.

It's obviously bad design to have something as high level as a file manager be a glorified 2D wrapper of 2 command line tools.

The window manager manages windows. It has nothing to do with the filesystem or how it's presented to the user.

They meant "window file manager", ie graphical file manager.

> that's the pretty standard behavior on unix.

Not even slightly:

  $ mkdir 1 2
  $ touch 1/foo 1/bar 2/baz 2/quux
  $ mv -T 2 1
  mv: overwrite '1'? y
  mv: cannot move '2' to '1': Directory not empty
  $ mv --force -T 2 1
  mv: cannot move '2' to '1': Directory not empty

I hate being the kind of internet guy who's like "X sucks" about something a lot of people have worked on, but I really, really, really dislike Finder. It fails as a file explorer on several fundamental levels. For example network shares in Finder feel so tenuous and like they could break any instant. Sometimes after you sleep your Mac and wake it up, you have to reboot to be able to reconnect to a network share.

Well, at least Finder used to be good... before OS X.

> * closing a window (using the red x icon) doesn't close the app

There are applications with more than one window.

> * weird scroll acceleration that makes clicky scroll wheels unusable This is called "progress" or UI/UX or whatever name they have today for brain damage . Some years ago the Apple GUI was looking good. Then the replaced the window buttons with coloured circles. Guess which one is which ?

>There are applications with more than one window.

And windows handles it just fine. Clicking X on one window doesn't close the entire app.

> * closing a window (using the red x icon) doesn't close the app

Command-Q is your friend.

I never understood the rational behind the second one... Sure I get that's how directories probably work underneath the hood but in a GUI I guess I expected a bit more "magic"

Reply on news.ycombinator.com