Bonum Certa Men Certa

Microsoft on “Embrace and Extend”, the “Windows API Franchise”

Summary: Old lessons about Microsoft's intentional sabotage through “embrace and extend”; use of the Windows API with software patents (like Mono's problem)

T

ODAY'S INTERESTING exhibit arrives after a lot of work on the Wiki. We have hundreds more coming. We will summarise key observations drawn from Exhibit plex_5906 (1997) [PDF], which contains an E-mail from Aaron Contorer to Bill Gates. The full exhibit is available as plain text at the bottom, but here are the bits worth paying attention to, as well as corresponding background.

We start with the realisation -- as Microsoft confesses to it -- that Windows is at great risk.

Today we face the largest threat Microsoft has faced since the success of Windows For the first time, there is a really credible threat to our position as the leading platform for ISVs to write to.


Fear of Java comes into play:

There are three possible ways to address the threat of the Java platform. One is to do nothing and gradually die as others innovate around us. The second is to join the parade of people who are saying "let's kill Microsoft and share their market among us” - good for everyone else, but reducing us to the much smaller role of a common software company like Lotus or Borland or even Symantec. Thats a great way to make all our stock options worth zero, even If we would not technically be out of business. The third choice is to make major innovations to our platform so people still prefer to write to us instead of some tepid cross-platform Java layer. This is our only real option.


We have already revealed the gory details about Microsoft's attack on NetPC (sometimes referred to as "NC"). The Gartner Group helped Microsoft's attack, as always. Here is some more information from Microsoft:

Our competitors are not stupid, so they are pushing the Java platform as the solution for programs that really need to run closer to the user. Sure, its a half-assed solution and isn’t compatible with anything and in fact scarcely exists, but hey, at least it’s not Windows. With Oracle and HTML-generating code on the server and a browser with Java on the client, you have a very crude, complicated, but functional platform for developing line-of-business applications more specifically distributed applications which take advantage of all the interactivity and media-richness that purely centralized mainframe apps never had


Microsoft is then defining "Embrace and Extend":

In economics there is a well-understood concept called switching costs - how much it costs for a trading partner to change partners. Our philosophy on switching costs is very clear: we want low switching costs for customers who want to start using our platform, and we want to provide so much unique value that there are in effect high costs of deciding to move to a different platform. There is a name for this: it is called Embrace and Extend.

Embrace means we are compatible with what’s out there, so you can switch to our platform without a lot of obstacles and rework. You can switch from someone else’s Java compiler to ours; from someone else’s Web server to ours; etc. Customers love when we do this (as long as we don’t spend our energy embracing extra standards no one really cares about); our competitors are not so sure they like It because they prefer us to screw up.

Extend means we provide tremendous value that nobody else does, so (A) you really want to switch to our software, and (B) once you try our software you would never want to go back to some inferior junk from our competitors. Customers usually like when we do this, since by definition it’s only an extension if it adds value. Competitors hate when we do this, because by adding new value we make our products much harder to clone - this is the difference between innovation and just being a commodity like corn where suppliers compete on price alone. Nobody builds or sustains a business as successful as Microsoft by producing trivial products that are easy to clone - that would be a strategy for failure.

If we fail to embrace, we can lose because there are big barriers to buying our products. But if we Fail to extend, or do only humble work that is easy to clone or to surpass, we automatically lose because our competitors will spend literally billions of dollars to clone our work and replace us.


With that in sight, think about MSODF and how Microsoft broke interoperability in other malicious ways [1, 2, 3, 4, 5, 6, 7].

The "Windows API" is then described as "Embrace and Extend" against NC specifically:

Windows was a very successful embrace-and-extend move. People already had DOS machines and DOS apps, and we were able to go in and say "add this to your machine and it wLll just get better.” Wow! What a deal! It seems to have worked out all right so far. NT is a very similar move; although It’s not trivial to upgrade from Win95 to NT. in general you can use the same computer, same apps. and same APIs as before, plus more.

The really big win in Windows is the API. An app that calls the Windows API is effectively calling upon thousands of person-years of engineering work to help their app get its job done in a very specific way. You could argue !hat the API is too hard to use, that not every library is as fast as it should be, or other serious imperfections, but the fact remains: if you took away Windows, that apphcation would no longer work.

