Annnnnd Microsoft adds yet another layer of failure onto their API pile: https://msdn.microsoft.com/en-us/library/windows/desktop/hh802935(v=vs.85).aspx … (via @gunvulture)
-
-
Replying to @tweets_dan
@gunvulture
@cmuratori@Jonathan_Blow Probably how it should have been done from the beginning. Then it wouldn't be perceived as complex :)1 reply 0 retweets 0 likes -
Replying to @PolymorphNinja
@PolymorphNinja @gunvulture@Jonathan_Blow Actually it's awful, and it _has_ been affecting everyone since Windows 7, I found out.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@PolymorphNinja @gunvulture@Jonathan_Blow The Windows API Sets thing is actually what fucked up all the DLL linking after XP!1 reply 0 retweets 0 likes -
Replying to @cmuratori
@PolymorphNinja @gunvulture@Jonathan_Blow It used to be relatively straightforward to manually repair a bad install using Depends.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@PolymorphNinja @gunvulture@Jonathan_Blow Now it is essentially impossible. I've had _tons_ of problems with this crap.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori @gunvulture@Jonathan_Blow MS is in the unfortunate position of attempting to maintain b/w compatibility while trying to move fwd1 reply 0 retweets 0 likes -
Replying to @PolymorphNinja
@PolymorphNinja @gunvulture@Jonathan_Blow It's not an unfortunate position. That's called API design.4 replies 0 retweets 0 likes
@PolymorphNinja @gunvulture @Jonathan_Blow They're just not good at it, and continue to make the same mistakes over and over again.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.