2,487 karma · joined May 18, 2018
Can you expound on this? The same parent company (Amer Sports) also owns Salomon/Atomic and several other well regarded brands. I wasn't aware that something had changed recently. Are you talking about the Anta Sports buyout? People use these brands for life-critical applications in the backcountry, so this is certainly concerning to hear.
git clone --bare <dotifles repo> ~/.dotfiles
git --git-dir=$HOME/.dotfiles/ --work-tree=$HOME checkout
git --git-dir=$HOME/.dotfiles/ --work-tree=$HOME config --local status.showUntrackedFiles no
And then I add an alias: alias cfg='git --git-dir=$HOME/.dotfiles --work-tree=$HOME'
Now I can just manage my dotfiles as a git repo, and I don't have to worry about accidentally adding local secrets to the repo.[0] https://the5krunner.com/2020/08/29/joshua-cheptegai-gutted-a...
That's unlikely, unless it increased your own risky behavior. If you install uMatrix and then set it to allow all content, you would be in the same situation as if you didn't have uMatrix at all, ie. no less safe.
I ran a race through this tunnel back when races were still a thing. Very surreal experience running in a dark, wet tunnel with hundreds of others in the clouds of steam illuminated by headlamps. I really love this section of trail.
These types of bugs can be very hardware-specific. If people are playing on hardware similar enough to the game developer's workstations, they might not encounter them at the same rate that you do. Something to bear in mind.
Have you tried fingerless gloves? During long winter backpacking trips or situations where I'll be living without heat for a while, I take some liner gloves and cut the fingers just past the first knuckle. The gloves stay clean even with prolonged use, and you can still use capacitive touch screens and do dexterous work like typing.
(An alternative interpretation of these events is that my body rewired itself in my mid 20s and my behavior changed accordingly.)
That's exactly what happened during the black plague. It lead to the end of feudalism. A shortage of labor will absolutely boost the value of labor.
The problem is that each of the magic functions you listed above are separate plugins. They're not part of Jenkins itself. Each plugin may (and often will) push breaking changes and vulnerabilities to your Jenkins instance, if they haven't been outright abandoned by their maintainers. Over time, your builds will steadily accumulate hacks to work around broken plugins, and your Jenkins instance rots.
(Caveat: If you plan to do devops at a Big Corp, then you might as well get good at Jenkins because they already use it.)
The email-based workflow could be convenient for some, but speaking for myself, I'd mainly prefer to interact via the web UI. The ability to send updates to patches submitted from the web UI seems to be missing. If I made a mistake or was asked to change something, I had to completely re-submit the patch as a separate email. I couldn't find a way to communicate on mailing lists without using an external email client. Basic things, like needing to hand-wrap my emails at 70-something characters, and remember to remove quoted text from the bottom of emails, is an unfortunate barrier to entry for new contributors. All of these things could be abstracted away via the web UI for those who don't want to use email.
Authentication is blocked by accessing storage. You cannot proceed until the storage read operation is completed. There is no parallel work to be accomplished here. This isn't UI code. There's no event loop. Why would you want this to be asynchronous? This seems like async as a dogma, rather than as a tool to accomplish something specific.