Jonathan Willing

@willing
282 Followers
225 Following
135 Posts
@mark I also like my Homey. less capable than hass, but ultimately it *just works* which is precisely what I want in a drama-free smart home.
@vanvoorden we’ve certainly thought about it! we have some novel approaches to SwiftUI that I haven’t seen much of in the wild. maybe someday we’ll find an avenue to share more.
proud to have led the team on this. want to come build the next generation autonomous ride hailing platform? come join my team: apply or message me.
- ios: https://careers.withwaymo.com/jobs/senior-software-engineer-marketplace-booking-ux-ios-mountain-view-california-united-states
- android: https://careers.withwaymo.com/jobs/android-engineer-booking-mountain-view-california-united-states
Senior iOS Engineer, Booking - Mountain View, California, United States

Waymo is an autonomous driving technology company with the mission to be the world's most trusted driver. Since its start as the Google Self-Driving Car Project in 2009, Waymo has focused on building the Waymo Driver—The World's Most Experienced Driver™—to improve access to mobility while saving thousands of lives now lost to traffic crashes. The Waymo Driver powers Waymo’s fully autonomous ride-hail service and can also be applied to a range of vehicle platforms and product use cases. The Waymo Driver has provided over ten million rider-only trips, enabled by its experience autonomously driving over 100 million miles on public...

Waymo

next generation of Waymo booking flows rolling out.

lots of cool new tech here: flexible server-driven platform, fully native SwiftUI + Compose app components.

@dlx I’ve seen this one too. One workaround I’ve used is to always apply a fixed vertical size to the body of the inset view.
@dlx I usually work around this by just having each container pass down it’s safe area insets via a separate environment value (e.g. the root view describes the device safe area insets). Still a little clunky.

@schwa secret hack they don’t want you to know: you can create a pseudo-lazy Layout by wrapping each individual subview in a LazyV/HStack.

the subview attribute graph is unfortunately still evaluated due to the nature of Layout, but the render tree is lazy.

@harshil I tried and failed. the APIs just don’t exist.

the only option seems to be to use a UITabBar in a representable.

@kyleve amazed to hear this is still a problem. it’s the sole reason that I switched to Spotify literally a decade ago (though Spotify has plenty of different issues).
@dlx that’s one aspect of kotlin that I enjoy