masklinn

FWIW there’s a better one next year which skirts through southern spain and norther Africa.

TBF it’s quite late in the evening already so in the places where this is happening none of it is as off as it is when the eclipse occurs mid-day.

Recommendation (2) assumes any UA which supports background-clip supports -webkit-text-fill-color. That seems rather dodgy.

Wrapping the rule in a feature query seems a lot cleaner and more reliable.

There’s also memory hotplugging via virtio-mem. But generally speaking downscaling live vm memory can’t be said to be a solved problem, it’s more of an active area of research.

“microvms” are real vms but the hypervisor and vm (guest kernel) shed most of the hardware / device emulation, support, and discovery which makes traditional VMs look / feel like real computers, as well as most guest interactions. This gives them extremely low overhead.

Firecracker is designed to start a VM in under 125ms and 5MB. Netbsd advertises that you can direct-boot a MICROVM kernel configuration in under 10ms.

It's not just a budget saver (and possibly an aesthetic decision), it also keeps the ground permeable which has all sorts of impacts in terms of acquifers, ground subsidence, sewer service, etc...

Thanks for writing!

An other commenter pointed me towards the link in the first footnote. May I suggest linking most of the opening sentence, from "a post" to "curlese"? That would make it very clear where said previous post is.

Also maybe cross-link the italian and contributed english versions of the original post in case someone else finds the former and can't read italian, the contributed translation is definitely quite a bit better than Apple's automated translation at the very least.

So there is, thank you for the directions.

You should probably link to the previous post, it’s a right pain to find.

Also is there an approved English version of it, or the same information by someone else?

edit: as pointed out there is one (to an english translation) in the first footnote

The upsell ads progressively getting more massive and desperate is pretty funny tho.

> I thought the idea behind exoskeletons and fancy wheelchairs was that they allow handicapped people to go more places, not to substitute for better infrastructure. I haven't seen any of the companies behind these devices claim that they make such improvements obsolete.

They don't need to, and the might not even do that, but the boosters and the clipfarms are very much in on it. You don't see that "engagement" for continuous sidewalks and raised crosswalks despite how amazing they are.

And they're also very convenient as a way to avoid infrastructural improvements, you can point to disability dongles as a reason not to invest in it, that way you're conveniently not bearing the cost.

> And as the post mentions, such infrastructure is useful for anyone with luggage, a stroller, or a hand truck.

The problem is that's at best a post-hoc realisation, when that argument is made upfront it's pretty much always dismissed out of hand (very much blub adjacent), you can see it in pretty much every discussion about better walk/bike infrastructure.

amp wasn't just stripped down HTML either, it was a mix of restricted HTML and custom AMP components, the latter being necessary to load external resources (breaking standard browser preload scanners and requiring amp's js to load before that could happen). The banned HTML elements (https://amp.dev/documentation/guides-and-tutorials/websites/...) included img, picture, video, audio, iframe, all replaced with equivalent amp components.

> It's effectively dead today, and while it was dominant, Google abused it to get people to view and link to their cached copies of AMP pages, rather than the original site.

That was the entire point of the tech. If Google had wanted they could have upranked simple and lightweight websites but they didn’t do that (at least not until whoever had used amp for their promo package left and the project was killed).

It does not look like the author posted this here since it was posted on the blog last week. So would probably be a better idea to suggest / recommend this at https://github.com/github/rust-gems/tree/main/crates/casefol...

A little treat for all the seagulls keytar solo

That is exactly why many big projects are migrating to becoming CNA, so that randos can’t get assigned unqualified CVEs which nobody has looked at or validated.

Apparently RedHat is a CNA of last resort, so it might be possible to get your project under Redhat’s scope and go through them without having to be a CNA yourself.

RAII has complications in GC’d, fuzzy ownership langages, it becomes much less ergonomic there because now passing an RAII object as parameter to a function causes that function to clean it up, so you need additional mechanisms to bypass this. Same if you just poke an RAII object inside a collection.

Traditionally langages with simpler runtimes simply used destructors for this, refcounting made it deterministic (modulo the old reference leak), but more advanced garbage collection schemes made that stop working.

And try/finally.

> Or does ripgrep only override Rust's global allocator?

That one, as you can see in the code linked above, it only does rust-level overriding as that was where musl's allocator was found to impact ripgrep (https://github.com/BurntSushi/ripgrep/commit/03bf37ff4a29361...)

> I get why people don't bother replacing the default allocator from musl all the time (it's there, convenient).

