FROM : Gregory Weston
DATE : Fri Jun 27 21:12:44 2008
Hans Larsen wrote:
> I'm not up for a debate on wether Apple, Linux or
> Microsoft is right or wrong on ways of doing things. I prefer the OSX
> way, but when you design code based on Linux/Windows, and then need to
> port to OSX in a very short time, some shortcuts must be made.
I don't think it's even an issue, though, of whether one way or
another can be argued as abstractly "right." If your client wants
this app to actually by adopted by Mac users, it really should act
*for them* like a Mac app. Gratuitous consistency among platforms, at
the cost of consistency within the platform is a great way to set
yourself up for failure. (For what it's worth, I'm also not fond of
Mac-like programs on Windows. It's just jarring to the point where
it's distracting and disruptive.)
> The client is aware of the constraints/problems. We told them
> everything (from no-64bits-in-carbon to shouldn't-use-custom-cursors).
> They have the last say.
But I'd argue that you have a responsibility to inform them of the
likely consequences of their actions. Presumably that's part of why
they hired you instead of just buying a book on Carbon for one of
their existing coders and watching the project spiral into death that
way.
DATE : Fri Jun 27 21:12:44 2008
Hans Larsen wrote:
> I'm not up for a debate on wether Apple, Linux or
> Microsoft is right or wrong on ways of doing things. I prefer the OSX
> way, but when you design code based on Linux/Windows, and then need to
> port to OSX in a very short time, some shortcuts must be made.
I don't think it's even an issue, though, of whether one way or
another can be argued as abstractly "right." If your client wants
this app to actually by adopted by Mac users, it really should act
*for them* like a Mac app. Gratuitous consistency among platforms, at
the cost of consistency within the platform is a great way to set
yourself up for failure. (For what it's worth, I'm also not fond of
Mac-like programs on Windows. It's just jarring to the point where
it's distracting and disruptive.)
> The client is aware of the constraints/problems. We told them
> everything (from no-64bits-in-carbon to shouldn't-use-custom-cursors).
> They have the last say.
But I'd argue that you have a responsibility to inform them of the
likely consequences of their actions. Presumably that's part of why
they hired you instead of just buying a book on Carbon for one of
their existing coders and watching the project spiral into death that
way.
| Related mails | Author | Date |
|---|---|---|
| No related mails found. | ||






Cocoa mail archive

