Keith Smiley

@buildbuddy, maintainer of @bazelbuild's iOS support, creator of @MobileNativeFdn. LLVM & Swift contributor. Previously Principal Engineer @Lyft, @modular

[Keith Smiley @SmileyKeith]

@steeve @zml_ai 💸

[Keith Smiley @SmileyKeith]

@steeve Yea you should upstream that. Stuff seems pretty dated

[Chris Lattner @clattner_llvm]

Wow, @llvmorg just passed half a million commits to the monorepo! Congratulations to all of the 3811 contributors so far!

If you love LLVM, consider star'ing the repo: https://t.co/GXyeKGXWvd

[Chris Lattner @clattner_llvm]

Wow that's right. This was a big day and Swift has come a long way in the intervening decade: Congrats to everyone who has driven it forward to support such an amazing tech platform! 🍎🐣

[Keith Smiley @SmileyKeith]

@bradysays @OpenSauceLive Nice!

[Keith Smiley @SmileyKeith]

@krzyzanowskim Yea that's what I did everywhere too ¯\_(ツ)_/¯

[Keith Smiley @SmileyKeith]

@corentinanjuna Of course!

[Blacktop @blacktop__]

The wait for macOS 14.4/iOS 17.4 sauce is OVER! 🍝🥫

XNU

https://t.co/6rrYoHElkY

Security

https://t.co/WPj6FrRWdQ

OBJC

https://t.co/V5VYNbEnMw

ld64

https://t.co/OoUtKr0aoM

dyld

https://t.co/7VlWifxvos

[Rui Ueyama @rui314]

The linker is in a better position to inject malicious code into your system than xz/liblzma if compromised because it can do whatever it wants with the programs being linked. For example, replacing a specific function during linking openssh would be a pretty easy hack.

Therefore, it is important to use a trustworthy linker binary to build your program. But how do you build a trustworthy linker? If you use a malicious linker to link another linker, it can inject code into the new linker which in turn could do something malicious to other programs. This is the well-known chain of trust problem.

This is a real issue for us because we distribute mold binary packages on our GitHub release pages. Fortunately, we recently implemented a change in the script to create the binary packages so that the script is reproducible -- meaning that regardless of the environment it's run in, the script always creates bit-for-bit identical output for the same git commit.

With the reproducible build, you can independently verify that our binary distributions are actually built from the corresponding release of source files. You can also ensure that no third-party binaries are involved during the build.

Thanks to Docker and QEMU, it is pretty easy to write a reproducible build script these days. I'd strongly recommend doing the same if you are distributing binary tarballs. The script for the mold linker is available here: https://t.co/qeeCfmrcm7

[vx-underground @vxunderground]

The xz backdoor was initially caught by a software engineer at Microsoft. He noticed 500ms lag and thought something was suspicious.

This is the Silver Back Gorilla of nerds. The internet final boss.

[Keith Smiley @SmileyKeith]

Mojo hit an important milestone today by open sourcing the stdlib, excited to see where it goes from here! 🔥

[Modular @Modular]

👩‍💻 We're excited to announce that we've open sourced the Mojo 🔥standard library! 📚

Building Mojo🔥 in the open will lead to a better result and open sourcing the standard library is our next step in the journey.

🚀 We're also dropping MAX 24.2 today!

https://t.co/X2BdAGfynY

[Santiago Pastorino @spastorino]

“Rust teams at Google are as productive as ones using Go, and more than twice as productive as teams using C++.” @larsberg_ #RustNationUK

[Keith Smiley @SmileyKeith]

Please let this be true

[Joe Rossignol @rsgnl]

iOS 18 will let you place app icons anywhere on the Home Screen grid, multiple sources told me

Example image via @iDownloadBlog

[Simon Willison @simonw]

Have you ever hesitated to try out an API from Azure, AWS or Google Cloud because just the idea of needing to figure out how to get API credentials puts you off?

[Keith Smiley @SmileyKeith]

Making a Macintosh Studio https://t.co/rFhakCF5hg

(This person's videos are generally awesome if you like this one)

[Keith Smiley @SmileyKeith]

@varun_santhanam So wild!

[Keith Smiley @SmileyKeith]

One solution for swift macros build times is if someone (ideally the swift-syntax repo) distributed the required prebuilt xcframeworks instead of requiring everyone built from source (bonus points if someone solves shipping a single framework with muiltiple swiftmodules)

[maybe: varun @varun_santhanam]

@SmileyKeith fwiw so far we think that they are considerably slower even w/o the overhead of SwiftSyntax -- https://t.co/k2OKpXMGhh