• 12 Posts
  • 299 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • Oh I could easily be wrong about forgo having integrated ci/cd already. It’s the only tool I mentioned shove that I have never used before. I’m not a good source on this one.

    But I have used both flux and argo quite a lot. I’ll admit that it flux implementation was bad, but it was just a bad experience for everyone using it with me. It was a memory hog and often created. Very few people understood how to use it correctly. When there were errors with e.g. a helm template, you just had to go looking for issues and read through the log. It moved git tags around so you don’t get a history of what flux was doing. I could probably remember more issues if I tried.

    But none of that was a problem with Argo. We just started using it successfully on day 1. Plus its UI is fantastic and a huge advantage. It’s easy to navigate, spot issues, troubleshoot, etc. It also exposes users to resources they unknowingly create because Argo displays owned resources. This part really helped people understand what was going on in k8s. Oh and argo is very extensible. Maybe flux is too but I haven’t tried.


  • They’re both good and quite similar on the surface. But I find that larger, more complicated uses tend to get messy with gitlab because of the heavy use of bash. However, actions are (always?) written in typescript. If your automation needs a lot of logic to handle varying uses, then it’s nice to avoid bash and code with a more language.

    In other words, I’ve seen a few monstrosities that large companies build into gitlab and yikes!










  • 🙂 Daily Quordle 980
    3️⃣6️⃣
    4️⃣5️⃣
    m-w.com/games/quordle/
    🟨🟨⬜🟨⬜ ⬜⬜🟨🟨⬜
    🟩⬜🟩⬜⬜ ⬜⬜⬜⬜🟨
    🟩🟩🟩🟩🟩 ⬜🟨⬜⬜⬜
    ⬛⬛⬛⬛⬛ 🟩⬜🟨⬜⬜
    ⬛⬛⬛⬛⬛ ⬜🟨⬜⬜⬜
    ⬛⬛⬛⬛⬛ 🟩🟩🟩🟩🟩

    ⬜🟨🟩⬜🟨 🟩⬜⬜⬜⬜
    🟨⬜⬜⬜🟨 ⬜⬜🟩⬜🟨
    🟨⬜⬜⬜🟩 ⬜⬜🟩🟨⬜
    🟩🟩🟩🟩🟩 🟨⬜⬜⬜⬜
    ⬛⬛⬛⬛⬛ 🟩🟩🟩🟩🟩

    I normally don’t post scores because adding the spaces on every line is a pain on IOS. But I got a good score today 🤣


  • Lodra@programming.devtodailygames@lemmy.zipBlossom 9/29
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    I’ve played a few times and got big scores like that. My top was 358 or something around there. The big scores were cool but I spent waaayyy too much time chasing those big words. Maybe 2 hours spread throughout a day. I’m no longer playing this one daily because I couldn’t make it a casual effort.

    If you can be happy playing the game and not worrying about beating everyone’s top scores, then I suggest simply enjoying the game


  • Lodra@programming.devtodailygames@lemmy.zipDuotrigordle #940
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Daily Duotrigordle #940
    Guesses: 37/37
    1️⃣8️⃣ 1️⃣9️⃣ 1️⃣5️⃣ 1️⃣4️⃣
    0️⃣9️⃣ 1️⃣6️⃣ 1️⃣3️⃣ 0️⃣5️⃣
    2️⃣0️⃣ 2️⃣1️⃣ 1️⃣2️⃣ 2️⃣2️⃣
    2️⃣3️⃣ 1️⃣0️⃣ 0️⃣4️⃣ 2️⃣4️⃣
    2️⃣5️⃣ 2️⃣6️⃣ 2️⃣7️⃣ 2️⃣8️⃣
    2️⃣9️⃣ 3️⃣0️⃣ 3️⃣1️⃣ 3️⃣6️⃣
    3️⃣2️⃣ 3️⃣3️⃣ 3️⃣4️⃣ 3️⃣5️⃣
    0️⃣6️⃣ 3️⃣7️⃣ 0️⃣7️⃣ 0️⃣8️⃣
    https://duotrigordle.com/

    I think this is my first win. You really have limited mistakes available!









  • That basic idea is roughly how compression works in general. Think zip, tar, etc. files. Identify snippets of highly used byte sequences and create a “map of where each sequence is used. These methods work great on simple types of data like text files where there’s a lot of repetition. Photos have a lot more randomness and tend not to compress as well. At least not so simply.

    You could apply the same methods to multiple image files but I think you’ll run into the same challenge. They won’t compress very well. So you’d have to come up with a more nuanced strategy. It’s a fascinating idea that’s worth exploring. But you’re definitely in the realm of advanced algorithms, file formats, and storage devices.

    That’s apparently my long response for “the other responses are right”