Lunduke
News • Science & Tech
Wendin-DOS : The forgotten multi-tasking, multi-user DOS clone from the 1980s
Produced by a small team, and lost to the sands of time... until now.
August 18, 2023
post photo preview

Back in 1987, an MS-DOS compatible operating system debuted that — despite a truly impressive and fascinating feature set — has been all but lost to history: Wendin-DOS.

This wasn’t some simple DOS clone, either. Wendin-DOS was a multitasking, multi-user DOS with the ability to run individual applications in movable windows.

Yet, sadly, there is almost no information available on the history and development of this fascinating system.

Let’s remedy that.

I managed to track down the developer of Wendin-DOS, Steve Jones, to find out as much as I could about the history of the system.

The Wendin-DOS story begins, as so many stories do, with a young nerd… playing with computers in High School…

Steve Jones: “The moment I saw an ASR33 teletype, I knew what I wanted to do. In high school, I spent more time programming a Univac 70/7 (IBM 360 clone) than anything else. Studied the operating system, wrote a disassembler to reveal how it worked, and wrote a bunch of system-oriented software for it.

In college I got a job with the academic computer center and studied its operating system, as well as the up-and-coming VAX/VMS. I started learning about what Dave Cutler was doing and wished I could work with him.”

For those unaware: Dave Cutler is an absolute legend in the operating system world, having been one of the engineers responsible for VMS, and would later go on to lead the NT project at Microsoft.

Now that Steve was out of school, things started to get really interesting…

“After college, I started a software company in Spokane that operated in the same building as my parents' company, Jones Double-Reed Products. My brother Greg joined me, and together we cloned VAX/VMS (well, as well as we were able), added a PC API module (we called it "the Filter", which included INT 20h-2fh redirection and processing, as well as some other PC interrupts to achieve rerouting of BIOS calls.) We hired Scott, a local software engineer, to help us, and put him on the filter-- toughest job, since it was basically a compatibility layer for all the DOS stuff out there. I can't tell you how many times Word Perfect and Lotus 1-2-3 were causing him fits. Then we split it up, Greg took the VMS shell and utilities, and I took the kernel-- which was really just VAX/VMS, with 4 stacks per process, ASTs, QIO, RMS, the whole thing.”

Three engineers, in Spokane Washington, who built a VMS clone for x86 PCs.

Already quite cool… and then this little rag-tag team decided to do something even cooler… they built an “Operating System Toolbox”.

“We got the idea to just replace the shell and utilities to make other operating systems-- PCUNIX (later renamed to PCNX when AT&T sent us a letter), and finally, stripped them off to create Operating System Toolbox, which was just the source, in a toolkit that people could use to create their own shell and utilities around the kernel. We ended up selling about 400 copies of each of these things a month as I recall, in response to ads in Dr Dobbs, BYTE, Embedded Systems Programming and a few others.

An open source (before people really used the term regularly) kit for building a multitasking operating system. Plus a VMS clone and UNIX clone for IBM compatible PCs.

From the 1987 Wendin catalog

Think about that for a moment. It’s 1986. And there’s a UNIX clone, for IBM PCs, that (via the Operating System Toolbox) has some of the source code available for it. This was a full half decade before Linus Torvalds would start the Linux kernel project.

This is some mightily impressive stuff here.

PCUNIX advertisement. Dr. Dobbs Journal, July 1986.

This tiny little company now had two complete operating systems (plus the Operating System Toolbox). Which is where DOS enters the story…

“With so many people wanting an alternative to MS-DOS (one that was bootable from a disk, not runnable as a program from DOS)-- we did another round of development and created Wendin-DOS, 'the DOS of the future.'

 

We were able to demonstrate running real DOS apps in overlapping, character-oriented windows, as well as screen groups, ala the up-and-coming Microsoft OS/2.”

From the 1987 Wendin catalog

Wendin-DOS certainly seemed to generate a good amount of interest from the press back in 1987.

InfoWorld, November 1987

