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

help-circle
  • Omg it’s sooo daammmn slooow it takes around 30 seconds to bulk - insert 15000 rows

    Do you have any measurements on how long it takes when you just ‘do it raw’? Like trying to do the same insert though SQL Server Management Studio or something?

    Because to me it’s not really clear what’s slow. Like you’re complaining specifically about the Microsoft ODBC driver - but do you base that on anything? Can you insert faster from Linux or through other means?

    Like if it’s just ‘always slow’ it might just be the SQL Server. If you can better pinpoint when it’s slow, and when it’s fast(er) that probably helps to tell how to speed it up


  • When I stopped, subversion was what we used. I’m trying to understand Git, but it’s a giant conceptual leap.

    It’s probably not ‘that much of a leap’ as you imagine. If you’re looking at Git tutorials, they’re usually covering all kinda complex scenarios of how to ‘properly use Git’. But a lot of people barely care about ‘properly using Git’ and they just kinda use it as a substitute for SVN… You create branches, you merge them back and forth, and that’s about it.

    Like if you want to contribute to an open source project, all you have to do is create a fork (your own branch in SVN terms) - commit some stuff to it, and create a pull request (request to have your changes merged) back to the original branch. git pull is just svn update - getting someone elses commits

    Not saying there aren’t more complex features in git, or that learning git properly isn’t worth it, just saying, I don’t think you have to see it as a ‘giant conceptual leap’ that’s preventing you from jumping back into programming. Easiest approach just to get started would be probably to just download a GUI like Sourcetree or Fork, and you just kinda pretend you’re still using SVN - approach wise











  • I believe there are a large number of feature requests on Lemmy’s GitHub page, making it difficult for developers to prioritize what’s truly important to users.

    Github issues are annoying that way. You could solve it by closing down “issues” and using discussions instead. People can up and downvote discussions, and you can see that from the listview, unlike with issues.

    And you can have threaded conversations in discussions.



  • 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