Yesterday, @GitHub announced Codespaces, a new feature that brings a full-fledged IDE directly to https://t.co/A4GbPG5pd4.
We just updated our articles about VSCode and Language Server Protocol with more information about about our Xcode-free future.
Earlier today, Apple released iOS 13.5 beta 1, which includes the first public release of the ExposureNotification
(née ContactTracing) framework.
We’ve updated our original article with information about the latest version:
It's become a truism among iOS and macOS developers that Apple's documentation is often incomplete or missing altogether.
But to what extent is this actually the case? With a bit of web scraping, I was able to come up with some numbers:
Last week on @NSHipster, we covered the 10 [NS]Formatter subclasses that app developers should know about — including 2 new (and as yet undocumented!) ones: ListFormatter and RelativeDateTimeFormatter.
I’ve always enjoyed technical writing, and today I am thrilled to contribute to a website I’ve learnt so much from throughout the years.
Also, huge props to @mattt for his excellent guidance and the crazy amount of love he’s pouring into @NSHipster. 🧡
I’m so happy to welcome @kaishin as the newest contributor to @NSHipster!
Reda’s write-up about UIStackView is a feast for the eyes and the soul — a must-read for anyone feeling down about their UIKit codebase since WWDC.
iOS API design, short history:
Objective C - describe all semantics in the name, the types don’t mean much
Swift 1 to 5 - name focuses on clarity and basic structs, enums, classes and protocols hold semantics
Swift 5.1 - @wrapped $path @yolo
Find me at the UIKit and Dark Mode Lab on Wednesday for help making your web content dark mode aware on iOS 13 and macOS Catalina.
Thanks for the showcase page @NSHipster! #WWDC19https://t.co/XV3YNebknf
SwiftFormat 0.39.5 is out, and is a recommended update for everyone. Fixes a longstanding issue with indenting of comment blocks, along with that pesky closing brace issue mentioned in the @NSHipster article :-) https://t.co/HdSGc2bV7B
For your consideration: a Swift type that constructs `Decodable` objects from regular expression matches by named and positional capture groups.
I can’t decide if this is a reasonable approach, or well into “Here be dragons” territory... 🐲