• 1 Post
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • It looks safe to me in the sense that I don’t see any malicious code in here. I don’t think the committee is trying to sneak in security hopes or similar. So all good on from that perspective.

    It’s a very simple helm chart which is consideration! Here’s the thing with charts. They’re meant to be an official means of distributing your app’s manifests for k8s. One package with all runtime needs defined. If the chart supports every tweak I need, then it’s great! If it doesn’t, then I need to modify it myself. This usually means forking the project, making edits, and templating from the fork. It’s a lot of overhead for end users. If the maintainer is willing, it’s so much easier to create an issue or submit a PR with the needed changes.

    Your project has some stars and forks. People are likely using it. Grats! The helm chart doesn’t like meet everyone’s needs and I would expect this to spur some extra issues and PRs. Is that good or bad? That’s up to you!!




  • This isn’t exactly a rogue like but there are some similar aspects and I find that it satisfies in the same way. The game is Backpack Battles. Available on Steam. There’s a free demo available too with full mechanics but limited character options.

    This is my default game more for when I have a few minutes to relax and nothing more pressing to do





  • 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”


  • Never do this.

    Git is all about tracking changes over time which is meaningless with binary files. They are bloat for your repo, slowing down operations. Depending on the repo, they are likely to change from CI with every commit. That last one means that every commit turns into 2 commits btw. They are can ruin diffs. I could go on for a long time here.

    There are basically 0 upsides. Use an artifact repository instead!