Jon

@twostraws It would be better if it could be used in function arguments. Then it’s more readable than using a ternary operato (at least some of the time, imo)

Back in Swift 5.9, if and switch were adjusted to work like expressions so you can assign their result directly to a variable. Clean and consistent, or hard to read? 🤔 hackingwithswift.com/swift/5.9/if-s…

@pepicrft @SwiftLang Swift keep implementing new things and not finishing them. completely assuming it’s because people jump on to the next cool compiler thing.

I’m very intrigued about what led to this: > Everywhere: Abandon Swift adoption @SwiftLang there might be some input there to learn from. github.com/LadybirdBrowse…

@Argos_Online im getting texts for a delivery and it’s not mine

Now we can use LLMs to write code I don’t understand why you’d chose python over Swift or Kotlin. Having compile time safety seems way more helpful than easy of writing

@jaredpalmer @github @georgebrock This is great! will it be able to automatically rebase the stacked PRs?

Stacked Diffs on @GitHub will start rolling out to early design partners in an alpha next month. In the meantime, here's video of our progress so far: (h/t for @georgebrock + team for their awesome work)

@TfL @Citymapper waterloo bridge is Closed but it’s not updated in both apps so buses are still shown as going there

@pepicrft @tuistdev Ah I had content blockers on that hid it from both tweets, thanks 😊

@Jon889 @tuistdev tuist.dev/blog/2026/01/2…

Flaky tests are a common source of time wasted, so it was a natural problem for us at @tuistdev to tackle. With a single action in your Xcode project schemes, you can now detect and quarantine the flaky tests in your codebase. tuist.dev/blog/2026/01/2…

@Hyperoptic can you just tell me the prices for your packages? the postcode checker is saying it’s not in my area but I literally have it already, I just don’t own the account.

@TfL staff member for the mildmay at Stratford just announced “platform 1 is the next train doors closing in 10s.” so everyone in the train in platform 2 (the one that was there 1st) ran across only to find the doors locked already. You need to sort out showing which one is next

theverge.com/tech/854556/le… I’ve seen Stargate SG-1 and how this goes 😂

@Sentry there’s no Apple/iOS option for creating a project?

@AvantiWestCoast I’m in the 18:50 from Milton Keynes and both staff members I’ve encountered so far have been fantastic!

@polpielladev I’ve only ever had performance issues the other way round. When the parents state changes the init is re-run on a new instance and the passed in child views all recreated. Storing it as a closure prevents the child views from being recreated

A common pattern for building flexible SwiftUI views is passing child views through an initializer as a closure. ⚠️ Be careful when doing so though, you should NOT store the closure itself in the view. Closures capture parent state (often self), so unrelated parent changes can cause the view to redraw unnecessarily. ✅ Instead, don’t mark the closure passed to the initializer as @escaping, call it in the view’s initializer, and store the resulting child view.

@TfL could you fix the jubilee platform departure boards in Stratford? also the departure board on the south side of the west subway is broken.

@LNRailway @WestMidRailway The heaters went off briefly for 10 minutes but are now back on

@Jon889 @WestMidRailway Hi there, unfortunately, we cannot alter the temperature of the train whilst the train is in service, apologies. -Ben

@LNRailway @WestMidRailway any chance you could get the heating turned off on the 16:46 from Euston to Crewe? It’s boiling.

@jacobtechtavern The could’ve given us a modifier to set a UIScrollViewDelegate on a ScrollView from day one and acknowledged it’s not very SwiftUI-y and then over the years refined a SwiftUI replacement… instead they only add functionality if enough people feedback specific use cases.

Delegates don’t actually suck. I almost cried last year when I touched UIScrollViewDelegate for the first time since 2019. I was building a cute interaction that animated a line of emojis along a circular path, with their motion along the circle linked to your scroll offset. I could trivially access scrollView.contentOffset.y from the scrollViewDidScroll(_:)delegate method. Do you know how hard this is with SwiftUI preference keys!? To be completely fair to SwiftUI, onScrollGeometryChange (iOS 18) can do this now. At the time, I was supporting iOS 17 and couldn’t touch it. But there are hundreds of UIKit delegate methods that remain unsupported, like scrollViewWillEndDragging(_:withVelocity:targetContentOffset:). Even if SwiftUI achieves parity with the full UIScrollViewDelegate, we are subjected to a combinatorial explosion of memorisation for new views, view modifiers, and their respective positions on the view hierarchy. Don’t even get me started on namespacing. You’re more or less allowed to apply every view modifier to every view in SwiftUI. It almost feels like… maybe delegates were actually quite a good pattern for implementing the iceberg of nuance underneath the world’s most complex UI system. Read “the year SwiftUI died” here 🪦 blog.jacobstechtavern.com/p/the-year-swi…

@jaredpalmer @github Don’t hide large diffs or make them more noticeable

How can we make @GitHub Pull Request and code review experience better?

I think my AirPods Pro 3 are broken because the ANC is worse and so is the fit. who decided to angle the buds more??