The Windows API is so broad, so deep, and so functional that most ISVs would be crazy not to use it. And it is so deeply embedded in the source code of many Windows apps that there is a huge switching cast to using a different operating system Instead. You can't just take a Windows app and stick it on some weird Java NC from Oracle, for example, and expect it to work - the guts just are not there. For many customers, the cast of reworking all their apps would be huge.


Watch this:

In short, without this exclusive franchise called the Windows API, we would have been dead a long time ago.


Think about the role of Mono and why it helps Microsoft. Remember that this whole memo is about fighting Sun's NC and Java, which is cross-platform. Oracle, which now owns/buys Sun, was part of this programme at the time.

Watch how Microsoft intends to use software patents to shield its territory (it is just as though Mono is history repeating itself):

We are doing all of this. We are fixing TCO and further improving our dev tools. We are providing new value such as Viper and great multimedia and unified storage. We are making sure that Windows, not some new platform, is the most attractive place to run apps written in this now programming language. We are building the best virtual machine in the world, and optimizing it to run on Windows. We are even making sure you can run your Windows apps remotely on an NT server if all you have on your desk is a GUI terminal. As if all this work were not already hard to copy, we are also getting a bunch of patents to further protect It against cloning.


On the role of ActiveX and DirectX in merely preventing platforms from becoming a commodity, to use Bill Gates' explanation:

Let me be dear we have no problem with the Java language or with running Java apps really really well on our platform. But we are explicitly not in the business of making it easy for people to write apps that get all the features of Windows on a non-Windows platform. “Pure cross-platform portability” is another way of saying “commoditize the OS.” In this vision, every OS is just an engine for running this layer called Java as fast as possible, and adding any value below the Java layer Is explicitly against the rules.

Sun has already figured this out and has launched its 100% pure Java” marketing program, which literally certifies apps as running the same on any client OS. Programs that call a Windows API or use ActiveX or DirectX, or any platform-specific feature, are by definition not 100% Pure Java, and are therefore evil. Hey, If you were Sun, you would say this too!


As usual, there is a lot to be learned from this. Although it is over a decade old, this was not seen before in the public arena, just in courts for the most part. Microsoft settled to keep it away from the public eye.

"Those who do not learn from history are doomed to repeat it."

                 -- George Santayana




Appendix: Comes vs. Microsoft - exhibit plex_5906, as text










Erik Stevenson (LCA) From: Aaron Contorer Sent: Friday, February 21. 1997 12:47 PM To: Bill Gates Subject: Memo material

This is 1 page of new material, followed by some closely related material I wrote and sent you on 2/12.

Today we face the largest threat Microsoft has faced since the success of Windows For the first time, there is a really credible threat to our position as the leading platform for ISVs to write to. Windows faces challenges in satisfying end users and IT organizations, but we have a lot of smart work underway to address these problems. By contrast, we are not executing on a strategy that lets us maintain our leadership position as the people who define the platform for ISVs.

Owning this platform is the Microsoft asset. It is the difference between growing to twice our current size in the future, or shrinking to much less than the role we enjoy today.

There are three possible ways to address the threat of the Java platform. One is to do nothing and gradually die as others innovate around us. The second is to join the parade of people who are saying "let's kill Microsoft and share their market among us” - good for everyone else, but reducing us to the much smaller role of a common software company like Lotus or Borland or even Symantec. Thats a great way to make all our stock options worth zero, even If we would not technically be out of business. The third choice is to make major innovations to our platform so people still prefer to write to us instead of some tepid cross-platform Java layer. This is our only real option.

For over half a year I have been upset that some people at Microsoft are apparently working hard on plan 2 to destroy the value of the Windows API. Of course I agree that we must win against the Java platform, but a belief that we have to just match everyone else’s actions one for one is fundamentally misguided and wrong it makes us a commodity player, one of the pack, instead of the leader. - Centralized Computing

Sun, Oracle, and Netscape are all pushing a new model of [almost] centralized computing. They all acknowledge that Microsoft holds tremendous sway over the desktop platform, so they all want to quickly strip as much value and spending as possible off of the desktop and onto the server where they can charge premium prices and push their own platform offerings.

