2 ms·
> So, if it makes you feel any better, Visual Studio 2010 was developed, at least in some major part, using WPF It doesn't make me feel better, especially sinc
by beagle3 14y ago
> So, if it makes you feel any better, Visual Studio 2010 was developed, at least in some major part, using WPF
It doesn't make me feel better, especially since I have to support a product that uses WPF, suffers from a massive leak that (unless gc is _manually_ called every rendered frame) just stops the program from working without reporting any error - a bug microsoft does not intended to issue a fix for for WPF4 (so .. never going to fix): https://connect.microsoft.com/VisualStudio/feedback/details/603004/massive-gpu-memory-leak-with-interopbitmap https://connect.microsoft.com/VisualStudio/feedback/details/... - reported to Microsoft more than 2 years ago.
When this product gets rewritten, it's going to be either web or an Android app. It sure as hell not going to be using any Microsoft tool.
- saurik 14y agoI feel like I shouldn't have to say this, but: none of these complaints have anything to do with the concept of "dogfooding".
- beagle3 14y agoWell, not directly - but it's the kind of stuff that would get fixed if they were actually using it. I haven't really researched this, but AFAIK very few Microsoft products actually use WPF (or SilverLight for that matter). That's not really surprising, because most of them have a long legacy, and a rewrite of e.g. Word or Explorer to use WPF doesn't make sense. It's been my experience that when a developer actually uses the APIs they publish, they work well, are better documented (or at the very least, when you have an inquiry you can get a knowledgeable, reasonable answer from someone on the inside, as you still can from Raymond Chen about WIN32 stuff). The horrible level of support and bug fixing is an indirect observation of very little dogfooding.