An enterprise shop I co-op'd at was porting one of their apps from Xamarin to MAUI when I worked there, but certainly it doesn't have much mindshare (if any) amongst SE undergrads at my university.
All dependency management is speculative. You've got to hedge your bets that the dependency is reliable and fit for purpose. It is reasonable to view Bun's recent choices as increasing the risk associated with depending on it.
I like mine. the moto g line of phones are like $200, unlocked. They're fast enough for anything I do with a phone. It runs android. It's fine. I've thought about GrapheneOS before but I a) don't want to give Google money to rely less on Google and b) Pixels are expensive. If Motorola can change those points then I'd definitely be interested.
This one misses the point entirely, I'm sorry to say. Microsoft 365's "lunch" is that a majority of US businesses, schools, and governments are reliant on 365 for anything in their organization to function.
I thought so too at first, coming from a language (Hare) where they are very easy and common, but the Diagnostics pattern isn't that bad once you expect it. Various examples: https://ziggit.dev/search?q=Diagnostics
When talking in terms of software parallelism, "parallel" and "sequential" are more common to describe, for example, multi-threaded vs. single-threaded implementations.
It says the first half of the advance would be paid on approval of the first third of the book. It also says that the first third of the book was never submitted. So I don't think the advance was ever paid out.