top | item 42456226

(no title)

jjirsa | 1 year ago

> I would say it's opposite. No one contributes to open source and the developers have to make money on the side to work on the project

You missed the important part of his sentence:

> All those open source copycat projects, using open source to get exposure then switching

The original open source here was Cassandra. Scylla exists to pick off that market share. They launch with a free license, pull customers, then swap license. The actual adoption of Scylla would have been a fraction had it been released under this license to start, which everyone understands.

> Or more often companies with money come to fork an open source project from the developer, and continue pretending it's their own now

It had already been AGPL, so it's not like they're protecting against competition. They already had a license that avoided the forking problem. This isn't protection against AWS (keyspaces likely has more OSS cassandra code in the protocol tier than it has Scylla code, if it has either). It's protection against free consumption.

discuss

order

splix|1 year ago

Copycat is a bit of a stretch here imho, considering it's in different language, and even the general architecture. But I agree they are very compatible on the protocol level, which they used as an advantage as people don't need to rewrite their code when they migrate.

jjirsa|1 year ago

> Copycat is a bit of a stretch here imho, considering it's in different language, and even the general architecture. But I agree they are very compatible on the protocol level, which they used as an advantage as people don't need to rewrite their code when they migrate

It's not a stretch. They literally copied the java code and re-implemented it class-by-class with Seastar/c++.

It's literally in the ORIGIN file in their repo: https://github.com/scylladb/scylladb/blob/dc375b8cd3e8c7e85d...