Hey guys, wanted to share a little insight on my app's custom runtime for SwiftUI: Kulve's SwiftUI runtime | Kulve
7 Likes
This is probably an amazing thing, but I have to confess I didn't understand the slightest of it. What exactly did you improve by that? Is it a blueprint for us to use in our apps or can Apple use it to optimize their use of SwiftUI?
And where exactly is the Swift-C++-interoperability coming into play?
Potentially it can be used to make SwiftUI cross-platform, if it works. @a-soll, it should be a huge amount of work, did you leveraged AI tools for this project?
no I did not leverage AI. AI isn't capable of doing something like this in my experience.
It's essentially a direct replacement to Swift's concurrency and memory management. by offloading that work to C++, SwiftUI is able to work with data at no cost. Which is a big win considering how much SwiftUI copies data when it comes to redraws.
I would say it's less of a blueprint and more something that would be used by SwiftUI behind the scenes. it completely abstracts away async/threading but it's not something that has a very formal frontend. that is, you still need to understand the low level part of it to really leverage it. that's mostly just due to the fact it's purpose built for my application, but going forward, it could end up being a framework for general purpose SwiftUI use.
2 Likes