@bigzaphod Somebody’s been busy!
"tired of how slow SwiftUI is” — given it was pretty performant before (I can only imagine the herculean effort required), this should be *very* nice.
Discussion
@bigzaphod Somebody’s been busy!
"tired of how slow SwiftUI is” — given it was pretty performant before (I can only imagine the herculean effort required), this should be *very* nice.
@montyhayter lol - a chunk of the speed comes from giving up on the idea that I was making a reusable component, so yeah, it’s like…. Really tied to Tapestry now. It’s also way more code. So.. I really hope this doesn’t backfire on me in terms of maintainability but at the same time, I’m sitting here with 5 year old devices at this point so the usual way of upgrading my way out of performance problems wasn’t working. 😛
@bigzaphod I was just looking at some code the other day that is “reusable”, but as needs and use cases have evolved it grown into this sprawling, awkward mess.
When I have time it’s getting redone as separate classes for each use.
Sometimes task specific (or more) is *more* maintainable.
And yeah, “upgrade out of performance issues” is something we can’t count on anymore… and probably shouldn’t have gotten in the habit of in the first place.
@bigzaphod …wow, that’s smooth 😍
Not that I could ever afford to the way things are going, and it’s probably way too tied to Tapestry’s specific needs… but if you ever consider licensing any of this, that’s a conversation I’d have — even though I have no money and usually avoid third party libs 😀
Maybe I’ll win the lottery. 🙃