• moonpiedumplings@programming.dev
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    20 hours ago

    Licenses like SSPLv1

    The SSPL requires that all software used to deploy SSPL software is open sourced. If I deploy my software on Windows, do I have to provide the source code for Windows? What about the proprietary hardware drivers, or Intel Management Engine?

    The SSPL is not the next generation of licenses, it is effectively unusable. And both Redis and Mongo, dual licensed their software as the SSPL, and a proprietary license — effectively making their entire software proprietary.

    make money without risk of a cloud vendor snapping up their software (think Redis, MongoDB, etc) need a place at the table.

    Except Redis, and Mongo were making money. They had well valued, well earning SAAS offerings — it’s just that the offerings integrated into existing cloud vendors would be more popular (because vendor lock in). They just wanted more money, and were hoping that by going proprietary, they could force customers away from the cloud offers to themselves, and massively increase their revenue… They did not get that.

    Another thing is that it’s not “stealing” Mongo/Redis’ when cloud vendors offer SAAS’s of Mongo/Redis. Mongo/Redis, and their SAAS offerings, are only possible because the same cloud vendors put more money than Mongo/Redis make yearly into Linux and other software that powers the SAAS offerings of Mongo/Redis, like Kubernetes. Without that software, Mongo/Redis wouldn’t have a SAAS offering at all.

    I definitely think that it’s bad when a piece of software doesn’t get any funding it needs to develop, especially when it powers much more modern software, like XZ. But Mongo/Redis weren’t suffering from a lack of funding at all. They’re just mad they had to share their toys, and tried to take them away. But it didn’t even matter in the end.