warmwaffles

Oh that's interesting. I've never used mdadm before. At least not knowingly.

> The only thing it's missing before I consider it full-featured is stable RAID 5/6. But it looks like that hasn't been forgotten.

I've been running BTRFS RAID6 since 2016 and have only had one issue (arch kernel needed to be rolled back) and never suffered anything catastrophic. It's perfectly happy humming along with a 15x8TB raid array.

The flexibility of software RAID is nice that you can mix and match hard drive manufacturers and generally have zero issues. For hardware RAID, I've always been told to stick to one drive family from one manufacturer and not to mix and match.

I've been let down by ZFS once before when I wanted to add more drives to an existing pool.

High rise buildings consume more electricity per capita than smaller family homes and apartments.

Cool, so absolve the EPA of any wrong doing?

> It's like blaming the dentist for scratching your gums while repairing a cavity. A big dose of, "Well sure, but if you had listened to them in the first place.. "

Terrible analogy. The EPA knew there was heavy contamination in that mine, and yet decided to drill into the side of the mountain regardless knowing full well the implications of the heavy water getting released. There were other ways they could have gone about measuring and keeping tabs on the toxic build up. Yet they chose the most expedient riskiest solution that backfired spectacularly.

In your analogy, this is akin to the dentist taking a 1/4 inch drill bit to the side of your tooth to measure the cavity damage and spilling about a pint of blood on the floor in the process.

The other problem is, the EPA isn't also all sunshine and rainbows https://www.cnn.com/2015/08/09/us/colorado-epa-mine-river-sp...

I was thinking something more like this: https://en.wikipedia.org/wiki/Baseball_glove

A big net, or a gigantic baseball glove.

I don't believe the spec ever calls out what is exactly supposed to happen for multiplication overflow, and this was left up to the implementation to decide what to do. That being said, libmusl implemented a short but sweet check [1]. Fun stuff.

[1]: https://github.com/rofl0r/musl/blob/d05aaedaabd4f5472c233dbb...

> This sounds like an Inbound TCP License is next on the UK’s list?

Make sure you have a license for those bits.

I really missed newground's style of BB.

Wrong, planes are powered down often.

Usually these aircraft are power cycled often. There is no way they are flying these planes 51 days straight with no power cycle. Maintenance checks would necessitate a restart.

> How much was ECC ram at that point? Linus is incredibly wealthy...

I don't think Linus likes wasting money for the sake of wasting it.

I wonder how much more likely it is for random bit flips in machine shops with Thoriated tungsten rods near a CNC machine.

Nothing is risk free. As long as the user has a legal copy of the game it is possible. Just look at OpenRCT2. You need to have a legal copy of the game in order to run it.

You can't use that leaked code without being sued. It has to be clean room implemented or disassembled AFAIK.

"I use arch btw"

> Every team I'm in I strongly advise against such commits honestly. They don't help anyone, I emphasize being able to find things you changed if you need to find them. You can even enforce a format for commits.

Same with me, but people still ignore it.

Depends on the situation entirely.

If I see a ton of commits like "fixing formatting" or "oops", I want those squashed away into proper commits.

If the changes you make are atomic in their own right and I can check out that commit, compile it, then run tests, and it passes. That's perfect. It works good for git-bisect, but the trick is to get everyone on board in the project to do that.

For public libraries I maintain, it's squash merges all the way. I like a clean history and the ability to check out that commit, compile, test, and run cleanly is perfect.

Oh no, don't give me ideas to do the same for our girls.

> POLIO. In 2022. We did this.

First off there are two strains of polio. It will never be eradicated, it'll just mutate and move on. Just like the Spanish Flu did.

Second

> "State of Emergency" != Martial Law

It certainly was being treated like that early days during the pandemic. Shuttering all businesses, forcing people to stay home, and curfews.

> Emergency powers help us keep more Americans safe & alive. > ... > Can't wait to see what we manage to fuck up in the next 20 years.

You are being hyperbolic.

> And if we decided that we should do some things for public health in the very short term, should we humor every crackpot who wants us to wait?

That's a very short sighted view. Expanding the power of government is not always the answer.

This is incredibly helpful. I did not know this was a possibility.

How would this look with a sample query? (using AS NIT MATERIALIZED)

The only issue I see with CTE's and have encountered, is poor query performance. The query planner needs to improve in this regard. At one point I noticed some of my CTE with queries being written to a temp file on disk and used to join against, when an inlined query did not do this producing the same results.

Reminds me of "The Geometry of Innocent Flesh on the Bone: Return-into-libc without Function Calls (on the x86)" [1]

[1]: https://hovav.net/ucsd/dist/geometry.pdf

This is how I understood it to work. When you buy your plane tickets now, that money goes into an escrow account and stays there until you check-in for your flight and is not released until check-in happens. This is why airlines like you to do early check-in.