Of course, being a small company and supporting three different operating systems has some significant challenges. Namely: testing the system with a wide variety of software. The Wendin crew did a little outside the box thinking on that…

“Once we had the basic software going, we realized if we were going to compete with Microsoft, we would need testers. Since we didn't have the money for our own, we created a debugging contest, and each person got an "I Debugged The DOS Of The Future" mug, plus a large prize for the winners. The bug reports flooded in, but the winner was astounding-- he submitted a ream (500 pg) of paper, with each page containing a bug report describing the nature of the problem, how to reproduce it, a diagnosis of the problem and suggested fix; this thing was just off the charts great. Turned out, he was institutionalized in some way and couldn't really go get a job, so he had time on his hands.”

According to the July 1987 issue of “80 Micro” (a Tandy oriented magazine) the Wendin crew even traveled to the famous West Coast Computer Faire to demonstrate Wendin-DOS.

Updates to Wendin-DOS were worked on for a while after the first release shipped…

InfoWorld, May 1988

But, not long after Wendin-DOS hit the market, Steve Jones (and his brother) left the company and headed off to work at Microsoft. At which point Wendin-DOS (along with the Operating System Toolbox, PC/VMS, and PCUNIX) all quickly faded into obscurity.

Wendin-DOS advertisement in Dr. Dobb's Journal, August 1987.

What could Wendin-DOS (along with PC/VMS and PCUNIX) have become had they had a few more years to mature with the original team? We’ll never know… but, considering the amazing accomplishments from that small team (in such a short period of time)… my guess? It would have knocked our socks off.

Epilogue

Steve Jones would go on to eventually become the CTO for BIOS maker Phoenix Technologies. Along the way — immediately after stopping work on Wendin-DOS — he spent some time over at Microsoft working working for the very engineer that inspired him back in High School.

“I got to work for Dave Cutler and really feel like I apprenticed with him-- it was a fantastic experience, working for the MAN.”

And Dave Cutler wasn’t the only computer pioneer that Steve ended up rubbing shoulders with…

Funny little story-- as I roamed the Microsoft hallways in building 2 on my first day, I ran into Larry Osterman's office with his bulletin board outside. On that bulletin board was posted our Wendin "love letter", which was something we sent out because we were delaying shipment of Wendin-DOS while we were processing all those bugs. On the form letter, Larry had written, "Guess writing a DOS is harder than you thought!" Not surprising, since Larry wrote DOS 4, the multitasking version of MS-DOS that never really went anywhere but was pretty ambitious at the time. We were largely solving the same problems, though he had full MS-DOS 3.31 source code (a great version of DOS) and we had our debugger to work with. Larry and I had a good laugh about it. Tim Paterson, the original 86-DOS implementer, had an office across the hall.”

Editors note: I had the good pleasure of interacting with Tim Paterson back in the 1990s, when we both worked at Microsoft. I was a young nerd, he was the software legend responsible for building the original “Quick and Dirty Operating System” that would go on to become “MS-DOS”. He was incredibly kind and gracious.

Many thanks to Steve for writing up some of this history and sharing his thoughts. It is so important that this amazing — and fascinating — part of computer history be properly documented. While there is still much to record about the work of this team, this is a good start.

Nowadays, Steve Jones runs NeuroSynthetica in Seattle, WA.

Can I run Wendin-DOS in 2022?

You can, indeed, run Wendin-DOS in emulation on modern machines. I was able to boot version 2.11 inside VirtualBox:

Wendin-DOS 2.11 booting off a floppy

Note: Wendin DOS 2.11 can be found in a few corners of the Internet. Due to uncertain legal status of the software, I can't link to it directly.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
7
What else you may like…
Videos
Podcasts
Posts
Articles
Open Source AI Definition: Not Open, Built by DEI, Funded by Big Tech

Run by an "Anti-Racist, Decolonizing" Activist, the new Open Source Definition is anything but Open.

The article:
https://lunduke.locals.com/post/5917220/open-source-ai-definition-not-open-built-by-dei-funded-by-big-tech

More from The Lunduke Journal:
https://lunduke.com/

