We need to parse this version in order to know which version of the PackageDescription library to load. By keeping it in a comment, SwiftPM can extract it with a lightweight scan, then select the right parser.

That is just wild. It's almost like you became the comic and the comics became the audience. Your storytelling, timing, "yes, and" are the equal of anyone on that stage. You can see that they almost didn't want to interrupt you because you were LANDING that. In awe. 👑

A likely story! I'll bet the other guy came off worse! Maybe you can go with a pirate eyepatch and a parrot on the shoulder? 🦜

I’m assuming that in addition to the great collection of crystals in your office, you also have a great collection of flight cases proudly displayed in your garage? 🤣

Congratulations to all of you!

It's an interesting question, and I don't have a good answer. A lot of folk I chat to are fatigued and demoralized, and there's a sense of fatalism -- this is what others voted for, so now they have to reap the whirlwind. There's also a lack of a leader to rally around at this point.

You really are the Taylor Tomlinson of Google. I follow you for the best takes on the current zeitgeist.

It's not too hard -- thanks for the request :) Now that we've published swift-build, we have a pull request open to integrate it into SwiftPM, at which point it's just one build flag away. More details here: github.com/swiftlang/sw...

I’ve never been particularly enthusiastic about Android 😜

Here we go!
youtu.be/EBLbRbvWPKc?...

You too, Thomas -- hopefully this year is one of happiness and new horizons for you. (And who knows, perhaps with a little Swift experimentation 😉)

Nice! I bought a WASD keyboard a few years ago, but I picked the wrong keycaps and I have regretted it ever since. But I'm determined not to get suckered into the endless search for the dream keyboard. I have too many keyboards already!