Linked by Thom Holwerda on Wed 2nd Apr 2008 20:53 UTC, submitted by Matthias
Thread beginning with comment 307888
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-07
Windows Vista: The use of to many archaich techniques like Messages and heavy use of interfaces.
Uh, what? You don't have to code in MFC or the Win32 API on windows. If you find message maps archaic and bothersome, you can always find something else that scratches your itch. Even Qt.
Mac OSX: It lacks in clarity of the framework, the use of objetive C doesn't help eather.
Define lack of clarity? As far as I am concerned, the Mac as a platform provides a wide plethora of frameworks that are widely documented and intuitive to use. Of course, one mans intuitive is another mans nightmare so YMMV. However, I do agree that the choice of Objective-C is a strange one but once you get used to the syntax and terminology, you find that it is actually quite good.
Failing all that, you can still fall back to using other libraries like Qt to program on the Mac.
I understand that this is a KDE news item and as such the KDE centric users and developers will be out in force. Even so, there is no need to spread nonsense about other platforms just to make your own look better.
p.s. I use GNOME but I don't develop for it, so I'll leave that to some GNOME developer to argue the point with you.