4 ms·
> always did "dogfood" That's not been the case at least since .net came out. They were trying to get developers to use .net GUIs and other APIs without dogfo
by beagle3 14y ago
> always did "dogfood"
That's not been the case at least since .net came out.
They were trying to get developers to use .net GUIs and other APIs without dogfooding (WPF, WCF, WinForms, SilverLight, and a lot more). Most of them are horrible, buggy and unsupported a few short years later.
I'm not sure there is a lot left of the "Raymond Chen" camp of fanatic bug fixing and backward compatibility that was there in the Win32 days.
- saurik 14y agoSo, if it makes you feel any better, Visual Studio 2010 was developed, at least in some major part, using WPF (I remembered that one, and managed to find a reference for it on an official website). I can't say much about the other technologies, though. You certainly can't blame your WPF issues on them not eating that particular dogfood. "Get an insider’s look at how Microsoft created the next-generation, large-scale integrated development environment experience using Windows Presentation Foundation (WPF) 4." -- http://www.microsoftpdc.com/2009/CL09 http://www.microsoftpdc.com/2009/CL09 Apple, in contrast, consistently uses things that they deny access to for normal developers; not just high-level libraries and platforms that you could technically re-implement (although they certainly do this, and they do it ludicrously often), but fundamental capabilities on their platforms that they have reserved "only for Apple" (whether just by radical un-documentation, or now by controlling software distribution and manually checking for usage). The difference is dramatic: when you see Microsoft release a application for their operating system, you can feel pretty confident that if you spend enough time reading their developer documentation, you could build that exact same thing yourself. This is not the case with Apple. (This also has nothing to do with whether or not they will deprecate your code a couple years later.) I'll happily believe that Microsoft has gone horrendously downhill on this axis, though, since I stopped paying attention to them in 2008 (that's when I started doing Cydia fulltime, which led me down a path that forced me to eventually switch to using a Mac as my primary development machine). If nothing else, I am under the impression that Microsoft gave up this feature with Windows 8 Metro :(. Hence why I used the past perfect "always did" (as opposed to the present imperfect "always does"): the contention from JonnieCache was that MS does not nor nor that they ever did (as if they actually were to do so it would be "for the first time"), when radical dogfood eating that was always what made MS great and set them apart from everyone else.
- 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.