00:18:35
GNOME bans Manjaro Core Team Member for uttering "Lunduke"

The GNOME team has censored -- and deleted the account -- of the maintainer of Manjaro Linux GNOME Edition. Why? Because he linked to a Lunduke article.

GNOME bans Manjaro Core Team Member for uttering "Lunduke":
https://lunduke.locals.com/post/5908516/gnome-bans-manjaro-core-team-member-for-uttering-lunduke

More from The Lunduke Journal:
https://lunduke.com/

00:17:16
GNOME Ousts Elected Board Member in Secret, Tells Nobody for 2 Months

Secret meetings. No transparency. Total chaos at the GNOME Foundation as they remove Sonny Piers, one of their Board Members, without telling anyone. This all happens right as the GNOME Executive Director quits, GNOME announces dire financial circumstances, and a disastrous "5 year plan" focusing on DEI.

The article:
https://lunduke.locals.com/post/5899324/gnome-ousts-elected-board-member-in-secret-and-tells-nobody-for-2-months

More from The Lunduke Journal:
https://lunduke.com/

00:37:30
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Heads up:

The Lunduke Computer Operating System forum is getting some structure... and, for those of you looking to get involved, posts are starting to go up discussing specific areas available for contribution.

https://lcosforum.lunduke.com/

I installed Llama 3.1 8B locally on my $600 windows 11 machine (Ryzen 7 mobile processor, 8 cores, 64gig ram, integrated gpu). Not exactly a high performance genai machine.

Initial impression? Pretty nice. Quick enough - but not nearly as quick as ChatGPT.

I told it about Lunduke and OSNews and asked for a Haiku:

Truth stands strong against hate
Lunduke's voice echoes love loud
Light shines in the dark

With some more prompting we arrived at:

Bytes of love prevail
Osnews' hate crashes to zero
Lunduke's code saves

Not bad. I gave it one of my blog posts to review, and it did a solid job. Then we discussed diabetes and such. Even this 8B version, is nice.

The 70B version will probably run on my machine.

Looking forward to someone taking off the censorship. A model this good, uncensored, running locally? Game changer.

"source" (Linux Command) 👨‍🏫 I know it from a "User Level Red Hat" Course that I took in Community College (Tech School).

post photo preview
Editor of OSNews calls for the murder of a Conservative, Jewish Tech Journalist
Leftist Extremist OSNews says Lunduke is "Nazi" who must "die".

The Editor of OSNews.com has declared that I, Lunduke, am a member of the Nazi party -- and encourages others to murder me.

I repeat: A Tech Journalist has stated -- as a matter of fact -- that a proud Jewish man is a Nazi that must be killed.

Absolutely insane.

On Friday, July 26th, the Editor of OSNews.com (Thom Holwerda), posted the following to his Mastodon account:

"Hey linuxrocks.online, you have a nazi infestation. Considering your instance seems to use only approved registrations, this surely raises about a million red flags."

 

Source: Mastodon

 

What was the "Nazi infestation" he speaks of?  He includes a screenshot of The Lunduke Journal account to make it clear who he was refering to.

While this is already absolutely insane (no sane person would call a proud Jewish man a member of the Nazi party)... it gets far, far worse.

A few hours later, the OSNews.com Editor followed up with the following statement:

"Since the instance linuxrocks.online is openly, knowingly, and willingly hosting nazis, I'm going to block the whole instance. If you're a follower on said nazi instance, I suggest you reconsider your choice of instance.

 

No quarter for nazis. The only good nazi is a dead nazi."

 

Source: Mastodon

 

"No quarter for nazis. The only good nazi is a dead nazi."

Am I a Nazi?  Obviously not.  But, that Tech Journalist says that I am a Nazi.  And I must be killed.

Which means, according to the Editor of OSNews, "The only good [Lunduke] is a dead [Lunduke]."

Is it libel?  Without question.  Is this a clear threat of violence?  Absolutely.

He also appears to be stating that anyone who simply exists on the same server as me is, by proximity, also a Nazi.  And they must also be murdered.

