Linked by on Tue 27th May 2008 15:00 UTC
Thread beginning with comment 315790
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.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2007-08-22
Well.. the truth is in the eye of the beholder.
So, no, developing for Win is not really painful, in my experience.
Well...while programming for Unix/Linux is relatively painless, so can programming for Windows assuming you use the right API set.
For example, programming for Win32 is quite nice and easy compared to programming for MFC. Sure MFC makes some things (dialogs) quick and easy to do, but it also throws a ton of gunk in too. CString is just horrendous compared to std::string - especially when trying to track down information on CString and see _which_ CString implementation the software is actually using (since CString itself is really just a template of multiple templates).
Sure, Win32 may require a little more hard-lifting than MFC; but overall it really is easy to use and painless.
Now, COM, ATL, etc...I won't even go there.