>>This is not about proprietary code (owning the code), anymore, but about owning the platform and making people use it. FOSS, early on created a whole bunch o

>>This is not about proprietary code (owning the code), anymore, but about owning the platform and making people use it. FOSS, early on created a whole bunch of concepts and ideology that was very useful for framing the issue. Back then, it did make sense to focus on open vs proprietary code license etc. That was a long time ago though, and most of what we know about the software industry wasn't known yet. These days we know software's best businesses are about control and power. OS can be used for strategic commodities, while convenient bottlenecks like app stores, cloud platforms or key dev tools. A lot casual assumptions got made about links between norms at GNU, linux, etc and what OS is. We need an update to OSS language. What does freedom, or openness mean today? As it stands, it's hard to say whether or not such and such violates such values, because the values are vague and unarticulated. We can fall back to 1980s FOSS, but that's somewhat dated.