bardi

4 ms·

1. 1.▲
   Show HN: Tab-da, a keyboard-first Chrome extension for people with too many tabs(thirdculture.app)

   1 points by bardi 3mo ago|1 comments
2. 2.▲
   by bardi 4y ago

   Great question. I don’t think I have an answer that will satisfy you. Our natural instinct was never to revert to UIKit because we have no experience working with it. This combined with the fact that our problems built up gradually over tim
3. 3.▲
   by bardi 4y ago

   Thanks so much for the kind words! Okay, so a few things: 1) we’re still in beta, and so we’re aware that the experience still has room for improvement in terms of optimisation. We’ve made big strides recently, but there’s still ways to go
4. 4.▲
   by bardi 4y ago

   The one other thing I’d add as being a major source of frustration and anxiety is SwiftUI’s update cycle. It’s acceptable for there to be issues in any technology, whatever its age, but it’s not satisfactory to need to wait 12 months for th
5. 5.▲
   by bardi 4y ago

   You’re right, you shouldn’t have to but it seems to be a penalty you currently have to pay if you go all-in with SwiftUI at this stage in its lifecycle. Admittedly, it’s still relatively/technically immature compared to its predecessor
6. 6.▲
   Every Question/Answer from Apple’s WWDC 22 Design and SwiftUI Digital Lounges(blog.timing.is)

   1 points by bardi 4y ago|0 comments