Hot take: SwiftPM would be better with TOML/JSON/YAML + public JSON schema instead of Package.swift.
Look at Rust's Cargo.toml. Static config eliminates compiler slowness without sacrificing DX. Editor support becomes accessible to everyone.
Most Package.swift files are static structures. Those doing I/O or reading environment? Anti-pattern, even when Apple does it.
Accessibility and performance matter.
Swift by Sundell is back! 😀
Some really impressive work from my teammate Kevin here: https://forums.swift.org/t/the-future-of-serialization-deserialization-apis/78585
If you care about Codable and/or serialization in Swift in general, definitely check it out
Hello Swift Community, I’m happy to announce that I've been hard at work planning a potential future for serialization & deserialization APIs in Swift. It's clear from community adoption and feedback that Codable has had a lot of success in the years since it was added to Swift 4, but that it doesn’t satisfy some important needs. One of the foremost of those needs is performance more in line with programming environments that compete with Swift. As such, the main goal for this effort is to unlo...
I won’t cease to repeat it. We chose Elixir for @tuist because it builds on Erlang, and the Erlang runtime is so powerful that we can spend our time building and not seeing a complex system emerge as our solution grows.
I don’t regret the decision a single time.
I had no idea that due to the way the #Swift type system is design compilation times are hard to optimize and errors messages to improve. Chris Lattner touches on it here:
https://www.youtube.com/watch?t=373&v=9ag0fPMmYPQ&feature=youtu.be
Massive improvements to UIKit are coming!
• Lightweight observation of models
• 2-way bindings for controls
• State-driven navigation
…and more!
Pedro Piñera
John Sundell
David Smith
Tuist
Pedro Piñera 
Point-Free