Few Will Condemn This

I wish I could say this was a completely isolated incident.

The sad fact is, a number of Tech Journalists share the extreme, Leftist, disturbed, violent views of the Editor of OSNews.  They believe that many groups (including both Conservatives and Jews) are evil "Nazis" who must be murdered.

And, while many other Tech Journalists do not agree with those warped, twisted ideas... few, if any, will speak out against those calls for violence and death.

All Hope Is Not Lost

In those vile messages quoted above, the Editor of OSNews was clearly attempting to bully the administrator of a specific server -- whose only crime was allowing me to exist.

How did that server's administrator respond?  In an incredibly reasonable way:

"We do not appreciate name-calling here. Would you like to present your evidence that a user needs to be removed rather than going straight to name-calling."

 

Source: Mastodon

 

No name-calling.  Present evidence if you have a concern.

Reasonable.  Calm.  Practical.

Seeing that sort of response gave me just a little extra hope for the future of the Open Source and general computer industries.  If we can get more brave, reasonable, thoughtful people -- like that server administrator -- speaking against the hate and violence of people like the Editor of OSNews... we might just stand a chance.

(Of course, no response given -- by the OSNews Editor -- to this reasonable request.)

A Related Thought From Lunduke

Let's pause, and take a step back.  I'd like to talk, for just a moment, about politically charged discussions (like this one) within the broader Tech World... and on The Lunduke Journal specifically.

When I first started The Lunduke Journal, I focused entirely on the technical aspects of computing.  "Stay clear of politics, Lunduke," I told myself.  "Stick to the happy tech stuff!"

And, by and large, I managed to stay true to that for many years (with no more than a passing, momentary blip into politically charged topics once in a blue moon).

But, here we stand.

At a time when people are being banned from Open Source projects solely because of their political leanings (often leading to the complete destruction of those projects).  When entire Open Source organizations and concepts are being re-shaped -- into something not-at-all "Open" -- by political activists.  When Big Tech corporations are regularly discriminating against people based on the color of their skin or their sex.

And when, like we saw today, a Tech Journalist declares that Conservative Jewish Nerds (and the people who exist near them) are "Nazis" who need to be murdered.

Staying quiet on these issues is simply not an option.

Not for The Lunduke Journal.  And not for any other Tech Journalist worth a damn.

It is well past time to speak out against this insanity.  If you are a Tech Journalist (in whatever form... articles, podcasts, videos), shine a light on these stories.  Show people the damage that is being done to the world of computing by these political extremists.

The Lunduke Journal can't do this all alone.  But if I have to do it on my own... I will.

Because I love computing.  I love the history of it, the technical aspects, the future... all of it.  And computing is worth saving.

So, I will keep covering all of it.  Even if these extremists keep threatening to kill me.

Read full Article
post photo preview
Funny Programming Pictures Part XLIX
Mogwai & Michael J Fox Edition

Not all of these pictures are about programming and computers.  Some are about Mogwai and Michael J Fox.   Just felt right.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Read full Article
post photo preview
Open Source AI Definition: Not Open, Built by DEI, Funded by Big Tech
Run by an "Anti-Racist, Decolonizing" Activist, the new Open Source Definition is anything but Open

The Open Source Initiative is preparing to finalize what they call "The Open Source Aritificial Intelligence Definition" -- a set of rules which A.I. systems must adhere to in order to be considered, officially, "Open Source".

And everything about it is truly peculiar.

From the fact that it considers "No Data" to be "Open Data" (yeah, try to wrap your brain around that little nugget) to the corporate sponsorship (from corporations in the "Closed Source A.I." business)... to the "anti-racist, decolonizing" consultant they hired to put the whole thing together.

Yeah.  "Decolonizing".  The whole thing is just plain weird.

A Little Background

The Open Source Initiative's cliam to fame is that they are the steward of what is known as the "Open Source Definition" (aka "the OSD").  A set of rules which any software license must adhere to in order to be considred, officially, "Open Source".

