The economics for corporate controlled open source are quite clear. It's a cost saver for corporations to open source solutions to common problems. This gets others to buy in, which spreads maintenance costs and ensures that no one is seriously winning in the domain of the project. Essentially de-risking cost/benefits in the domain of the project.
Another problem, which the author didn't discuss, is that corporate controlled software is often designed by a committee, or designed by those with political capital within the corporation. There is not usually a strong selection mechanism for good system designers, or good open source leaders. Go is a happy and rare exception. Projects coming out of corporations are often not as well designed as projects which rose to prominence organically through differential amplification by the community.
We could have C# 30 years before we did if it weren't for microsoft.
His focus is TypeScript.
Mads Torgersen has been leading C# design since version 7, more or less.
Look at through a lens of scarcity. What Google sells that is 'scarce' is not the Go runtime - it's ads and other things.
But an independent open source project doesn't really have a source of 'scarcity' that it can sell.
https://journal.dedasys.com/2007/02/03/in-thrall-to-scarcity...
Of course, in an alternate timeline where the government successfully funds public/"open source" software, this post would be titled "Stop Building on Government-Controlled Languages".
Look at what happened to NSFNet and how it's no longer a network that's open but now a part of a large, billion/trillion dollar oligopoly with no obligation to serve anyone who won't make them a profit.
Freemium format. It floats the WordPress plugin ecosystem. That ecosystem has $1 bn size. Likely larger now since that statistic was made 1-2 years ago.
You give the base software and most if it free. You provide paid addons for niche, corporate, business use cases etc. Everyone is happy - the userbase gets their software free, advanced & business users have advanced features that could not have made it into the main software in addition to having paid support. And most important for everyone - the project & its organization can sustain itself and it can keep maintaining its software.
That's a more difficult case of course. But I believe enterprise support and custom enterprise features/addons could help in the case of languages.
> corporation controlling at least the proprietary components?
WP plugins are still GPL. But the users can buy, download them from the original source, install them on their site, and update them from their site with one click. Coupled with premium support, this works well. Its a bigger risk and hassle to 'pirate' the plugins from 3rd parties rather than just getting everything directly from the source. (though such 'piracy' does have impact).
In any case, one organization controlling at least the proprietary, custom enterprise components is much better than the alternative.
Look at tailwinds, open source lib with saas opportunities that netted the creator millions of dollars