> Wouldn’t it be cool if we could just use standard OS threads, blocking APIs, avoid new shinies like io_uring, but still get to cancel any work reliably?
Wish more was said about this: why would that be cool? I get that having robust cancellation in standard threads is cool, but why do we want to avoid io_uring?
Programming asynchronous code is hard. Execution is split up, you have extra state machine to handle, extra resources to manage that need to survive across async boundaries. And by asynchronous, I mean either callbacks or manually checked completions from some event system. Modern languages hide that under async/await, which is much better from DX perspective, but still leads to split in the ecosystem, and it's hard to optimize across async boundaries.
This is an example why Go is such a successful language, in my view. It hides the async complexity and allows you to pretend you have a simple continuous thread of execution. It's just cheaper than system threads. Imagine if operating system threads and the blocking syscalls were this efficient.
I've spent the last year building a similar runtime for Zig. Purely because I want my applications to forget they are using things like io_uring in the background.
io_uring has been one of the greatest sources of exploits for the Linux kernel in years. io_uring has resulted in so many practical privilege escalation attacks that many containers completely block it, and companies like Google keep it entirely disabled. RHEL also ships a kernel without it by default.
I didn't see it touched on, but I'm hoping improved storage management is included in the update. My system has > 20% storage used by "system storage" and in total nearly half the device storage is used by ios and is outside my control. Supposedly some of this stuff is just cache data and there's no way to adjust what data gets cached or when it gets purged aside from rebooting. Handling for large files is also hit or miss and could use some updates. I didn't even realize some of that was AI stuff I might not even be using.
Yeah file management in general is still incredibly rough around the edges. I would still like to be able to simply grab files from my phone via a connected linux computer, but apple will never let me have that one.
>no way to adjust what data gets cached or when it gets purged aside from rebooting
Unfortunately the only current ways to pull this off is to either artificially move the current time years forward so it hits a time gate and dumps the cached files, or use enough space on your iPhone to force it to dump the useless cached files then delete whatever you used to take up space temporarily.
Won't weigh in on psychiatric care, but I will say from experience that everyone should look into both an advanced healthcare directive and an advanced psychiatric care directive: these are documents that authorize someone else to have input into your care if you are unable to do so yourself. Psychiatric care is considered separately so even though a medical health directive was in place we were stuck and could not have input into care even though we tried. Set this up before needed because in an emergency it may be too late and care providers are limited in what they can say and what they will do without that.
Consult a lawyer. Participating locations only. etc. etc.
We did at least have a health care proxy and a power of attorney in hand.
Funny story (that I didn't include in the blog) is that I actually wound up in a psychiatric facility for a second time after I was in-and-out of Brigham and Women's on 3 separate occasions. I was in a much better state mentally and physically, and this particular facility (McLean Hospital) was way better than the first one I was in. The circumstances were different and I was happy to be there because things were still very rocky at home. And very dark. So my wife and I felt it better that I be in an in-patient facility at this point, which came right before my official anti-NMDA receptor encephalitis diagnosis.
Anyway, the funny story is that I showed up to McLean, after being transferred from Brigham and Women's, with a physical copy of my wife's PoA over me and a health care proxy. The charge nurse said it was the first time he had ever seen anything like that before.
Oh dear! Medical issues are scary enough without all the red tape (has to be a better word than that) getting in the way of good care. Spreading the word in the hopes that it is more common and fewer people are left out
Thanks for sharing the story so openly! Sorry for everything you went through to get a proper diagnosis and treatment and for everything that the encephalitis itself inflicted on you. Glad you're doing better!
It used to publish the `model` values but found that so few repair events collected `model` values and the scant values that did turn up were not very useful. The data is compiled and published on a shoestring budget, so resources are very limited.
The purpose of the data has evolved over years as a response to and a source for various investigations and campaigns that feed into the European Right To Repair campaign. It is also used by individual repair groups and networks to demonstrate their work and achievements - both environmental and social - in order to garner support and funding. The main use of the dataset is as an overview of a glimpse of community repair activity worldwide.
> The tendency for people to get overwhelmed when they are presented with a large number of options, often used interchangeably with the term paradox of choice.
There's 30 "laws" which are all text-based content buried under 30 irrelevant pictures that up half the visual space on the page.
It looks pretty, but it isn't an effective way to study these.
Oh man! I came here to complain about printing! I just discovered yesterday that you can no longer drag and drop print jobs from one printer to another. Apparently you can move a print job via some command line stuff but it just ended up deleting the jobs entirely. The only reasons I found this out is because the printer which had been working fine moments before just stopped working after replacing toner. No amount of deleting and re-padding the printer or power cycling either machine fixed it. One time the whole OS just froze and I had to force reboot. I spent a good chunk of the afternoon trying to get one 3 page document to print. To be fair, I haven’t had problems with this setup for 10+ years but when it went south it also went to the remote frigid corners of Antarctica.
There's this line:
> Wouldn’t it be cool if we could just use standard OS threads, blocking APIs, avoid new shinies like io_uring, but still get to cancel any work reliably?
Wish more was said about this: why would that be cool? I get that having robust cancellation in standard threads is cool, but why do we want to avoid io_uring?