• 1 Post
  • 76 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!








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








  • So I read a bit of Mozilla’s documentation about this feature. It sounds like they’re trying to replace the current practices with something safer. Honestly, my first thought is that this is a good thing for two reasons.

    • It’s an attempt to replace cross site tracking methods, which are terrible
    • Those of us that fight against ads, tracking, etc. can simple use typical methods to block the api. Methods that were already using (I think)

    If both of these are true, then it could be a net positive for the world. Please tell me if I’m wrong!