Honestly: By trying to control usage its not FOSS anymore and you yourself become a bad actor in the eyes if the FOSS idea. No soon to be unicorn can use any of your stuff.
May I add: You’d have to stop using VsCode or TypeScript, or even npm and Chrome, if you think big means bad, and you don’t want to fuel big corporations.
One can see how rediculous the whole idea of limiting FOSS in a “who can use this” way is.
Truly free will always win in the long way. Or you don’t think, a paid dev with some AI can replace your package fairly quickly?
I've learned quite a bit from the comments here, also got to see perspectives I wasn't focusing on. I've since then added a bit to the article about how one could be in favour of the deal. To be more transparent about changes, version history is coming to coffee.link.
The question I'm having is: Where exactly do inter.link and Google peer? Like either they are both at a public IXP (which would mean Google is not actually discontinuing peering, or you'd have to really define the "direct" in that quoted sentence), or one has a fiber cable to one of the others DC? How does that work? Any insights?
HeyHey. The website uses Ghost right now, and a lit based web components catalogue. Some features are not yet entirely carved out. The commenting system being one of them. Components are ready, but some integration work has to be done. We also want to enable highlighting stuff directly, so people can comment on specific referenced stuff...
The commenting APIs in ghost are a little obscure.
May I add: You’d have to stop using VsCode or TypeScript, or even npm and Chrome, if you think big means bad, and you don’t want to fuel big corporations.
One can see how rediculous the whole idea of limiting FOSS in a “who can use this” way is.
Truly free will always win in the long way. Or you don’t think, a paid dev with some AI can replace your package fairly quickly?