At the same time, they know this is fundamentally wrong. There are good reasons why a big company in the 1990’s uses thousands of small and midsize CPUs instead of one giant Cray supercomputer to do all the work. Centralized machines have poor price/performance when they get too large; they have high latency for ordinary interactive tasks like typing and even worse latency for multimedia (unless you literally spend a fortune on your network); and they fail to take advance of the principle of colocation putting the processor close to the inputs and outputs it needs to work with.

Our competitors are not stupid, so they are pushing the Java platform as the solution for programs that really need to run closer to the user. Sure, its a half-assed solution and isn’t compatible with anything and in fact scarcely exists, but hey, at least it’s not Windows. With Oracle and HTML-generating code on the server and a browser with Java on the client, you have a very crude, complicated, but functional platform for developing line-of-business applications more specifically distributed applications which take advantage of all the interactivity and media-richness that purely centralized mainframe apps never had

Fortunately for us, this solution is an incredible hack. Real applications require work in Oracle and Java HTML and Gci, and except perhaps for DNS, no unifying architecture ties the whole thing together, If you

Plaintiffs Exhibit 5906 Comes V. Microsoft

TXAG 0008204 CONFIDENTIAL

MS-CCPMDL 000000292576 CONFIDENTIAL

want to write an app like Amazon.com or a comparable intranet app, you are on your own. Even a cool tool like Visual InterDev merely serves to paper over this disastrous platform, not to fix It.

This situation leaves open a huge strategic opportunity: to provide a better way to write distributed applications.

We need to make clients and servers more powerful and functional. But more crucially, we need to ensure that our platform - the thousands of person-years of proprietary code that we license to customers - makes it incredibly easy to write real business applicat!ons in at their richness and complexity.

-end of brand-new material-

Switching Costs

In economics there is a well-understood concept called switching costs - how much it costs for a trading partner to change partners. Our philosophy on switching costs is very clear: we want low switching costs for customers who want to start using our platform, and we want to provide so much unique value that there are in effect high costs of deciding to move to a different platform. There is a name for this: it is called Embrace and Extend.

Embrace means we are compatible with what’s out there, so you can switch to our platform without a lot of obstacles and rework. You can switch from someone else’s Java compiler to ours; from someone else’s Web server to ours; etc. Customers love when we do this (as long as we don’t spend our energy embracing extra standards no one really cares about); our competitors are not so sure they like It because they prefer us to screw up.

Extend means we provide tremendous value that nobody else does, so (A) you really want to switch to our software, and (B) once you try our software you would never want to go back to some inferior junk from our competitors. Customers usually like when we do this, since by definition it’s only an extension if it adds value. Competitors hate when we do this, because by adding new value we make our products much harder to clone - this is the difference between innovation and just being a commodity like corn where suppliers compete on price alone. Nobody builds or sustains a business as successful as Microsoft by producing trivial products that are easy to clone - that would be a strategy for failure.

If we fail to embrace, we can lose because there are big barriers to buying our products. But if we Fail to extend, or do only humble work that is easy to clone or to surpass, we automatically lose because our competitors will spend literally billions of dollars to clone our work and replace us.

The Windows API

Windows was a very successful embrace-and-extend move. People already had DOS machines and DOS apps, and we were able to go in and say "add this to your machine and it wLll just get better.” Wow! What a deal! It seems to have worked out all right so far. NT is a very similar move; although It’s not trivial to upgrade from Win95 to NT. in general you can use the same computer, same apps. and same APIs as before, plus more.

The really big win in Windows is the API. An app that calls the Windows API is effectively calling upon thousands of person-years of engineering work to help their app get its job done in a very specific way. You could argue !hat the API is too hard to use, that not every library is as fast as it should be, or other serious imperfections, but the fact remains: if you took away Windows, that apphcation would no longer work.

The Windows API is so broad, so deep, and so functional that most ISVs would be crazy not to use it. And it is so deeply embedded in the source code of many Windows apps that there is a huge switching cast to using a different operating system Instead. You can't just take a Windows app and stick it on some weird Java NC from Oracle, for example, and expect it to work - the guts just are not there. For many customers, the cast of reworking all their apps would be huge.

TXAG 0008205 CONFIDENTIAL

MS-CCPMDL 000000292577 CONFIDENTIAL

It is this switching cost that has given customers the patience to stick with Windows through all our mistakes, our buggy drivers, our high TCO, our lack of a sexy vision at times, and many other difficulties. People have tried to clone Windows, but it is just too hard to do well. Customers constantly evaluate other desktop platforms, bit it would be so much work to move over that they hope we just improve Windows rather than force them to move.

