For #visionOS developers: As we approach first software update for #visionPro I want to add support for visionOS „Device Support" files in #DevCleaner - anyone could confirm me what is the format of the folder that contains them, if you can just DM me (or send via e-mail, contents of this folder if you ever used Vision Pro for development: ~/Library/Developer/Xcode/visionOS DeviceSupport
Is it just me that I use built-in #macOS#TextEdit basically all the time? It's set to "plain" text mode and I use to various kind of notes and temporary text, except code. I would love some improvements for this app in the future!
There's something iffy with (all? most?) native #SwiftUI apps on #macOS
In theory - they look ok, controls are native, but "something" feels wrong wih them: they're usually slow, with some weird margins and behaviors sometimes, with choppy scrolling, etc.
@kkolakowski Yeah, as the rare macOS-only SwiftUI developer, I agree with you
SwiftUI is a framework for iOS first, and macOS is just tackled on. There are so many macOS things that don’t work properly or at all: sheet resizing, window animations, etc.
In my app, Cork, I have a sidebar that can have hundreds of items. For some reason, when you right-click one of the elements, it takes a few seconds to just open the context menu
Could anyone tell me why XML apparently is "banned" as a viable data format now? 🤔 I have a feeling that absolutely no new project is using it.
For some use cases it fits much better than JSON for example, yet everyone treats it like some kind of "legacy" and "unusable” format for some reason 🤷♂️
@krzyzanowskim Those are very good points indeed... That's probably how cycles in tech works 🤷♂️
Even in Swift we have JSONSerialization for Codable types in stabdard, yet any kind of XML serialization must be provided manually or by third-party libraries.
I'm not saying that JSON is worse in general, as it's probably (a bit?) better in some cases (config files, API responses?) - but for some other things, for example to describe a UI, or a document - I would still use XML.
It's quite obvious for #iOS developers that #Swift compiler is SLOW 😔
But how slow? I made a toy project that tries to (naively, I admit) compare compilation speed of a few compiled programming languages: C, C++, Go, #Rust and #Swift 🤓
For those who have to deal with time/dates in Swift (or Obj-C), in a little bit more advanced way than just parsing/displaying them - this is great article that details not only how, but also "why”.
Date & time is incredibly hard problem for CS, and do not try to „outsmart” it, by creating wrappers & abstractions over what might seem to be too verbose. It'll bite you!
FYI guys, Swift 5.7 introduced Clock protocol and Duration type that are great improvements over the good-old TimeInterval, and finally a "proper" way to measure performance.
One thing that is missing and should be added to Foundation (TimeInterval is part of Foundation) is conversion from Duration to TimeInterval - not a hard thing to do, but could be helpful.