ripgrep actually sets jemalloc as global allocator when built for 64b musl: https://github.com/BurntSushi/ripgrep/blob/435f59fc4b43af3ab...

> Millions do experience 0F, and it’s ok to not use the full range.

That’s not even an argument. Billions never experience freezing temperatures let alone 0F, and it’s ok to use negative numbers.

> At or around 0F is cold, as you move closer or beyond it, it’s cold.

The exact same statement can be made about 0C. Hell if you live in a subtropical area 10C is cold.

> Most people would likely prefer to never deal with <0F or >100F.

Most people would likely prefer to never deal with < 15C or > 30C.

> 0F is cold, 100F is hot. I experience both of these temperatures outside where I live every year.

Most people never experience anywhere near 0F in their lives.

> -20C to -40C seems much more arbitrary as a way to measure the zone humans mostly live in.

The zone most humans live in does not routinely (if ever) get anywhere near -20, to say nothing of -40.

It’s frightening that… NIST is doing the very thing it was established to do back when it was called the Bureau of Standards?

Not really, a large reactor is way too power dense. An EPR reactor has a thermal output of 4.6GW. And the tertiary is cooling steam turbines so it's below boiling, you'd need something like 10 sqkm worth of surface, per reactor, with an environment cool enough that this could actually radiate.

Even using industrial air-cooling design you'd need on the order of a million sqm or two (for reference a good quality computer heatsink is about a third of a square meter worth of fins)

It can vary by the river too (e.g. I remember Switzerland pulling back a reactor around 25 intake), and iirc there’s an absolute limit on the outflow (you don’t want to boil alive the stuff just off of the plant) and a relative one a bit downstream (you can’t heat the river to 20 when it’s freezing).

These heatwaves reduce the margin from both directions, a hotter intake means you have less margin on the outflow, and the lower flow rate means there’s less water to dilute that outflow. And apparently for that specific plant there’s also the water level not even reaching the intake.

The reactor absolutely is not going to care, it’s the tertiary cooling circuit cooling for the steam turbines, it will have cooked off everything downstream long before it’s an issue.

This is entirely an ecological and safety concern.

Is there also a webhook? I don’t fancy busy-looping on dozens or hundreds of PRs for tools with large scopes of overview.

Also what about external merges? Is there a way to sanely interact with stacks when merging locally or via external tooling?

Does trunk use GitHub’s api to merge stacks, or does it do the integration internally / on its own?

> With pull requests, you can independently review and check each commit inside the pull request, and then merge the entire pull request in one click

Except you can’t really do that on GitHub, the “unit if review” is the PR so reviewing commits is adhoc, inconsistent, and awkward, and tracking their changes as they get fixed up is a pain. “Splatting” that as PRs is not the nicest way to do it green field, but it’s an evolution that makes sense in GitHub’s model.

> There's an internal system we have called CPRMC (Create Pull Request Merge Commit) that is used to evaluate whether a PR is "ready" to merge. This covers everything from mergeability (checking for merge conflicts) to rule evaluations (ensuring that approvals match the potential commit that will be created by merge) and more.

By the way could there be a way to disable that when doing integrations externally? It seems to be quite costly (which makes sense), and the pull/ refs kinda bloat the reflist.

I’m sure that external integration is not exactly beloved internally but there’s really just a small handful of big annoyances which would make it so much nicer and more comfortable.