In short, without this exclusive franchise called the Windows API, we would have been dead a long time ago.

The Java Platform

So along come Scott McNealy and Larry Ellison, saying “hey, we’ve got a good new programming language called Java.” Fine, we like programming languages a lot. After all we are a software development company. The problem is that very quickly they also said, “we’ve got a whole new platform, a whole new set of runtime libraries and APIs, to go with it - so as long as you are writing your apps in a new language, you might as well write to this new platform that we say lacks the flaws of old Windows.’ In other words, they are saying, switching costs will never be lower than they are right now - the barriers are low so join us now.

You would think it would be our top priority at such a time to (A) fix any serious flaws In Windows which could push customers over to the Java platform, (B) add so much new and unique value that this vaporous “Java platform” doesn’t sound very attractive anyway, and (C) make damned sure that our new value is really hard to copy so it doesn’t show up tomorrow in Sun’s or Oracle’s offerings.

We are doing all of this. We are fixing TCO and further improving our dev tools. We are providing new value such as Viper and great multimedia and unified storage. We are making sure that Windows, not some new platform, is the most attractive place to run apps written in this now programming language. We are building the best virtual machine in the world, and optimizing it to run on Windows. We are even making sure you can run your Windows apps remotely on an NT server if all you have on your desk is a GUI terminal. As if all this work were not already hard to copy, we are also getting a bunch of patents to further protect It against cloning.

Following the Java Parade

So It is with some amazement that I listen to a number of people who just don’t get it who think we should do work that actually makes it easier to copy our work and to run apps written for Windows on other platforms. That flies in the face of everything we are trying to do - it’s almost like a suicide attempt. The philosophy here seems to be “our competitors’ products are getting more press than ours, so we should kill ours and build copies of theirs instead.” This is foolish. Since when did we start believing our competitors’ press releases instead of rebutting them?

Let me be dear we have no problem with the Java language or with running Java apps really really well on our platform. But we are explicitly not in the business of making it easy for people to write apps that get all the features of Windows on a non-Windows platform. “Pure cross-platform portability” is another way of saying “commoditize the OS.” In this vision, every OS is just an engine for running this layer called Java as fast as possible, and adding any value below the Java layer Is explicitly against the rules.

Sun has already figured this out and has launched its 100% pure Java” marketing program, which literally certifies apps as running the same on any client OS. Programs that call a Windows API or use ActiveX or DirectX, or any platform-specific feature, are by definition not 100% Pure Java, and are therefore evil. Hey, If you were Sun, you would say this too!

Both Sun and Oracle make their money primarily on servers. (Sun still has some workstation market share, but NT is inevitably eating away at their share and their profit margins on the desktop.) So these companies have every incentive to turn the desktop platform (aka Microsoft’s main business) into a cost-driven commodity and focus all the high-margin business onto servers where they (especially Oracle) have a real fighting chance against us.

This is all the exact opposite of what we want to happen. It is critical to us that application writers choose to take advantage of features that are (A) part of Windows, end (B) extremely hard to clone. Therefore it

TXAG 0008206 CONFIDENTIAL

MS-CCPMDL 000000292578 CONFIDENTIAL

would be a huge mistake if we (A) spent all of our energy just embracing other companies’ innovations, or (B) asked key groups to do extra work that makes it that much easier to replace Windows, such as making Visual Basic apps run on the Java virtual machine.

We have enough people trying to kill us without us helping! It is our goal to make them lose while making ISVs and customers very happy by delivering great benefits.

Making Real Progress

With technologies like DCOM, Viper, and client-side persistent caching, we are just starting down the long road to the distributed world. There is a lot of design work to do, and a lot of intelligence to build into the OS and the network and the tools, And critically, each part has to be managed be the person or program who knows how to make the best decisions. Web site designers should not have to design their whole site around the latest statistics art who has what browser. End users sitting at desktop machines should need to do nothing - no Setup or anything else - to get computation to happen on local machines, just as they do nothing to enable the server apps or Web sites they connect to today. Business system designers should not all have to be experts on variable-speed wide-area networking. Library administrators should not care if a student brings in an app from home and wants to run it on a public kiosk machine for a while. Users with laptop machines should not have to know or care how the right things from the server magically get replicated to their local disk before they leave for a trip. An engineer who needs a big calculation done should not have to care which machine has spare CPU space, and an artist who needs to save 800MB of images should not have to manually hunt around for disk space. The list of “shoulds” goes on and on.

