Josh Asbury

Specialist Lead iOS Engineer (contributor Tech Lead) at Concentrix Catalyst // @GeelongCats // ❤️ waterfalls, beaches, sci-fi, and tech

[Josh Asbury @theoriginalbit]

@ToddLa @parrots They are, at least for simple colour + image based launch screens.

[Josh Asbury @theoriginalbit]

@aaron_pearce Damn 😞

[Donny Wals 👾 @DonnyWals]

In Xcode 14.0 Beta 2 Combine has received a super welcome update! They've added primary associated types to Publisher so now we can write "some Publisher<Output, Error>" instead of erasing to AnyPublisher!

Learn more about primary associated types here: https://t.co/j4PxAAWHAB

[Josh Asbury @theoriginalbit]

@pavm035 @DonnyWals Android’s compat stuff may be nice, but it’s also a mess!

[Josh Asbury @theoriginalbit]

@ziademarcus You should be able to do it with the “new” navigation bar appearance API too.

[Josh Asbury @theoriginalbit]

@art_garzajr @harlanhaskins But modern swifty ways would be an optional

[Josh Asbury @theoriginalbit]

@art_garzajr @harlanhaskins Yeah following apple’s Obj-C days you would return NSNotFound instead of -1

[Josh Asbury @theoriginalbit]

@art_garzajr You could very easily make this work with more than just arrays, could even work with non-contiguous collections of any type that conforms to equatable and comparable. with only a few changes.

[Josh Asbury @theoriginalbit]

@swiftbysundell FYI you have the same issue in your post. You use a SettingsConvertible protocol when you should just add buildExpression to your result builder to convert the single setting into a settings group. It ends up much cleaner and one less type with extensions in code

[Josh Asbury @theoriginalbit]

@twannl in your "Result builders in Swift explained with code examples" you introduce a LayoutGroup protocol to fix the variadic error. You can fix this with result builders without needing to muddy NSLayoutConstraint with the protocol conformance. 1/2

[Josh Asbury @theoriginalbit]

@twannl 2/2 result builders have a buildExpression designed for this purpose, and you can use that instead. The "Write a DSL in Swift using result builders" WWDC video covers this exact error and solves it with the expression builder. https://t.co/zUYp7QHPmz

[Josh Asbury @theoriginalbit]

@twannl How’d you go with exploring this? I opened the post today to share it and noticed it’s still using the LayoutGroup protocol when it could use buildExpression.

[Josh Asbury @theoriginalbit]

@bartonsmith @gelistirmen @mikaela__caron Maybe try this https://t.co/5WfBHf2ENq

[Josh Asbury @theoriginalbit]

@onmyway133 I like the details that this provides: https://t.co/Vh7WEwEppq

[Josh Asbury @theoriginalbit]

@DonnyWals The question is invisibles on or off, right? ‘Cause I live with them off. 😝

[Josh Asbury @theoriginalbit]

@kevinclark Also pressing it shows the sound waves and strike through on the volume HUD

[Josh Asbury @theoriginalbit]

@KingArix @kevinclark But other software indicators also don’t, here’s iOS’s HUD

[Josh Asbury @theoriginalbit]

@akaralar @DonnyWals @SlackHQ Even with an 85% discount that’s a LOT of money!

[Enid @ios_dev_alb]

⚠️ Don't skip UIKit!

If you are looking for an iOS developer job, I have one advice for you:

• Don't skip UIKit!

I know UIKit is hard to learn, but almost all apps are developed with UIKit.

P.S. With UIKit you will have more control.

#iosdev

[Josh Asbury @theoriginalbit]

@DonnyWals Not when we support iOS 12 😭

[Josh Asbury @theoriginalbit]

@_saagarjha @gonzalolarralde The screen minus the status bar.
Last I saw the screen corners and even the multitasking handle are considered “safe”