Now up to two real-world sightings, and I love them

It's not perfect, but this is much more useful at least.

bryan says it's more about the power efficiency but we all know it's so we can put oxide racks in our bedrooms and still sleep at night

👀

Building a visualizer for Cargo codegen unit graphs. It's going great

C# is getting a stronger "unsafe" keyword! All callers of unsafe code must either be unsafe themselves or "discharge" the unsafety with a warn-if-missing safety comment.

The Fleet Foxes were a really mixed bag. They sounded great, but between each song Robin Pecknold kept chatting with friends of his in the front rows. He also tried to take a request for a song that wasn't on the set list, did a bit of the intro, and then admitted he didn't remember the rest.

🚨 GO PROPOSE A TALK ON OPEN SOURCE SUSTAINABILITY RIGHT NOW 🚨

Just stopped myself from buying another novelty domain name. Please clap

Iron & Wine Fleet Foxes Bon Iver Green Day Weezer Fall Out Boy My Chemical Romance Bring Me The Horizon Phoebe Bridgers Paramore

Does Rust actually guarantee wrapping for overflow in release mode? The language reference doesn't commit to it, though the intro Rust book and common folk wisdom says that's the guaranteed behavior. Wondering how reliable that guarantee is long-term. doc.rust-lang.org/reference/ex...

Ugh, I hate the word "simple" in software design discussions. Here are two espresso machines, the Flair 49 Pro (the black one) and the Breville Barista Express (the silver one).

The Secure Supply Chain Consumption Framework (S2C2F) could use some updates

I hope this feed makes it easier for people to ask questions and get help with #jj-vcs on here! I love crawling the Rustlang feed to find questions to answer, and will be doing the same with this feed.

Like #jj-vcs? Check out this new Jujutsu feed! It should pick up all posts tagged with #jj-vcs and include posts that appear to be about Jujutsu.

At this point we should treat C++ the way we treat Fortran or Cobol. Legacy, unavoidable in some systems, yet to be replaced as soon as possible.

Heads up maintainers of packages, this is a big deal: github.com/orgs/communi...

For OSS consumers, with AI accelerating vuln exploit timelines and supply chain attacks getting more common, the choice is either... 1. Rapidly make informed patch decisions (dep cooldowns or "just patch" aren't enough) 2. Accept the risk So, how expensive is "too expensive" for your OSS deps?

Edited and improved the interop chapter of my error handling guide: nrc.github.io/error-docs/r...

Testing testing #jj-vcs

This corporate apology should be studied. 1) takes clear accountability, 2) explains *why* it happened, 3) doesn't talk down to users, 4) makes clear that parts of this system are out of their control, and that Stripe-level issues will continue, 5) makes clear that more rule changes will come.

As we all know, the first web outage happened on December 7th, 2022, one week after the release of ChatGPT.

We started building @hipcheck.mitre.org in the summer of 2019. I remember reading this paper when it came out in 2020, and this conclusion has only become more correct since then.

Check this out if you're at RustWeek! Like it or not, technology *is* political. Aeva's been in the trenches of that intersection for years, and there's no one I'd want to hear from more about it!

AI shortening time-to-exploit? Update immediately! Software supply chain attacks getting more common? Put a dep cooldown! ... wait

many people are saying

The "1" column is indefensible; AI demonstrably produces value for at least some users. The "B" row is indefensible; AI alignment / existential risk positions presuppose their conclusions (among many other flaws). The "2" and "3" columns aren't exclusive. AI is both powerful and likely overhyped.

Memory safety wins again

I recently wrote an AI policy for a software dev team I'm leading, and this is one of the first sections in the doc. (Anyone else feel free to steal / adapt this)

Just a little PSA- Neil Gaiman has reactivated his Bluesky account. Because he deactivated before a lot of people could unfollow him, and/or because Bluesky doesn’t remove you from a person’s followers when you block them, a LOT of you are still publicly listed as following him. You should check.

Sanderson Cosmere read-through update: finished Mistborn Era 2! ✅ Stormlight Archive books 1-5 ✅ Mistborn Era 1 ✅ Secret History ✅ Mistborn Era 2 Still to do: Elantris, Tress, Yumi, Sunlit Man, Emberdark, various short stories and novellas.

It's easy to fixate on AI here, but companies have been pursuing ways to 1) automate work away (like the AI ordering system in the article) and 2) individualize everything for years. This is emblematic of AI being a continuation of the Long Industrial Revolution, rather than a new revolution.

Printers are truly our most cursed consumer computer artifacts

The Dodgers? Hitting? It’s more likely than you think!

🚨🚨 STABLE TRY TRAIT MENTIONED, THIS IS NOT A DRILL 🚨🚨

Of course the usual thing will happen: the cost of PHP developers will rise! If there are few people to do an essential task, those people get more expensive. Maybe LLMs apply downward wage pressure, but since that affects all software devs I'd expect PHP devs to be impacted less than non-PHP peers

thread

"It would be very bad if I got sick, therefore I will not get sick," I say as I lick another doorknob.

Second paragraph "the dream of the '90s is alive" activating me like a sleeper agent for Portlandia

anyone else have a guide for this?

We should heavenban all CEOs to a platform full of AI readers so we don't have to see this stuff.

People in the moderation discourse really need to distinguish behavior that's interpersonally objectionable vs. behavior that's actually against the rules.

Do your thing #jj-vcs people!

Aaron is right, and of course the top comment is someone continuing to harass him with a screenshot of their own Trust & Safety punishment for a prior instance of harassing him.

When I buy an Oxide rack

Rust PSA: ranges are iterators and have weird cloning behavior. There's an approved RFD and WIP implementation of new range types with fewer footguns:

With cargo-dist the generated CI code for releases has a comment apologizing for how messy even a basic "if/else" is in GitHub Actions' YAML.

I've discovered it: the baddest color

"Showcase mode" is pretty neat