Seems to me that the virtual filesystem is a bit of a hack (though quite a useful one), and therefore it's not macOS's fault for accidentally breaking this when the virtual filesystem doesn't behave to it as a storage device should. Still, given how widely deployed it is (Raspberry Pi Pico and other RP2040 boards, BBC Micro:Bit, DAPlink) and the difficulty of fixing it on the device end and having users update their devices, Apple should fix it on their end.

"So to be clear this is not a “UF2 problem” or a “Raspberry Pi” problem. The problem isn’t specific to UF2 files and the UF2 standard, and it’s not specific to Raspberry Pi devices. It will affect any device using a “fake” virtual volume, of which there are many. So this isn’t a Microsoft versus Apple problem, or a Raspberry Pi versus Apple problem, despite some conspiracy posts to the contrary."

For interest, an overview of UF2: https://makecode.com/blog/one-chip-to-flash-them-all

> Right now, if you’re using a Pico with your Mac, we don’t recommend upgrading to Ventura (at least not yet).

That seems a bit extreme, given how painless the `cp -X` and `rsync` workarounds are.

Pico devices are used by users of all ages and abilities. Drag and drop is easier and less scary that a terminal for those users.

UF2, not U2F (which is a different acronym)

Yeah, I made a typo, by the time I noticed I wasn't able to edit the title.

I think you can ask the mods to fix it via email hn@ycombinator.com