Substitute for em dashes the inaccurate AI signal du jour. Then consider not posting about whether something is AI or not.

I seemed to have been through this pattern in my interests multiple times and just wait in the between times for something of interest. For hobby/interests I started with programming languages and then moved into understanding hardware and then mobile devices. I wrote HP 41 s/w, HP 48 s/w, the first public dethreader for HP 48 ROMs, Newton s/w, Windows CE s/w, jailbreak s/w and on device iPhone 1.0 s/w (pre App Store), but have been waiting for the next thing since iPhone 5 or so. In languages I went through a lot as well and now am waiting on C# to be improved.

I found C# exciting when it was new and adding features that were important to me, but now it feels like it has become bogged down with chunks just abandoned on the alter of backwards compatibility (Expression, anyone?) and adding features I couldn’t care less about (null safe code, pattern matching, etc).

Making allocators part of a type or scope instead of in every function call might be a start.

But for how many software domains are allocators more specialized than a single built-in general purpose one so important it should be the focus of your language?

“rapidly” - how long has it been?

We hired 3 experienced app developers a few months ago. That's now our app development team working on overhauling these apps. They've already replaced the entire Messaging app user interface with a new modern Compose UI. Messaging v13 is currently in the Alpha channel and v14 is on the way with a bunch of additional fixes needed for it to reach Beta and Stable. Multiple other apps including Contacts are well into the same overhaul process.

Feel free!

That might be valid (but not really) if those other OEMs actually didn’t delay the features and bug fixes themselves.

Sometimes market forces fail and it becomes the only choice.

This was literally a comment:

>GrapheneOS is not made for nerds, it is made for normal people.