Earlier quoted context omitted.
This is not true even in those spaces anymore. Games these days require libraries like SDL, or (increasingly) use engines like Godot. Defense is a weird place, but open source is used quite a lot there, it's often required to do so and to record the open source consumed to produce a product. And often times, it must be commercial open source where you can get engineering support for the lifetime of the product's exis…
Not at all, when talking about game consoles.
CockroachDB license change
441–450 of 476 posts
Re: CockroachDB license change
#442Re: CockroachDB license change
#443Earlier quoted context omitted.
> AGPL requires you only to provide the source code of your fork to its users The AGPLv3 is exactly the same as the GPLv3, except with the added clause that connecting to a server counts as distribution for the purposes of triggering the right to obtain source code. That means all the usual GPL copyleft rules apply: if you include an AGPL library in your server binary, the entire binary becomes subject to the AGPL. A…
Ah but what if you bundle both your application binary and some (unmodified) AGPL software into a single Docker container? Do you then need to provide source code for your entire application?
Re: CockroachDB license change
#444Yup - another "Contact Us" for pricing. God forbid if your business grows more than 10 Million ARR and now you owe them undisclosed amount of money.
At this point I'm convinced "Contact Us" is worse for business/sales than just disclosing any outrageous fees upfront
Re: CockroachDB license change
#445Earlier quoted context omitted.
Well what do you expect to maintain the mouse’s cloud servers, if not subscription revenue? The greed here!
if the server was integral to the running of the service then yes, it makes sense to discontinue it when there's no more profit to be made. However, increasingly more and more services which could've been an on-premises deployment become SAAS. This includes games (live services they call it). It is _designed_ to end, and designed to not be able to run locally. Tell me who's the greedy one.
- Prevent piracy
- Extract more money per user (subscriptions, repeated purchases in-game)
Look, you can live perfectly fine without all of those services, there are indie games and there are old games and, according to some, they're much better than any online crapware from today.
Make it a point not to buy Free to play online crap, forbid your kids from playing that crap. Absolutely don't give them any money for this crap.
If enough people stop buying the we'll see a shift to the DRM & no hassle approach of indie games. I'd also prefer giving my money to a small team of devs than some corporate ladder who happend to purchase the latest AAA game built by a studio of overworked and underpaid devs.
Re: CockroachDB license change
#446That's another company that feels like they don't want to be an OSS company after all. After Elastic, I pay more attention to contributor agreements. Basically I consider any project that requires transfer of copyright for OSS contributions as likely to change their license at some point. It's fine; I'm not against that sort of thing and I sometimes pay for software. But I like to know what I'm getting into before an…
CockroachDB hasn't been an open source project in more than 5 years. They took down the blog post (I'd be curious to know why), but here is the announcement: https://web.archive.org/web/20190604173131/https://www.cockr... What started as a neat project with a vibrant and enthusiastic community is now just another dull beige enterprise vendor.
Re: CockroachDB license change
#447Earlier quoted context omitted.
Ah but what if you bundle both your application binary and some (unmodified) AGPL software into a single Docker container? Do you then need to provide source code for your entire application?
That's the kind of question that only really gets answered when a judge rules on it. The pertinent question here is roughly whether the combined docker image constitutes a "derived work" of the AGPL software
Re: CockroachDB license change
#448Earlier quoted context omitted.
At large? As you can see, there is room for a community with a different view on that. My personal definition of an "open source license" is that, as the name implies, I can access the code, preferably without much gatekeeping (e.g., creating a free account in a private GitLab instance). And, to be honest, I prefer the BSL with an Additional Use Grant over any other license, because this is the most reliable option t…
You are welcome to choose that, but in my opinion, it isn't open source. I think open source should means anyone can contribute or take, and contributions are shared, without undue discrimination. Nobody is forced to work on the project, but if they are then they have to give the results of their work back to the common pool they took from. You have just as much power to keep the project going as anyone else does, in…
Well, here we go. Your "open" isn't so open in the end.
Re: CockroachDB license change
#449Earlier quoted context omitted.
But if I could just go to Amazon directly,presumably they'd offer support, how do I give you money. I just don't understand how for-profit company can develop true open source software. You can have a non profit foundation and a for profit support studio. Godot effectively does this. Plus if you've taken VC money you can always get voted out in a few years. Or just have a nice exit. I wouldn't be mad at anyone for ta…
If you go to Amazon directly, this is great - you continue using our products and recommending them to your friends. Probably, next time you'll become our customer. For example, if you aren't satisfied with the support from Amazon, or there are some missing features at Amazon, or if you just switch department or company. We develop open source products, we are profitable and we have good revenue growth rate. We make…
If I ever have a need for a metrics solution I'll consider your products.
Re: CockroachDB license change
#450Earlier quoted context omitted.
It's a lot more moving parts unfortunately and the TiDB team has historically little interest in fixing that.
TiDB CTO here, I think that a clear boundary between components is beneficial for the maintainability of a distributed systems like TiDB, and automated deployment tools like `tiup`( https://tiup.io ) and the Operator of Kubernetes shield end-users from this complexity in order to maintain best practices in deployment. While still providing enough debugging details for advanced users.
Having different parts written in different languages is awful too, because it brings some micro improvements (if any) but makes project look complex and scary for many new-comers :(