301–310 of 578 posts
Earlier quoted context omitted.
It is absolutely FUD. https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html
On the one hand you have a large department of battle-hardened IP lawyers who say that AGPL virality is overbroad and poorly defined, and on the other hand you have a FOSS advocate who says it's fine, so I guess we'll never know for sure!
I applaud this decision. I would like to see all major SaaSS projects be AGPLv3. End users still have freedom to user, modify, and distribute the software. Cloud providers must share contributions. This is how I like it.
That sounds nice in theory, but the reality is also that a lot of more permissively licensed (BSD / Apache) projects now cannot use (most) parts of Grafana / Loki / Tempo anymore, since realistically they won't be able to or want to switch to the AGPL as well (because of all the pain that would incur on others, in turn). That means that basically the whole free code sharing idea goes out of the window, at least in on…
Earlier quoted context omitted.
It doesn't adequately handle the SaaSification case, which is when someone hosts the software behind a paywall. It only handles the "Tivoization" case when someone ships the software inside a closed source box.
Are you sure? AGPL was written expressly to deal with SaaSification. Wikipedia seems to agree with me, at least[0]: "Both versions of the Affero GPL were designed to close a perceived application service provider (ASP) loophole in the ordinary GPL, where, by using but not distributing the software, the copyleft provisions are not triggered. Each version differs from the version of the GNU GPL on which it is based in…
Earlier quoted context omitted.
SQLite, Vim/Emacs, Linux, everything in GNU coreutils. All of the Apache projects (some to more/less an extant than others). Most programming language implementations (e.g. CPython). Memcached. WireGuard. SQLAlchemy. Web Frameworks like Flask, Django, Rails, on and on. There are many open source technologies that do not seek to capture the value they create with licensing hijinks. I don’t think it’s an accident, that…
I did not mean to say that open-source software (broadly, MIT-licensed) and free software (broadly, GPL-licensed) don't do well! They do, and I'm happy about it. Some have commercial entities around them, but most don't. What I was trying to say is that FOSS was never about capturing commercial value, and always about capturing the value of the freedom to inspect, share, and tweak. In this regard, going AGPL is prefe…
Sorry, but free software IS open-source software. I take issue with how you're presenting these. Perhaps a better term would be liberally licensed software, as opposed to copyleft.
Earlier quoted context omitted.
SQLite, Vim/Emacs, Linux, everything in GNU coreutils. All of the Apache projects (some to more/less an extant than others). Most programming language implementations (e.g. CPython). Memcached. WireGuard. SQLAlchemy. Web Frameworks like Flask, Django, Rails, on and on. There are many open source technologies that do not seek to capture the value they create with licensing hijinks. I don’t think it’s an accident, that…
> From your example, K8s will definitely outlive Google. Hard to say about Android. What leads you to say that? I wouldn't be surprised if kubernetes is dead in 20 years. I would be very surprised if google is dead in 20 years.
But I don’t think there’s a significantly-simpler, mature abstraction for doing container orchestration, than K8s.
K8s’ main advantage/stickiness factor, is how abstract and modular it is. It’s an opinionated Kernel that gets most things right and has a huge ecosystem of tools built around this kernel.
It has a very similar set of stickiness factors to Linux, imo, although the origin story couldn’t be more different of course.
I think if anything replaces K8s, it’ll take a Linux-like shape. But K8s gets enough things correct (licensing, api, modularity) that it’ll be hard to replace it wholesale.
Loki: Web Analytics Dashboard for NGINX
Tempo: An open source, easy-to-use and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. Tempo can be used with any of the open source tracing protocols, including Jaeger, Zipkin, and OpenTelemetry.
Earlier quoted context omitted.
>I can no longer use Grafana unless I also publish my SaaS under AGPLv3, right? If you link to it directly from your code then yes, unless you're willing to pay Grafana for a commercial license (assuming they offer one or you can negotiate one with them). If you have Grafana running on your servers but you aren't using the code in your own applications then you're generally fine (the GPL is generally recognized as en…
That was also my understanding of the GPL, but the AGPL is for me to understand.
More specifically, the only difference between GPL and AGPL is section 13 (and the preamble summary). The rest of the license is word-for-word identical (save for the name). https://www.gnu.org/licenses/agpl-3.0.en.html#section13
When we released our server product under GNU AGPL v3 license, we have received a rather negative reaction from other participants in our field. The general sentiment was, "this license makes a useless curiosity". I wonder where does this hostility come from. Jealosy? FUD? Frustration that they can't take the source and not share own improvements??
Earlier quoted context omitted.
> But I do note that your examples are from quite a narrow sector. TypeScript, Go and React are all languages. TypeScript is a nice facade over JavaScript, and React is ... well, a very powerful DSL.[ß] > ß: Our frontend team will probably want to roast me for that one, but there isn't much visible JS left in modern React code. Not for my eyes, at least. Can you clarify what you're talking about here with regards to…
> but React is a language now? In a way, it is. Whenever you write some module in your project, you're effectively designing a language. Every function you add is a new verb, every type you define is a new noun[0] - and the relationships between them form the grammar. It may sound trivial, but I think it's an important and underappreciated point. Modularizing and abstracting is done by building languages on top of ot…
Earlier quoted context omitted.
Also, the CNCF is essentially Google by another name.
that for sure is false... Google helped start CNCF but now plays a small part in its governance, they are just one board member like the 30+ others... they have no special voting rights... https://www.cncf.io/people/governing-board/ they still do quite a lot of heavy lifting though in contributing to a variety of CNCF projects if you look at the numbers: https://all.devstats.cncf.io/d/5/companies-table?orgId=1