cls59

Even with copy-on-write, fork() still has to pay the setup cost for COW. If the parent process has a lot of busy threads (e.g. Java), you can end up doing a lot of unnecessary COW before exec() fires.

If Apple keeps using A Pro-series chips for the Neo, then the RAM will go to at least 12GB when they swap to the A19 Pro, or newer.

Or Dow Chemical.

If I understand the article correctly, that second proof was published as a rider on a first proof that was entirely Dedekind's. So, there was definitely a credit owed at time of publishing.

I came away with the impression that the biggest villain in this story was Kronecker. Without the need to tiptoe around his ego and gatekeeping, these results may have been published as a paper with joint authorship.

The fact that it was even proposed in the first place is still concerning.

From a quick skim of hardware support on Wikipedia, it looks like encoding support for H.265 showed up in NVIDIA, AMD, et. al around 2015 whereas AV1 support didn't arrive until 2022.

So, the apparent preference could simply be 5+ years more time to do hardware-assisted transcoding.

Agreed. I think the buried lede here is actually the clawback clause. With that in the contract, this isn't a $1.5 million dollar grant, it's a $1.5 million dollar liability.

If you take the money and spend it on research and development and then get hit by a clawback, whether due to "DEI" or some other reason, that is a financially ruinous event to somehow come up with $1.5 million dollars that was already spent.

A shame and a waste as it sounds like the project would have been beneficial outside of the Python ecosystem, had it been funded.

Also, "git reflog" lists out all commit SHAs in chronological order. Trying to figure out how to rebase, but got lost and everything seems broken? You're just one "git reset" away from the better place you were in and "reflog" has the list.

The control plane of Tailscale can even be self-hosted via the Headscale project:

https://github.com/juanfont/headscale

As for backups, I like both https://github.com/restic/restic and https://github.com/kopia/kopia/. Encryption is done client-side, so the only thing the offsite host receives is encrypted blobs.

It doesn’t make sense to tax every other passenger for it.

I'd rather pay a monetary tax on my ticket to keep families organized together instead of the discomfort tax of sharing a row with parent+child that has been unexpectedly split up from their partner and is now trying to manage the child's behavior for the duration of the flight without the benefit of teamwork.

I've never encountered a bouncer taking pictures of an ID. They check it, using a flashlight if needed, and wave you in.

Many businesses in the US check ID at the door. If you are underage, they don't let you in.

On the surface it seems reasonable to ask for an equivalent ID check online.

But. The bouncer doesn't photocopy my ID and store it in a poorly secured back room that is regularly raided by criminal enterprises or outright sold by unscrupulous owners of the establishment. Similarly, they don't check in with the government in a manner that leaves a record.

I'm fine with an ID check, but I think it is also reasonable to demand the same level of privacy that one gets when visiting a bar, casino, burlesque club, or similar establishment.

README also leads with a screenshot that has macOS window styling. So, "works on Mac" is a reasonable first impression to draw.

This. There is plenty to dislike about Ruby, but it is exceptionally strong at implementing domain specific languages. Homebrew was able to use that to lower the barrier to packaging software.

Also, using Git + GitHub instead of SVN + Trac was absolutely a winning pick for scaling project participation back in the 2000s.

And then kinds just learn how to download and run an open-source browser produced outside of the country that does not implement the setting on the client side.

Yup. GitHub alone killed my last effort to go all-in on IPv6 for my personal cloud.

Sure, I could have hacked my way through it. But, that was more work than just paying the extra few cents a month for IPv4.

That depends on whether you need to sell the bond before its maturity date. Supposing it is a 1 year bond, if you hold it for the full year you get your £100 back. If you need to sell early, then you might get less back if rates have risen.

A money market fund operates differently from holding individual bonds and aims to provide you with the ability to sell at any time without a loss --- but the monthly interest paid out will fluctuate according to market rates.

There is the unfortunately plausible scenario of the US Congress suffering a fit of insanity and blocking the ability of the Treasury to make a timely payment.

It's hard to say what the outcome of such a move would be, but one possibility is Treasuries taking a large haircut, but without triggering the sort of collapse that would swallow FDIC along with everything else.

Many brokerages also offer access to a public market of bank CD offerings. So, you can go that route and get FDIC insurance if you want while avoiding the pitfalls of dealing directly with a single bank outlined in the article.

I prefer Treasuries in my taxable accounts as there is a break on State taxes for the interest generated. I hold CDs in my non-taxable retirement accounts as they tend to pay a few tenths of a percent higher.

Bryan Cantrill draws some excellent parallels between this incident and software systems in his "Debugging Under Fire" talk (beware of semi-automated systems):

https://www.youtube.com/watch?v=30jNsCVLpAE

To point 1, I'd argue that a SQLite database is a great next step beyond CSV despite being a binary format.

Sure, temperatures have changed before. But the rate of change this time around is as much of a problem as the amount of change: https://xkcd.com/1732/

I have one of these, nearly 12 years old at this point. Around two years in, it took nearly a full pint of double imperial stout head-on during a buzzed coding session. Was sticky for a little bit, but otherwise no ill effects. Built like a tank.

As someone who was on the Civil Engineering track prior to ending up in tech, jail time seems unlikely unless the breach of ethics was particularly egregious.

The consequence of poor decision making in a Professional Engineering setting that we were most often warned against was ejection from the profession. If your work results in the loss of life or property, you may find yourself unable to continue working in the field due to loss of license or a steep increase in insurance premiums.

As a software "engineer", the consequences for poor professionalism are not as sharply defined.

Yeah, Pihole made it super easy to cut over to Quad-9 once I figured out what the problem was.

Or who don't even care about the long-term health. Extract all you can today and dump the remains. Having a company that remains healthy and prosperous for generations is not an outcome that some investors seem to be optimizing for.

Most of the awk scripts I end up writing are for execution by other people on machines I don't have control over. If strptime was in the standard library, I could use it if I knew the target OS was something like "Ubuntu XX.XX or newer, RedHat X or newer".

When strptime is in an add-on library, I can't use it.

I wish gawk had a native strptime function. Always seems like an odd omission given strftime is included.

One of the first things I grep for in dmesg ;)

AWS is a 8,000 pound gorilla. This means throwing massive amounts of promotional credit at new accounts is often the only viable way to get them into the funnel.