• 3 Posts
  • 70 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle
  • Hmm, well the first round(s) are doable for beginners. If you want to get into programming, these kinda games are a good way to start, since you’re getting visual feedback of what your bot is actually doing.

    And you can participate in loads of languages, so you can pick anything that you’re somewhat familiar with.

    However, once you’re getting into higher rounds, ranks, and leagues, you’ll be playing against other peoples’ bots. So obviously if you have 0 experience it’ll be way harder to beat people with loads of experience, that understand which algorithms are suitable etc.

    But I’d say go ahead and try it out. Its free. Maybe it turns out to be too difficult, maybe you’ll manage.




  • It’s not a big red flag, but it indicates that the product is not fully open source. You can get the full community edition from Github, but for the Self-hosted Enterprise version you have to contact sales.

    So all the Enterprise features are most likely closed source, and when you buy/license it, you’ll just get the compiled version. And since their Cloud hosting model has a “Per 1,000 sessions/mo” model, their Enterprise self hosted model might have that as well. So it’ll have some kinda DRM/License managing, and maybe a “call home” to check your license or usage every once in a while


  • He’s already pointing out the problems himself:

    The difference is that Spotify is a for-profit corporation. And they have to distribute profits to their stockholders before they pay the musicians. And as a result, the musicians complain that they’re not getting very much at all.

    Yea, so at Spotify the profits are distributed “equally” - meaning Taylor Swift with 1 billion listens per month gets 99.9999% of the profits, [[Obscure metal band]] with 100 listens gets $0.001. However, if I only listened to [[Obscure metal band]] and nothing else, shouldn’t my entire $5.99/month go to [[Obscure metal band]]? And not be pooled with stuff I didn’t listen to?

    How would this work with a “Post-Open software administrative organization”? Ubuntu has 1 billion installs, my [[Obscure open source library]] is used by a couple of companies, and it’s the only “Post-Open software” that those companies use - Do I get that 1 percent of their revenue? Or does administrative organization siphon it away, keep 0.1%, and send the other 0.9% to the top 10 “Post-Open Projects”…?

    Companies would have to publish which “Post-Open software” software they’re using, and to what extend. For example, if Ubuntu would be Post-Open-software, it uses loads of inner projects and libraries, which again use more and more libraries, some might being Post-Open software. You’d have to create a whole financial dependency tree per company to determine how to distribute their revenue fairly


  • I manually redraw my service architecture because I can create higher quality documentation than when trying to auto-generate it.

    But you can get a baseline depending on which Cloud you use. For example, in AWS you can use workload discovery - that generates a system overview.

    Bonus (optional) question: Is there a way to handle schema updates? For example generate code from the documentation that triggers a CI build in affected repos to ensure it still works with the updates.

    Yes, for example, if your build server exposes the API with an OpenAPI scheme, you can use the build server to generate a client library like a nuget or npn.

    Then in the API consumer you can add a build step that checks if there are new version of the client library. Or setup dependabot that creates PRs to update those dependencies







  • 243650.0054 = 47,304$/ year / instance. How many instances are hosted by AWS? How many are hosted by Google? How many by other Redis aaS?

    Formatting it like 47,304$/ year seems like you’re saying it’s $47k, but it’s just $47. How much would it cost any company to self-maintain their Redis instance?

    Don’t contribute back in a significant manner

    They have multiple people full time employed that are contributing, and how are they “hampering its development”?

    If you look at the top contributors: https://github.com/redis/redis/graphs/contributors

    • #4 Binbin works for Tencent Cloud
    • #6 Zhao Zhao works for Alibaba
    • #7 Madelyn Olson works for AWS
    • #9 Wen Hui works for Huawei

    Soo actually these cloud providers are some of biggest contributes to the project. They’re not just taking Redis and aren’t contributing. The opposite actually lol.

    Besides, you’re acting like Redis is some poor little startup, but they’re a company with 991 people (by their linkedin stats). Its like if Oracle would change the MySQL license, and then you side with Oracle “Poor little Oracle, everyone uses MySQL, but no one contributes” - yea no


  • They were allowed to leech, […]

    Services like AWS and Google Cloud offer 1000s of “free software” (like Redis) as a service - like AWS Elasticache - and if you look at the pricing, cache.t2.micro for example, is $0.017/hour, while just a plain t2.micro vm is $0.0116/hour. So effectively AWS is only “leeching” $0.0054 an hour on the Managed Redis that they’re offering.

    An AWS managed Redis is just easier, otherwise I’d have to boot my own t2.micro, and install Redis there. I’d still be using official Redis on AWS, because self-hosting is still fine in the new license, it’s just more work for me, because the license doesn’t allow AWS to do it for me anymore.

    and the naive, purist opensource community ([…]) will happily join the ranks of businesses that couldn’t be bothered to donate to Redis

    It’s funny how people are now siding with Redis. When other companies did something similar (like identityserver4 was FooS, and then they created their new commercial company - and everyone was like “fuck you, you people are sellouts.”.

    Most of the time when a FooS project goes commercial, people make a free fork and the commercial project slowly dies


  • Probably, AWS and Google probably have millions of existing customers using Redis. And AWS and Google are not going to be paying for it themselves of course, but just pass the costs on to their customers.

    So they can stick to the old official Redis version for a while, before the license change happened, but at some point someone might find a vulnerability, and patch it in the official Redis, and then everyone that’s stuck on the old version is fucked - it’s a bit of a ticking time-bomb to be stuck on an old version.

    So then AWS and Google customers can decide

    • “I want to use the latest version of official Redis, and pay x per month per Redis cache” (if the new license allows that)
    • Or “AWS doesn’t support a free Redis anymore, but competitor does, so I’m just gonna migrate my infra to a different cloud”

    So if they already switch to an open-license fork they can preemptively mitigate most of those risks