astrsk

Well, it was fun paying into it for 20 years. Glad I never calculated the payout as part of my retirement strategy.

If you accept this one anecdote of an ambulance being stuck in NY, then you have to accept my anecdote that everyone in the PNW moves over to let ambulances through no problem.

It’s not all the same.

I still think I’ll stick with nala as my apt front-end but hopefully this will be a more robust backend.

$118/mo for 1200 down 35 up, copper. On a “contract” to get $30 off but added the $30 no data cap add on so it’s a wash, but at least it doesn’t double because we use ~4TB/mo data. This is in North America.

Just puts(“I’m a teapot”); :)

This is mostly an IOPS dependent answer. Do you have multiple hot services constantly hitting the disk? If so, it can be advantageous to split the heavy hitters across different disk controllers, so in high redundancy situations that means different dedicated pools. If it’s a bunch of services just reading, filesystems like ZFS use caching to almost completely eliminate disk thrashing.

I use Actual and my solution is to just report the differences in investments value at the end of each week as a transaction. It’s not great but it affords me an opportunity to see trends in a different way and make adjustments feeling a little more informed. I even put my car in and just check KBB every year and update it. Helps with the year end net worth evaluation though it’s not the most flexible.

The death note cannot be destroyed, not even by burning. It can only be relinquished willingly or by the owner dying.

Not if they’re picturing the correct person. Writing the wrong name but picturing the correct person will result in no death so as to keep the innocent or same-name people alive. It’s in the rules.

You don’t need to hide the book right before you die. The shinigami it belongs to will take it back and presumably leave. They might stick around to give it to someone else but that’s their choice and nothing to worry about in your upcoming purgatory. Even if you did cement it and bury it where no human will ever find it, the shinigami can just phase through and grab it any time.

Still waiting for Alive 2017 (I know…)

Exactly. This is a non-story and they already have a built in integrations system for escalating / customizing requests.

Alternativeto.net is a good resource for finding alternatives by filterable tags including platform! Also wine and proton have come a long ways, many windows apps work just fine in a small wine or proton container.

While it may be true that the master branch is more akin to a master record, not everyone knows the nuance and quite frankly it doesn’t matter, if it makes people uncomfortable then it shouldn’t be a problem to accommodate a simple change, most of the tech world has already done so. Computers used to have a literal slave/master relationship with hardware components and control systems and we moved past that just fine despite still having controllers and actors everywhere.

It was someone ranting about the many hours and days of lost productivity and cost of manually switching over 70+ legacy build pipelines all because of a branch name change. Also lots of condescending and insulting language from someone who thought their stubbornness and “standards” meant they were better than everyone else. Honestly I just probably set them off in my first message and they wouldn’t let it go, leading to increased levels of ranting and insults from them attempting to spout accomplishments while detailing their failings in the same breath. Admittedly that above description is a bit belittling from my end, I’m just annoyed they couldn’t keep their messages up for all to see.

I still stand by the opinion that changing branch strategies, names, or targets should not be a multi-hour multi-resource process and if it is, that’s a failure of the systems engineers / ops who put together such a plan. It’s possible to have CI/CD pipelines that run for years on end attached to critical infrastructure while being flexible enough for such simple config changes and maintained by one engineer.

Again, you’re conflating your own stubbornness with correctness and that just ain’t how it goes. Branch names are frivolous. So much so that changing the strategy or retargeting a branch one time shouldn’t be such a nightmare for your pipelines that you have to pretend like you’re the big dick on campus spouting accomplishments when someone mildly suggests there’s a mistake in your thinking. Look inward if you’re so upset by this that you have to make up irrelevant insults in a vague attempt to protect your own ego, then go fix your pipelines to make it easier to do for the next person after you’re gone.

lmao nothing you’ve said has anything to do with “Main is more concise and less problematic”. Just because you created more work for yourself by having 70+ pipelines that need to be rewritten for a branch name change doesn’t mean it’s less concise or more problematic. It means you messed up by not having a pipeline capable of such a basic feature – generalized targets with a separation of concerns. Standards change, requirements change, so do build pipelines. Being stubborn is not a reason against changing colloquial terms out of respect and growth in understanding.

The only statement in your ridiculous rant that has any validity is that of your legacy pipeline configurations. But pipelines need to be updated and validated semi-regularly and should be generalized to begin with, so it’s not really any good point that your legacy pipelines cannot handle a default branch name change like modern pipelines should.

Swap main and master in your comment and it reads the exact same with all the same shallow justifications.

Your username is not proof that your messages on Reddit were encrypted and not visible by anyone but you and the other party…

They never were