Linked by Thom Holwerda on Wed 2nd Jan 2013 23:38 UTC
Thread beginning with comment 547008
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.
Eck... The year on that article didn't register properly when I read it. I always get mixed up the first few days of a new year. I was thinking it was recent (i.e. 2012)
Regardless, it still supports my argument more or less. A year ago the developer was making the same complaints that Microsoft is making now. Nothing has really changed in the last year, they are still dealing with API breakages as they come. Microsoft can't afford to operate like that - they need guarantees or at least private channel communications about upcoming changes with some lead time.




Member since:
2013-01-03
Is it me or is that news article from over a year ago? (Dec 22nd, 2011, discussing a takedown on Jan 1st, 2012, and we are in 2013 ..)