<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrii Kasian on Medium]]></title>
        <description><![CDATA[Stories by Andrii Kasian on Medium]]></description>
        <link>https://medium.com/@to.kandy?source=rss-1b7861583448------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sl_FEpyj5hGb78oSX0C-bA.jpeg</url>
            <title>Stories by Andrii Kasian on Medium</title>
            <link>https://medium.com/@to.kandy?source=rss-1b7861583448------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:17:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@to.kandy/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Brief History of Microsoft Programming Revolutions]]></title>
            <link>https://medium.com/@to.kandy/a-brief-history-of-microsoft-programming-revolutions-3185a4208ba1?source=rss-1b7861583448------2</link>
            <guid isPermaLink="false">https://medium.com/p/3185a4208ba1</guid>
            <dc:creator><![CDATA[Andrii Kasian]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 14:28:26 GMT</pubDate>
            <atom:updated>2025-09-18T14:28:26.215Z</atom:updated>
            <content:encoded><![CDATA[<h3>Eliminating DLL-Hell — again</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_XaBmnYPcCJQE1pOo-WFKA.png" /></figure><p>First, there was the Windows API and DLL Hell. Revolution # 1 was DDE — remember how hot links let us create status bars showing the current price of Microsoft stock?</p><p>About that time, Microsoft created the VERSIONINFO resource, which eliminated DLL Hell. But another group within Microsoft discovered a <strong>fatal flaw </strong>in DDE: <strong>they didn’t write it!</strong></p><p>To solve that problem, they created OLE (which was like DDE, only different), and I fondly remember a Microsoft conference speaker proclaiming that the Windows API would soon be rewritten as an OLE API, and every control on the screen would be an OCX. OLE introduced interfaces, which eliminated DLL Hell. Remember “in situ” fever, and how we dreamed of the day that our applications would all be embedded in a (apparently very large) Word document?</p><p>Somewhere in there, Microsoft got the C++ religion and MFC emerged and solved all our problems again, but with inheritance. Well, OLE wasn’t going to take that sitting down, so it re-emerged as COM, and suddenly we realized what OLE (or was it DDE?) was really meant to be all along — and it even included an elaborate component version system that eliminated DLL Hell. Meanwhile, a renegade group within Microsoft discovered a <strong>fatal flaw</strong> in MFC: <strong>they didn’t write it!</strong></p><p>They forthwith corrected that problem by creating ATL, which is like MFC, only different, and tried to hide all those fascinating details that the COM group was trying so hard to teach us. This stimulated the COM group (or was it OLE?) to rename themselves ActiveX and issue hundreds of pounds of new interfaces (even new versioning interfaces, which eliminated DLL Hell), along with the ability to make all our code downloadable via web browsers, complete with user-selectable viruses (ha — try to keep up with that, you ATL weenies!). Like a neglected middle child, the operating systems group cried out for attention by telling us all to “get ready for Cairo”, some weird crud that they could never really explain, let alone ship. To their credit, however, the operating system group did introduce the concept of “System File Protection”, which eliminated DLL Hell.</p><p>Meanwhile, another group inside Microsoft discovered a <strong>fatal flaw</strong> in Java: <strong>they didn’t write it!</strong> That was remedied by creating J, or Jole, or ActiveJ (honestly, I can’t remember the name), which was like Java, only different. That was very exciting, but Sun sued Microsoft under some archaic law that limits the amount of crapulence any one company can ship in a year. This was clearly an attempt to stifle Microsoft’s freedom to create products that are like other products, only different, and resulted in the creation of The Microsoft Freedom to Stuff Money in the Trousers of Congressmen Network (newsletter and $14.75 T-shirts available). Remember the J/Jole/ActiveJ program manager pounding his shoe on the table and insisting that Microsoft would never abandon his product? Silly wabbit! All this could mean only one thing — too little attention for the ActiveX (or was it COM?) group. This incredibly resilient herd of API gushers came back strong with COM+ (shouldn’t that have been ActiveX+?), and MTS. (I have no idea why there’s no “COM” or “Active” or “X” or “+” in “MTS” — they totally shocked me with that one!) They also threatened to add yet another “+” onto all their buzzwords in the very near future. Around that time, someone was yelling about “Windows DNA” and the “Windows Washboard” for a while, but that died out before I ever figured out what it was.</p><p>At this point, Microsoft had been watching the Internet for several years with growing unease.. And that brings us up to date with .NET (pronounced like “doughnut”, only different), which is like the Internet, only with more press releases. Let’s be very, very clear about one thing: <strong>.NET will eliminate DLL Hell.</strong> .NET includes a new programming language called C# (turns out there was a fatal flaw in Active++Jspresso, so just as well it died). .NET includes a virtual runtime machine that all languages will use (turns out there’s a fatal flaw in relying on Intel CPUs). .NET includes a single logon system (turns out there’s a fatal flaw in not storing all your passwords on Microsoft’s servers). In fact, it’s probably easier to list all the things that .NET does not include. .NET is absolutely going to revolutionize Windows programming… again.</p><p>For a while, things were quiet. We built our glorious Windows Forms applications with this new, shiny .NET. But then, a group at Microsoft looked at the web and saw Adobe Flash. They squinted, scratched their chins, and discovered a <strong>fatal flaw</strong> in Flash: <em>they didn’t write it!</em> This was corrected with Silverlight, a .NET-based browser plugin that was like Flash, only different. We were told it was the future of Rich Internet Applications. We were told it would run everywhere. It was poised for total domination, right up until a fruit-themed company in California decided plugins were lame, and the rest of the web agreed.</p><p>Not to worry! Another group inside Microsoft was busy looking at Windows itself. They discovered a <strong>fatal flaw</strong> in all the UI frameworks they had just built: they looked dated. So they created the Windows Presentation Foundation (WPF), which used a markup language called XAML that was like HTML, only different. It enabled slick, animated interfaces and, most importantly, <strong>eliminated DLL Hell</strong> by introducing a new deployment model.</p><p>Then came the smartphone. A <strong>fatal flaw</strong> was discovered in the iPhone and Android: <em>Microsoft didn’t make them!</em> This led to Windows Phone, a beautiful new OS that required a beautiful new developer story. First, it was Silverlight for Phone, then it became the One True Future™: WinRT. This was a complete, back-to-the-drawing-board reimagining of the Windows API. It was based on COM (or was it ActiveX?), it was asynchronous, and it was the only way to write those cool full-screen apps for Windows 8. The message was clear: there was a <strong>fatal flaw</strong> in Win32 and .NET desktop apps, and that flaw was that they still existed. This new WinRT, paired with System File Protection and the new App Store model, would finally, once and for all, <strong>eliminate DLL Hell.</strong></p><p>The world, however, did not want its server management tools to be full-screen crayon drawings. So, after a brief period of market-driven humility, the WinRT group renamed themselves the Universal Windows Platform (UWP) group, which was like WinRT, only you could put the apps in a window.</p><p>Meanwhile, a deeply philosophical group within Microsoft had an epiphany. They stared at the explosion of open-source software, at Linux, at Git, at Node.js, and discovered the most profound <strong>fatal flaw</strong> of all in the entire ecosystem: <em>they didn’t control it!</em> What followed was not a reinvention, but a corporate judo-flip. They created TypeScript, because the <strong>fatal flaw</strong> in JavaScript was its lack of C#-like features. They created Visual Studio Code using web technologies, because the <strong>fatal flaw</strong> in their own Visual Studio was that it wasn’t built with web technologies. They bought GitHub. They made a Linux subsystem run <em>inside</em> Windows. And they took .NET itself, saw the <strong>fatal flaw</strong> that it only ran on Windows, and created .NET Core. This new, open-source, cross-platform .NET was like the old .NET, only different. It used a new package manager called NuGet, which was a revolutionary component system designed to <strong>eliminate DLL Hell.</strong></p><p>This brings us to today. After buying Xamarin to solve the cross-platform mobile problem, they found a <strong>fatal flaw</strong> in it (<em>they</em> didn’t write it <em>originally</em>), and rebuilt it as MAUI. After watching containers take over the world, they found a <strong>fatal flaw</strong> in Docker (you know the drill) and now you can’t click a button in Azure without spinning one up.</p><p>But the final revolution is upon us. A very clever group at Microsoft looked at the code that we, the developers, were writing. They analyzed it with a new kind of intelligence and discovered the ultimate, terminal, earth-shattering <strong>fatal flaw</strong>: <em>they didn’t write it!</em></p><p>And so, we have GitHub Copilot. It’s an AI that writes the code for you. The solution to every problem is no longer a new framework or API, but a clever comment prompt. The endless cycle of reinvention has reached its logical conclusion: the developer himself is being reinvented as a mere suggester, a guide for the AI that does the actual work. This, we are assured, will increase productivity, reduce bugs, and, I have it on good authority, will once and for all, for real this time, we promise to address <strong>fatal flaw </strong>and finally<strong> </strong>… <strong>eliminate DLL Hell.</strong></p><p>to be continue…</p><p>based on <a href="https://web.archive.org/web/20130224033936/https://www.drdobbs.com/windows/a-brief-history-of-windows-programming-r/225701475">https://web.archive.org/web/20130224033936/https://www.drdobbs.com/windows/a-brief-history-of-windows-programming-r/225701475</a> By Ron Burk, December 01, 2009</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3185a4208ba1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>