The current concurrency series from @pointfreeco is really good
Last week's deep dive into threads is worth the whole subscription fee, awesome work, looking forward to the continuation!
@objcio I want to buy your 'Thinking in SwiftUI' book. Should I wait for the new version to come out, or can I buy the current version with a free update when the new one comes out?
@azamsharp I am for WFH (been doing it for 2 years now) but do you think there should be any limitations to it?
For example, what about companies in low cost/salary areas, that won’t be able to attract local talent because they can be better paid remotely?
A note on working with SF Symbols in SwiftUI: don’t use `resizable()` modifier. Image returned from `resizable()` is no longer a symbol image.
Use `font()` modifier to resize the symbol or `imageScale()` to set the scale relative to the font size.
Swift Tip 💻
I've always loved Swift's way of handling optional values.
Did you know that in Swift 5.7, we'll have a new shorthand for unwrapping?
#ios#swift#programming
"When determining the size or complexity of a new habit ask yourself, "What can I stick to—even on my worst day?"
Start there. Master the art of showing up. Then advance."
- James Clear, author of Atomic Habits
Lesser know, useful Xcode shortcuts:
- ⌃0 (Control-0): Choose Scheme
- ⌃⇧0 (Control-Shift-0): Choose Destination
- ⇧⌘J (Shift-Command-J): Reveal in Navigator
- ⌘⌃F (Command-Control-F): Toggle fullscreen
The last one is a Mac shortcut, but useful nonetheless
@jordibruin@dvrzan The biggest problem for me is the fact that NavigationLinks are tightly coupled to the view. If you want to reuse a view with a NavigationLink and have this NavigationLink be agnostic about the view it presents, you run into a roadblock
@pointfreeco Very interesting work. One question: are you going to tackle the current tight coupling of destination views in navigation links? Use case: re-use a view with a navigation link, and make the destination view of the navigation link different for each re-use