I'll bite. Why is it like this (in your opinion of course)?

Mostly the failing events (e.g. the Messages app failing to keep the first word of a message when typing rapidly after sending a message) are, I think, due to Apple using Catalyst for these apps.

Catalyst was an ambitious project, which works… mostly. But in the details, it has a lot of rough cuts. I fully expect Apple to end up rewriting Messages and co completely in SwiftUI eventually, but that will take many years, if they ever do it.

For the rest, most of the time my wild guess would be that Apple is constantly migrating their frameworks, or creating new ones, and the engineers developing apps are using ever moving frameworks. The framework stabilizes at the end of the release cycle (or sometimes even later…), which leaves no time for the front devs to truly finish quality control on their part.

Basically, to summarize, the release cycle is too small. Apple should do releases every two years instead of every year. Or drop the cycle altogether and just release when ready.

I agree, but I tend to find that "git diff aware syntax" also makes things simpler for humans as well

Do you have any favorite docs or blogs on these? Reading about one of the best designed permissions systems sounds like a fun way to spend an afternoon ;)

Looks neat! I highly recommend showcasing the interactivity with a few GIFs in your README. You can script them with https://github.com/charmbracelet/vhs

No

One language vs 3 or 4? And some folks REALLY like Rust

Yes (from the README)

Super impressive, can you link to this post in that issue?

I'd like to try iced, but switched to egui on the official Android support.

Until the book gets really good and you have to keep reading past your bedtime to learn what happens (or maybe that's just me)

It's not just you, I hear this often, but I am always suprised people can read for so long in bed. No matter how interesting a book is, I can rarely read more than 20-30 minutes before the urge to fall asleep becomes too strong.

But I can sometimes code until like 4AM. Weird.

Reading is usually more passive than coding. I'm often never sleepy if I'm actively coding something late at night but reading a book (no matter how engaging) or watching a tv show can very easily make me sleepy. That said, everyone's brains work very differently.

This is just so weird. In general coding won't let me fall asleep but a book 100% will never let me sleep until I finish.

I also find the idea of "forcing" yourself to read rather peculiar, but we're all different people. I wonder if there's genuinely something different in how the brain reacts.

Well you are sitting in front of a relatively bright lamp when coding.

This happens to me about once a year. I’m much more likely to stay up later than planned while doing other activities such as watching tv, coding, talking, social media, or spending time with my partner.

Anything true crime keeps me up. Same with many genre's like you said, but for some reason true crime always hooks me.

I read the Zodiac book by Robert Graysmith in less than two days over break in college. Could not put it down.

You might enjoy https://www.bitsaboutmoney.com/archive/seeing-like-a-bank/

It has a REALLY good section about why customer service is very hard to get right

I keep running into Gleam posts and podcasts and videos. I think it could be an especially attractive alternative to JS for UI with the Lustre library. Haven't tried it yet, my backlog is ever growing...