None of this is provided today by the Java platform, but one by one each of these features in being worked on by many people at MS and at our competitors, and each will get property implemented by someone. We have an opportunity to make many of these advances part of the Windows platform we get paid for, or part of the Java platform that is given away for free. As a shareholder, which do you want?

12

TXAG 0008207 CONFIDENTIAL

MS—CCPMDL 000000292579 CONFIDENTIAL



Credit: wallclimber

Comments

Recent Techrights' Posts

UEFI "Secure Boot Doesn’t Play Nice at the Moment"
UEFI "Secure Boot" does not improve security. It's an artificial obstacle in service of monopoly.
If You Want to "make your 'Windows PC' lean, mean, and fast" You Will Install GNU/Linux or Some BSD
That kind of article says a lot about IDG
"Bad Shim Signature"; So 'Secure' That It Overrides Users' Preferences and Turns Itself Back on (Coercive Measure)
This was a few hours ago
We Covered UEFI 'Secure Boot' Scandals. The World Listened.
To hell with UEFI 'secure boot'
 
Satya's Plan B: Try to Hide the Massive Extent/Scale/Scope of Microsoft Layoffs
fewer people buy Microsoft
Red Hat News About De Facto Mass Layoffs (Bluewashing) Gone From Reddit (Censored by Gatekeepers), Still Online in The Register
With RTOs, PIPs, relocation etc. expect IBM to "shed off" many Red Hatters
Gemini Links 14/09/2025: ROOPHLOCH, Music, and Reddit
Links for the day
Slopwatch: Google News Infested With Slop (About Half of the Results for "Linux" Today)
This is the sort of junk one finds when looking for "Linux" in Google News these days
Links 14/09/2025: Ricky Hatton Dies and McDonald's Declares War on Tipping Culture
Links for the day
Links 14/09/2025: Disasters for CEOs Obsessed With Slop and Slop Companies School Like Fish
Links for the day
"Bad Shim Signature" (Microsoft 'Secure' Boot)
"Fresh install not booting"
What Microsoft Garrett and Microsoft Lunduke Have in Common
Similar tactics, different "wings"
Links 14/09/2025: US "Economy Sagging", "Michigan Economy Wobbles From Tariffs"
Links for the day
Gemini Links 14/09/2025: Minimalist Snippet Manager and Omarchy Linux
Links for the day
The Face of the Digital Far Right: Microsoft Lunduke
Microsoft Lunduke is an online extremist that belongs to and panders to the far right
20 Years Later and Academia Isn't the Same
"I never dreamed of being a professor"
'Cancel Culture' by the Right: Microsoft Lunduke Contacts People's Employers Trying to Get Them Fired
Microsoft Lunduke panders to extremists online
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, September 13, 2025
IRC logs for Saturday, September 13, 2025
Microsoft is Rapidly Dropped From Web Servers, Shows Survey
Microsoft lost about 8% "market share" in just 3 months
Many GNU/Linux Users Report MOK (Machine Owner Key) Issues in Recent Days
many people don't report this online and never post in Reddit
Links 13/09/2025: Escalations in East Europe and POTUS’ Health Cover-Up
Links for the day
Gemini Links 13/09/2025: Lagrange Turns 5 and Lagrange 1.19.2 Released
Links for the day
Microsoft Inside Your Linux: "Security vulnerability that allowed an attacker to bypass UEFI Secure Boot."
2 hours ago
A New Low for "Linux Journal": Promoting MICROSOFT WINDOWS Using LLM Slop
They've just jumped the shark entirely
Fake News With Fake Numbers About Microsoft
"This is what happens when the world's economy is governed by sick old men"
Slopwatch: "Google News" is Fast Becoming a Mashup of Slopfarms, Linux Journal ("LJ") is a Dump of LLM Slop
Well done, Google News. Google itself can flourish as a slopfarm mashup.
Torturing Users Who Just Want to Run GNU/Linux on Their Own PC
"Linux does not want to install"
The Register MS Still Takes Money to Hype Up "AI" in Articles by Microsoft Resellers With the Term "AI" 30+ Times in Them
Notice how many times they mention "AI"
The Apache Logo News is VERY Old, Racists and 'Anti-Woke' Bigots Look for Something to Incite Other Bigots With
Nothing to see here, move along
Linux Mint 9/11: "4th One Today..." (in Reddit)
Remember that not everyone having an issue reports it to social control media like Reddit
Nepal Will Fall Without a Single Shot Fired, Thanks to Social Control Media
Or very few shots (by the authorities)
European Corruption in the European Patent Office (EPO) Targets Culture
"In reality, the project includes a new “legal instrument” shifting administrative burden and liability on EPO staff while creating new uncertainty and externalising Amicale activities."
European Authorities, Already Bribed and Infiltrated by Microsoft, Won't Help You Find BigBlueButton, Jami, Ring, and Jitsi
Because they're paid by Microsoft and are Microsoft 'addicts' themselves
UEFI Secure Boot Failing, as Expected for Nearly 15 Years Already (Techrights Said This Since 2012)
in the media
Debian 9/11
people report this issue
Gemini and Web Links 13/09/2025: MElon's Slop Grift and "Autonomous Trains"
Links for the day
Moving From Content Management Systems (CMSs) to Static Site Generators (SSGs) Saves You Time, Makes You a Lot More Productive
try to reduce the cost (financial and computational) of running your site
Pursuing Peace Through Violence
You cannot "see" a person's mind, until the mouth opens
Leak: European Patent Office (EPO) is Now Attacking Amicale Clubs
corruption has become the norm and scientists are robbed of any dignity
Can We Please Stop Celebrating Shooters?
"An important point to hammer on is that CoCs were never intended for uniform or symmetric application"
Oracle Fraud (or Defrauding Shareholders)
"the obvious [lie] is that watts are (wasted) electricity [and] and FLOPS are computing capacity"
Geminispace is Growing Faster in 2025 Than It Did in 2024
What matters is that corporations haven't ruined it and LLM slop is extremely rare
Links 13/09/2025: China Punishes for 'Negative' Posts, US Police Unable to Find Shooter
Links for the day
Who's the Mystery Financier of SLAPP Against Techrights and Is That a Millionaire/Billionaire?
Whose idea was it to fund meritless lawsuits against my wife and I?
Slopwatch: Slow Slop Day
This distracts from or may take traffic away from the original articles, actually written by actual people
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, September 12, 2025
IRC logs for Friday, September 12, 2025
CoC Gone Wrong: Celebrating Murder OK, Complaining About the Celebration Gets You Banned
Hopefully the NixOS Foundation will have a word with (maybe replace) the moderator/s
Gemini Links 12/09/2025: Familiarity and Secondary Dominants
Links for the day
Explaining (in Length and Depth) the Damage Matthew Garrett Did to Linux and to GNU/Linux Users
no matter how many threats we receive
Links 12/09/2025: "Bad Reviews" as Extortion Weapon, "Free Speech At Risk in America’s Schools" According to ACLU
Links for the day
Only One Speaker Does Not Do Sharecropping for MElon (in X.com)
The man who puts principles before PR/optics
The Mind of the 'Hulk Hogan of UEFI'
in a nutshell
A Day After "UEFI 9/11": UEFI Secure Boot Bypass
In the news today (right now), as published in the past few hours
Links 12/09/2025: Slop Code as Liability, Microsoft Outlook Down for Many
Links for the day
It's Still Not to Late to Turn Off "Secure Boot"
If people reboot their PC or server today, and it relies on "Secure Boot" on Sept. 12 or later, then depending on the firmware there may be trouble ahead
Links 12/09/2025: Shira Perlmutter is Back, “Software Per Se” Patent Rejections in In re McFadden
Links for the day
Slopwatch: Linux Plagiarism, Slopfarms Still Infesting Google News, Many Images Are Fake
Google is promoting plagiarism
"This Morning Might Turn Out to be an Interesting One for System Admins Who Haven't Updated Their Devices' Secure Boot Certificate" (If They Reboot)
Who asked for this anyway?
Gemini Links 12/09/2025: Metric System, Dumping Windows, and Software Architecture is Dead
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, September 11, 2025
IRC logs for Thursday, September 11, 2025