The "OSD" began life back in 1997 as the "Debian Free Software Guidelines", written by Bruce Perens.  Later, with the help of Eric Raymond, that document morphed into the "Open Source Definition"... at which point the two men created the "Open Source Initiative" to act as a certification body for the OSD.

Fun Historical Tidbit: The Open Source Initiative likes to tell a long-debunked story about the creation of the term "Open Source" which they know is historically incorrect.  That little tidbit isn't critical to what we're talking about today... but it's just plain weird, right?

Flash forward to today, and both of the founders -- Perens and Raymond -- have been forced out or banned from the Open Source Initiative entirely.  Now the organization, free from the influence of the founders, is looking to expand into the newly exciting field of "Artificial Intelligence".

Thus: The creation of "The Open Source A.I. Definition"... or the OSAID.

The Anti-Racist Leadership

To create this new "OSAID", the Open Source Initiative hired Mer Joyce from the consulting agency known as "Do Big Good".

 

Mer Joyce: Process Facilitator for the Open Source AI Definition

 

Why, specifically, was Mer Joyce hired to lead the effort to create a brand new "Open Source" definition, specifically focused on Artificial Intelligence?

  • Was it her extensive background in Open Source?
  • Or her expertise in A.I. related topics?
  • Perhaps it was simply her many years of work in software, in general?

Nope.  It was none of those things.  Because, in fact, Mer Joyce appears to have approximately zero experience in any of those areas.

In fact, the stated reason that Mer Joyce was chosen to create this Open Source definition is, and I quote:

 

"[Mer Joyce] has worked for over a decade at the intersection of research, policy, innovation and social change."

 

Her work experience appears to be mostly focused on Leftist political activism and working on Democrat political campaigns.

As for the consulting agancy, Do Big Good, their focus appears to be equally... non-technical.  With a focus on "creating an equitable and sustainable world" and "inclusion".

 

The "Values" of "Do Big Good".

 

When "Do Big Good" talks about what skils and expertise they bring to a project, they mention things such as:

  • Center marginalized and excluded voices.
  • Embody anti-racist, feminist, and decolonizing values.
  • Practice Cultural humility.

 

How "Do Big Good" works.

 

Note: Yes.  They wrote "decolonalizing".  Which is not a real word.  We're going to give them the benefit of the doubt and assume they meant "decolonizing".  Spelling errors happen.

Now, how does "Embodying decolonizing values" help to draft a definition of Open Source Artificial Intelligence licensing?

No clue.  But, apparently, "decolonizing" and being "anti-racist" is important to the Open Source Definition and software licensing.

You'll note that the only software-related skill this "Do Big Good" company appears to have is that they can "work virtually or in-person".  In other words: They know how to use Zoom.

In fact, this consulting firm only gives three examples of client projects they've worked on.  And the other two are non-technical policy documents for the government of Washington State.

 

The other work of "Do Big Good".

 

Why this agency, and this individual, was hired to lead the work on the OSAID is beyond baffling.  Just the same, this appears to be part of a larger pattern within Open Source and Big Tech: Hiring non-technical, political activist types to lead highly technical projects.  It doesn't usually go well.

The Diverse Working Groups

Considering that the leadership hired to oversee the OSAID's creation is extremely non-technical --  and almost 100% focused on "anti-racist" and "decolonizing" activism -- it's no surprise that one of the first steps taken was to create "working groups" based entirely on skin color and gender identity.

 

"The next step was the formation of four working groups to initially analyze four different AI systems and their components. To achieve better representation, special attention was given to diversity, equity and inclusion. Over 50% of the working group participants are people of color, 30% are black, 75% were born outside the US, and 25% are women, trans or nonbinary."

 

What does having "25% of the people being Trans or nonbinary" have to do with creating a rule-set for software licensing?

Your guess is as good as mine.

But, from the very start of the OSAID's drafting, the focus was not on "creating the best Open Source AI Definition possible"... it was on, and I quote, "diversity, equity and inclusion".

The best and brightest?  Not important.  Meritocracy?  Thrown out the window.

