Immediately after switching the page, it will work with CSR.
Please reload your browser to see how it works.
They also bash the Commons Clause purely using the definition (zero mention on why they think the restrictions are bad, it's just handled with "not OSI" and that's it)
Of course this position can be understood better when you look at who are sponsoring this organisation. (in a short way, opensource.net is an OSI front, and OSI is lobbied heavily by the software industry)
Single-vendor open source is the balance some companies have found between sharing their software with the community and capturing the value of their employees' labor. It's less free than openly developed FOSS and more free than proprietary software. It's unrealistic to expect all software to be openly developed FOSS with today's economics; the hundreds of thousands of contributors to single-vendor open source projects all need rent money, and you can't build a business on providing the open-source backend for AWS managed services.
Companies will move up and down the freedom gradient depending on their needs at any given time. Sometimes they do it well, and sometimes they handle it in a kludgy and myopic way (I'm looking at you, HashiCorp). LinkedIn open-sourced Kafka, and Elastic restricted their license for ElasticSearch. Software doesn't always go from "more free" to "less free."
I think that having a for-profit company controlling an open source project is a major conflict of interest. Open source does not always result in profit. Often the opposite. And I think we've seen the results of that with all the different open source projects that have re-licensed into pretend open source licenses.
There are ways to run open source projects that support both the open source culture, and allow for for-profit companies to make a profit. But most of those ways mean allowing competition. Which is where the single vendor project conflict of interest becomes apparent. Yeah, big tech will leech off any successful project. Yes, that means less money for the "single vendor". Yes, that is not fair. But I'd say re-licensing is worse than leeching, so...
The other side effect of "single vendor" I've run into a lot, is simply that their paid options are always priced for organizations with very deep pockets. So the smaller orgs (and individual developers) that jumped on the bandwagon early because the project was open source (and they actually could jump on the bandwagon), have no chance at supporting the project. And end up have to find something else because the project stops supporting open source.
This brings to mind two questions: why does open source need to "win" (why can't there be multiple options) and re: things being produced as their exclusive property, what is the issue with this? They did the work to make the thing, therefore it's their property (unless they choose to release it otherwise).
Sadly, a lot of the arguments I hear around OSS sound like the "you didn't build those roads" argument when they should be "thank you for making your work accessible to me." It's no surprise that most OSS work gets abandoned due to developer burnout when "open source" is often misinterpreted as "100% free for me to do literally anything I want, whenever I want, and you're evil if you disagree with my entitlement to your efforts."
The ideology around OSS has serious NPD vibes. It's worth people revisiting Rich Hickey's "Open Source is Not About You" [1].
[1] https://gist.github.com/richhickey/1563cddea1002958f96e7ba95...
I suspect that's not the message they intended to send.
(I read the article, btw.)
As the author of source available software, this article merely seems to be screeching from big players that they can't exploit some software anymore.