Linked by Thom Holwerda on Mon 9th Jul 2012 02:01 UTC
Permalink for comment 526295
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2009-05-19
I'm probably going to get hate mail for this, but it seems to me like a lot of the developer stuff they have made in the last decade is filling in where Visual Basic left off, but with a more serious "software engineering principles" side to it.
So ... If you're dead serious these days about writing a high performance Windows app, do you choose the new platform or do you still code in C/C++ ???
It seems like a lot of important legacy apps have yet to make the transition. So I wonder?
Does Metro complicate things now too?
I always worried about getting too involved with writing Microsoft specific stuff (e.g. C#, WPF, etc.) because I felt they changed tact too often. Before you knew it, everything you bothered to learn about was deprecated again. :-(