Before macOS 26 I would have agreed with you. But after Tahoe my M1 MacBook Pro feels a lot slower.
Funny, there's even some regression in layer backed NSView rendering where the app I'm working on is faster (in some aspects) in a macOS 15 VM than on bare metal under macOS 26.
Heh, funny. I recently implemented a countdown for a teleprompting app and that's exactly what I ended up doing to make the countdown "feel right".
The countdown in question doesn't display fractions of a second so it would immediately switch from "5 seconds left" to "4 seconds left" which just doesn't feel right. Adding 0.5s solved the issue.
If you're counting up, round down. If you're counting down, round up. A human expects the count to finish at precisely the moment we get to the last number in the sequence (zero, for counting down). Do a count in your head to see what I mean.
Apple chose a compromise by rounding to nearest, for it to "feel good", but you lose the ability to exactly predict when the timer ends as a human. Typical Apple.
Copying the abstract here, just in case anybody don't have access:
Emily Austin, Hilary S. Myron, Richard K. Summerbell, Constance A. Mackenzie,
Acute renal injury cause by confirmed Psilocybe cubensis mushroom ingestion,
Medical Mycology Case Reports, Volume 23, 2019, Pages 55-57, ISSN 2211-7539,
Abstract: Psilocybe mushrooms are consumed for their hallucinogenic properties. Fortunately, there are relatively few adverse effects associated with their consumption. This is the first reported case of acute kidney injury (AKI) secondary to confirmed ingestion of Psilocybe cubensis mushroom. A 15-year-old male developed symptomatic AKI 36 h post-ingestion of Psilocybe cubensis mushrooms. He was admitted to hospital with hypertension, nausea and abdominal pain and a creatinine of 450 mmol/L. A sample of the crop of mushrooms was confirmed by mass spectrometry to contain psilocin. On day 5 post-admission, he was discharged home. Outpatient follow-up confirmed complete resolution of his renal function.
Kind of a cool read. They're not really sure why the P. cubensis was nephrotoxic. The sample they put through mass spec didn't contain the compound (Orellanine) that the clinical presentation lined up with, and none of the other youths who ate from that crop of mushrooms had subsequent problems.
I wonder if there was an accidental polyculture issue, either with a different mushroom or a freak mutation that caused that particular shroom to synthesize toxic compounds. When growing directly from spores, you get mixed genetics, so your various mushrooms will grow slightly differently (if you want consistent genetics you grow clones from an isolate via agar plate or tissue sample from fruiting body).
How did you get out of your photography obsession? Because currently I’m really really into photography as well and it gets unhealthy. (Both time and money wise).
I think Rust speaks to people who don't "play" with their code during development. Moving stuff around, commenting things out, etc. When I try to do this in Rust, the borrow checker instantly complains because $something violates $some_rule. I can't say "yeah I know but just for now let's try it out this way and if it works I'll do it right".
I work this way and that's why I consider Rust to be a major impediment to my productivity. Same goes for Python with its significant whitespace which prevents freely moving code around and swapping code blocks, etc.
I guess there are people who plan everything in their mind and the coding part is just typing out their ideas (instead of developing their ideas during code editing).
That might be true. In my case, it is precisely because I do play a lot with my code, doing big 2-day refactors sometimes too. With Rust, when it finally compiles, it very often tends to run without crashing, and often correctly too, saving me a lot of debugging.
But it's also because of all the things I'm forced to fix while implementing or refactoring, that I would've been convinced were correct. And I was proven wrong by the compiler, so, many, times, that I've lost all confidence in my own ability to do it correctly without this kind of help. It helped me out of my naivety that "C is simple".
You eventually don't even think about the borrow checker, writing compiling code becomes second nature, and it also has the side effect of encouraging good habits in other languages.
> I guess there are people who plan everything in their mind and the coding part is just typing out their ideas (instead of developing their ideas during code editing).
I don't think there are, I think Gall's law that all complex systems evolve from simpler systems applies.
I play with code when I program with Rust. It just looks slightly different. I deliberately trigger errors and then read the error message. I copy code into scratch files. I'm not very clever; I can't plan out a nontrivial program without feedback from experiments.
reply