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

help-circle



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






  • I think this is a side effect of sharing and discussion these events online, especially in a link aggregator like Lemmy. You can you see inconsistent views presented in multiple threads yet they feel as if you’re interacting with the same group of people.

    Some people are happy about this turn of events while others are not. I expect that you’re seeing differing major opinions from separate groups of people.





  • Lodra@programming.devtodailygames@lemmy.zipQuordle #908
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    Daily Quordle 908
    6️⃣3️⃣
    5️⃣7️⃣
    m-w.com/games/quordle/
    ⬜⬜⬜🟩⬜ 🟨⬜⬜⬜⬜
    ⬜⬜⬜🟩⬜ ⬜⬜⬜⬜⬜
    🟨⬜🟩⬜⬜ 🟩🟩🟩🟩🟩
    🟩⬜🟩🟩🟩 ⬛⬛⬛⬛⬛
    ⬜⬜⬜🟩⬜ ⬛⬛⬛⬛⬛
    🟩🟩🟩🟩🟩 ⬛⬛⬛⬛⬛

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







  • A complicated plugin ecosystem (e.g. Jenkins) makes for a terrible use experience. It’s annoying to configure a bunch of config files. Managing dependencies can be a complete nightmare. these problems also complicate your ci/cd.

    So I’ll offer a slightly different answer. I prefer a single file instead of splitting up the config. And I’ll use OpenTelemetry as an excellent example of why. the plugins are compiled right into the app binary. This offers a ton of advantages, including a great reason to merge all of your app configs in a single file.

    This really only works well if you have a good app though.