Linked by Thom Holwerda on Fri 13th Jul 2012 23:39 UTC
Permalink for comment 526760
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2007-07-01
I see three possible reasons for those issues in Metro apps.
#1 Microsoft has clueless programmers and nobody checks their work. Stack ranking guarantees no-one competent will ever tell them how to do better.
#2 Microsoft's programmers have disincentives to do anything properly. If it compiles and works in the most trivial case, ship it. That's the agile way.
#3 Metro architecture is so screwed up it can't deal with multiple working threads. To be fixed in the next version of Windows.
Btw. Clicking to bring up tab bar to change tabs? Really?