[netcan]

I don't care much about native feel. When the things I like in a platform aren't preserved (cmd-comma for preferences), I get annoyed. When the things I dislike (OSX maximize) aren't preserved, I like it.

Overall, I think a little convention breaking is good. First, code once is a genuine advantage. It means faster releases across more platforms and more benefit to users. Second, it generates a little internal competition. If more apps break OSX maximize and users like it, maybe Apple will change it.

In the best cases, the freedom to invent the wheel yields gradually improving wheels.

[DanBC]

> In the best cases, the freedom to invent the wheel yields gradually improving wheels.

Except on mobile we have a bunch of reinvented wheels of varying non-round shapes and they all suck, leaving the user to guess what weird combinations of touching, tapping, swiping, double fingered tapping, etc will perform the desired action for this particular app.

[emehrkay]

Call me strange, but I prefer the old maximize. It only took up what space was needed for the window to not scroll horizontally, but did a full vertical. This had a few advantages for me: 1. I can see, and interact with, all of the other windows that I have open in the bkg without too much context switching (command+click to interact without giving a window focus) and 2. since I have an ultra wide monitor at work (and a 27 inch iMac at home), full screening for a browser or text editor is wasted space when I needed reference materials open too.

Apple's own iTunes app breaks a lot of pre-defined ui behavior -- cannot double click titlebar to minimize, the strange mini-mode, and it doesn't quite respect the screen boundaries. I just prefer for things that I use often to have an expected, common behavior.