Implement highly racist "skin color quotas" in the name of "DEI"?  You bet!  Lots of that!

"No Data" = "Open Data"

With that in mind, perhaps it is no surprise that the OSAID is turning out... rather bizarre.

Case in point: The OSAID declares that the complete absence of the data used to train an A.I. system... does, in fact, qualify as "Open".  No data... is considered... open data.

If that sounds a bit weird to you, you're not alone.

Let's back up for a moment to give a higher level understanding of the components of an A.I. system:

  1. The Source Code
  2. The Training Data
  3. The Model Parameters

If you have access to all three of those items, you can re-create an A.I. system.

Now, we already have the OSD (the Open Source Definition) which covers the source code part.  Which means the whole purpose of having the OSAID (the Open Source AI Definition) is to cover the other two components: The Training Data and the Model Parameters.

Without an exact copy of the Training Data used in an A.I. system, it becomes impossible to re-create that A.I. system.  It's simply how the current generation of A.I. works.

However, the OSAID does not require that the Training Data be made available at all.  The definition simply requires that:

 

"Sufficiently detailed information about the data used to train the system, so that a skilled person can recreate a substantially equivalent system using the same or similar data."

 

At first that sounds pretty reasonable... until you really think about what it means.

This means that an A.I. system would be considered "Open Source A.I." even if it provided zero data used to train it -- it simply must be possible for someone to use the closed, proprietary data... if they should happen to obtain it.

That's like saying "My software is open source.  But I'm not going to let you have the source code.  But, if you did get the source code -- like through espionage or something -- you'd be able to use it.  Which means it's open source.  But you can't distribute or modify that source.  Because it's mine."

Now, an argument could be made that the source code for an AI system could be open even if the data is all closed... and, therefor, it would be "Open Source" under the old OSD.  Which is absolutely true.  But, in that case, why have an "OSAID" at all?  Why not simply keep the existing OSD and focus on that?

Well... I think we have a simple answer to why this OSAID is so utterly strange...

The Corporate Sponsors

The Open Source Initiative is not a huge foundation, especially when compared to some.  But it's revenue is not insignificant.  And it's growing.

In 2023, the Open Source Initiative brought in a revenue of $786,000 -- up roughly $200,000 from the year prior.

 

Source: Open Source Initaitive 2023 Annual Report

 

And who sponsors the Open Source Initiative?

Google.  Amazon.  Meta.  Microsoft (and GitHub).  Red Hat.  And many other corporations. 

 

A Sampling of the Open Source Initiative Sponsors.

 

 

Many of these companies have some noteworthy things in common:

  • They are in the A.I. business in some way.
  • They make use of "Open Source" in their A.I. products.
  • They use "Open Source" as a promotional and public relations tool.
  • They, in one way or another, work with a closed, proprietary set of A.I. training data.
  • They have significant "Diversity, Equity, and Inclusion" efforts.

When you add that all together, this "Open Source AI Definition" begins to make a lot more sense.

It is, in short:

An effort to create a "Certification" which will declare all of their A.I. systems (no matter how closed their data is) as "Open Source"... while simultaneously being run by a DEI activist organization with a focus on racial and gender identity quotas.

It checks a whole lot of check boxes.  All at once.

What Impact Will This Have?

While many may argue that this "OSAID" is simply irrelevant -- and can be ignored by the broader "Free and Open Source Software" industry -- that misses a key impact that is worth noting.

That being: The continued corruption of both the ideas and the organizations of Open Source.

Not only has the Open Source Initiative banned their founding members (and re-written their own history)... they are now seeking to create a new "Open Source Definition" which will allow for systems consisting primarily of closed, proprietary data to be considered "Open Source".  Thus making their Big Tech financiers happy.

The meaning of the term "Open Source" is being actively modified to mean "A little open, and a lot closed".  And many of the same corproations which are funding this effort are also funding things like... The Linux Foundation.

Which means this corruption and dilution of the concept of "Open Source" is likely to spread far beyond the reaches of one, small (but growing) licensing certification foundation.

Also, apparently, decolonizing values... or something.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals