Got in our
@Zipcar
we've been driving for 3 days. It doesn't start. Call Zipcar and get told that the car can't access the internet so it won't start. The only option is to have a tow truck come and tow it to somewhere where it has internet.
Today I'm super excited to launch the Mobile Native Foundation! Its goal is to improve large scale mobile development. Learn more about it and how to get involved:
The App Store connect API has some very specific errors:
{"status": "503", "code": "SERVICE_UNAVAILABLE_ERROR.DISABLED_FOR_WINTER_SHUTDOWN", "title": "Winter shutdown enabled.", "detail": "Winter shutdown in progress."}
New as of git 2.15:
git diff --color-moved=zebra
To show moved lines different from adds/deletes. Set permanently with:
git config --global diff.colorMoved zebra
We just open sourced a library, primarily written by
@kastiglione
, for consuming Swift's index data. We're currently using it internally to discover unused code. Hopefully it lowers the barrier of entry for writing more powerful semantic analysis tools!
After nearly 9 years(!) at Lyft I've decided to move on. I feel so lucky to have worked with so many great folks over the years on such a wide variety of awesome projects. I'm excited to take a few weeks off and then share what's next for me!
Reminder: most "crazy" technical decisions you see from the outside are made by engineers just like you, making fine decisions, under different constraints
> Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.
Announcing Keith Smiley
@SmileyKeith
from
@lyft
. He will be speaking at
#BASwiftable
this November 🗣‼️
🎟 Don't forget to get your ticket
⚡️ Ask your local community for discounts!
I wrote a small tool for recursively inspecting your binary's dynamic dependencies. I've found this useful trying to understand where specific library dependencies come from.
Over the past few years
@kastiglione
and I have been using a stacked-diffs style workflow with GitHub. I finally split this out of my dotfiles and pushed it to its own repo, complete with a detailed explainer
The project I worked on for the longest time at Google (rules_apple) has officially switched to community maintenance with
@SmileyKeith
leading the effort. Really happy there's a concrete plan for OSS support for the rules. Lyft's investment in OSS is highly commendable!
Periodic reminder that not everything we use has to be built by Apple. Even the things that are can have downsides like:
- slow evolution
- potential to be untouched for years
- limited flexibility
And in the meantime the community gives up on solving it ourselves
Whether or not you "like" CocoaPods it continuing to exist is extremely important for the iOS community. Huge props to
@dnkoutso
for sponsoring it personally and now to
@PSPDFKit
Got sourcekit-lsp working in Vim with one of our SwiftPM projects. Jump to definitions and find references work amazingly well! I'm so excited to use this
Interesting new things in Xcode 9.3b1:
- SwiftCommandLine.framework, appears to be a Commander like framework
- ProvisioningProfileQLGenerator, a replacement for
- usr/bin/simtest, appears to be a utility for testing the simulator itself
Early takeaways as a user of the iOS 13 beta:
- dark mode is great
- new share sheet is awesome, it saves multiple taps and some typing for me every time
- swipe keyboard is great, switching back and forth with third party keyboards was always weird
- it has been stable
I wrote a small CLI for those times you want to extract libraries from the dyld shared cache but don't want to build dyld itself (or want it to support beta OS versions)
So, there was a library called Javaslang, now its "Vavr"
It had a class named "λ".
Obviously, our build fails with this:
```
java.nio.file.InvalidPathException:
Malformed input or input contains unmappable characters: javaslang/λ.class.Rule
```
just kill me already
Interesting to see SwiftNIO and SwiftGRPC drop support for CocoaPods
I wonder if other projects will follow because of this precedent, or if the community will continue to maintain the podspecs.