What’s the sense on mastodon lately? I feel like the core concept is also its Achilles heel in that with all these disjointed communities it’s really not a community at all.
renewedrebecca 12 days ago [-]
It's not very community-like out of the box, that's totally true.
OTOH, after you follow both people and hashtags, it feels pretty much like everything else, more or less.
jonquark 12 days ago [-]
It's the only social media I still use.
I don't notice "disjointed communities" I just look at the posts from people I follow without knowing which server they are on. I'm aware you can see a list of posts on your local server but I imagine people on most instances (unless the instance has a strong theme like for people from a particular location) never use it.
pixxel 13 days ago [-]
[dead]
thephyber 13 days ago [-]
New iOS (XCode) developer here.
Do you have any pro tips for optimizing workflow, reducing toil in XCode, or speeding up UI testing?
grishka 13 days ago [-]
It does look nice.
I can't seem to figure out how to open posts and profiles though. Neither single nor double-clicking does anything. Sometimes double-clicking a post that contains a link would open the link in the web browser. The only thing that works is right click -> open in new window. MacOS 14.7.5 (23H527)
anosidium 13 days ago [-]
Thanks!
Yes, that’s intentional — to view a thread or profile, use the contextual menu (right-click or control-click). Clicking is reserved for posts that contain a link or preview card, which will open in the browser.
dlachausse 13 days ago [-]
Always great to see native macOS apps! Is there a reason you aren’t using SwiftUI for the whole thing and that you opted for Core Data instead of Swift Data?
wpm 13 days ago [-]
Swift Data is CoreData in a wrapper.
Also, not OP, but I’m glad it’s written in AppKit vs SwiftUI purely; AppKit just feels better on the desktop. I can always “smell” a SwiftUI app just like I can an Electron app.
drcongo 13 days ago [-]
If the Settings app on current macOS is SwiftUI, then I can too. It's horrible.
sgt 13 days ago [-]
Never thought of that. Is that why the Settings app is so slow? If I click on one of the menu items on the left, it takes half a second or more to load the screen.
galad87 13 days ago [-]
SwiftUI doesn't help, but each panel is a separate process. The previous version of System Preferences hid the delay by showing an animation, the new one doesn't.
zerkten 13 days ago [-]
Why is a separate process necessary here?
pvg 13 days ago [-]
You don’t want login settings, cursor blink rate settings and random app settings running in the same process
kstrauser 13 days ago [-]
Why? Is there a mechanism by which one of those would be able to interfere with another?
pvg 13 days ago [-]
Yes, the mechanism of “memory access”.
sgt 12 days ago [-]
I still think they could easily load quicker though. Even switching between the different menu items in Settings takes long, when going back to ones that you already used earlier. They don't seem to be doing a lot of caching. At least they could keep those processes running for a while.
Unless it's actually SwiftUI taking time to render that UI, which would be bizarre.
As a macOS user I am so used to everything happening in the blink of an eye, so this is something that stands out. It's really not a big problem, 300-400ms.
kstrauser 12 days ago [-]
Ok, let me rewind a little. Are preference panes actually running apps? I imagined them more conceptually similar to an HTML form that System Settings displayed and processed and then wrote the results back to a plist or whatever. And in that model, there wouldn’t be a clear advantage to having separate processes.
Was I imagining that wrong?
pvg 8 days ago [-]
Yes they are more applike than UI-definition-like.
tough 13 days ago [-]
Search is also broken af raycast saves me from going mad
anosidium 13 days ago [-]
Thanks! I’m glad to hear that.
It’s an AppKit-first app — I’ve used SwiftUI in parts where it fits well, but I’ve avoided relying on it entirely because it’s still maturing, especially on macOS. In certain areas, it can compromise the native look and feel, or introduce unexpected behaviour.
As for Core Data, it’s a proven and robust framework that already does everything I need. Swift Data is still relatively new and doesn’t yet offer the same level of flexibility or stability for more advanced use cases.
aegypti 13 days ago [-]
Towards the end of COVID lockdowns I wrote a small, native macOS replacement for Zotero and ended up having to go with AppKit. Bit disappointing to hear the look and feel of a Mac assed mac app still hasn’t been replicated in SwiftUI.
Do you write about your experience with macOS dev at all? I would love to hear about it. I still look back fondly on that experience and toss around the idea of revisiting it, Documentation Archive and all.
noiv 13 days ago [-]
I like the Mac integration and all the features in the menu. Did I miss bigger fonts somewhere?
anosidium 13 days ago [-]
Nope. I will add this feature in future updates.
mountainriver 13 days ago [-]
The link goes to testflight?
anosidium 13 days ago [-]
Yes. It's not on the Mac App Store yet.
andrewmcwatters 13 days ago [-]
Nicely done, looks good!
anosidium 12 days ago [-]
Thank you!
techlatest_net 13 days ago [-]
Thanks for the TestFlight invite! I’ll install the iOS build and keep an eye on performance, UI responsiveness, and any crash logs. Happy to send feedback through the TestFlight app if anything comes up.
internetter 13 days ago [-]
Why isn't it open source? Ice Cubes is pretty good and FOSS
renewedrebecca 12 days ago [-]
Then use Ice Cubes. Not everything has to be FOSS.
AlexeyBelov 12 days ago [-]
What's the argument against it?
13 days ago [-]
zimpenfish 13 days ago [-]
Alas, fell at the first hurdle by saying my Akkoma and GotoSocial instances aren't valid.
anosidium 13 days ago [-]
Could you please give me some instance URLs so that I can check?
FediDB doesn't track GoToSocial servers, because of a dispute about scraping/crawling.
rglullis 13 days ago [-]
I guess that's been solved, because you can go to https://fedidb.com/servers and there are ~10 GtS servers being listed, all of them on the newest version.
anosidium 13 days ago [-]
Is there a better source that tracks a broader range of Fediverse servers? At the moment, my app officially supports Mastodon, though I’m aware there are derivative forks and other compatible implementations.
anosidium 13 days ago [-]
Thanks, that's helpful!
zimpenfish 13 days ago [-]
Added a couple of mine to the issue I filed earlier.
Rendered at 19:07:37 GMT+0000 (Coordinated Universal Time) with Vercel.
OTOH, after you follow both people and hashtags, it feels pretty much like everything else, more or less.
I don't notice "disjointed communities" I just look at the posts from people I follow without knowing which server they are on. I'm aware you can see a list of posts on your local server but I imagine people on most instances (unless the instance has a strong theme like for people from a particular location) never use it.
Do you have any pro tips for optimizing workflow, reducing toil in XCode, or speeding up UI testing?
I can't seem to figure out how to open posts and profiles though. Neither single nor double-clicking does anything. Sometimes double-clicking a post that contains a link would open the link in the web browser. The only thing that works is right click -> open in new window. MacOS 14.7.5 (23H527)
Yes, that’s intentional — to view a thread or profile, use the contextual menu (right-click or control-click). Clicking is reserved for posts that contain a link or preview card, which will open in the browser.
Also, not OP, but I’m glad it’s written in AppKit vs SwiftUI purely; AppKit just feels better on the desktop. I can always “smell” a SwiftUI app just like I can an Electron app.
Unless it's actually SwiftUI taking time to render that UI, which would be bizarre.
As a macOS user I am so used to everything happening in the blink of an eye, so this is something that stands out. It's really not a big problem, 300-400ms.
Was I imagining that wrong?
It’s an AppKit-first app — I’ve used SwiftUI in parts where it fits well, but I’ve avoided relying on it entirely because it’s still maturing, especially on macOS. In certain areas, it can compromise the native look and feel, or introduce unexpected behaviour.
As for Core Data, it’s a proven and robust framework that already does everything I need. Swift Data is still relatively new and doesn’t yet offer the same level of flexibility or stability for more advanced use cases.
Do you write about your experience with macOS dev at all? I would love to hear about it. I still look back fondly on that experience and toss around the idea of revisiting it, Documentation Archive and all.