A Swift concurrency pattern I’m seeing more and more is the “stateless actor”. This is fascinating, because it seems so counterintuitive. But I think people are reaching for this to get convenient access to background processing.
I don’t think this is “wrong”. But I think it is probably building bad habits. Local, private nonisolated methods are usually simpler and better long-term.
@dgregor79@mattiem@dimsumthinking removing isolation sounds like breaking the security assumption. would you say otherwise? (it just sounds like bad thing?)
I noticed my disk storage went drastically low and I started to check system, then I realized something ( #macos update???) enabled iCloud Photos synchronization to my Mac (that can take all the storage it get, and for that very reason I didn't enable it on my mac)
I am seriously thinking about alternatives to #Gmail. Not that I plan to take any actions anytime very soon, but because I no longer have faith that #Google will keep it operational as it currently is for all that much longer under their current management. Best to plan ahead.
After a day with 13in MacBook Air M2, I’m really amazed just how light and silent this thing is. Last MacBook I had was 2016 MBP that feels way more heavy than it really is.
This will be really nice travel companion for next decade.
I want to join The Browser Company just to fix the bodgy focus rings on their custom buttons in Arc, and then I'd fly off into the night like a vengeful, bug-fixing Mary Poppins.
@mattiem it says it execute on main dispatch queue, which runs on main thread. that’s why UI enqueued on MainActor runs on main thread. I don’t understand what are you talking.
@mattiem is not a main thread, it executes on main thread, which makes not much difference in practice if enqueue on the same thread. just like main queue is not a thread, but in practice special queue that runs on amin thread