Vince

@schwa@mastodon.social definitely. I actually liked the tab model they ended up with in Xcode 16.

Now you can't have the "0 tabs open" state anymore. And because the tab bar is only shown as soon as you have a pinned tab or more than one tab, the editor jumps up and down. This feels like a regression to me.

But will have to get used to it, I guess.

(Edit: Okay, at least you can enable "View -> Show Editor Tab Bar" so it's always visible, now bring back the 0 tab state)

@bigzaphod@mastodon.social @jeffmerola@mastodon.social @myell0w@mindly.social If it's implemented with custom actions, I *think* it will say "actions available" after reading the "main” accessibilityLabel.

@bigzaphod@mastodon.social true. my guess is that .task is just for short-ish things that are heavily tied to the view.

the docs state that the task is cancelled as soon as the view is removed or changes identity.

for longer running operations or things that need to keep running even if the particular view is gone, you would need to handle that in your model layer anyway and/or with the .backgroundTask modifier on Scene.

@bigzaphod@mastodon.social Couldn't you make the same argument for GCD?