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!
My strategy is pretty similar actually. I have two starter words that cover all the vowels, h, and y. Then I start guessing actually words from there. Gives me a chance at scoring 6 though that’s pretty darn unlikely. I typically score a 7 or 8. Losing is pretty rare now
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.
lol thanks for the answer. This is the really relevant bit isn’t it? My Linux machines have also never died this badly before. But I’ve seen windows do it a number of times before this whole fiasco.
This is funny timing for me. I mentioned something related to my wife yesterday. When I was a kid, my perception of other countries was completely ridiculous. Low tech, uncivilized, impoverished, etc. compared to the USA. It took way too long for me to achieve a more realistic perspective of foreign countries at large. I’m not sure who to blame for this but the they surely belong to the previous generation or two.
I’m familiar enough with Linux but never used an immutable distro. I recognize the technical difference between what you describe and “go delete a specific file in safe mode”. But how about the more generic statement? Is this much different from “boot in a special way and go fix the problem”? Is any easier or more difficult than what people had to do on windows?
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.
Exactly. There is a general need to destroy and rebuild a system but it is often dangerous and costly. Especially with regard to a system of laws and government. Improving the system more naturally is far more safe and more achievable at smaller scales.
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!