Keith Smiley

25.6K posts

Keith Smiley banner
Keith Smiley

Keith Smiley

@SmileyKeith

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

@[email protected] เข้าร่วม Nisan 2008
749 กำลังติดตาม8K ผู้ติดตาม
Keith Smiley
Keith Smiley@SmileyKeith·
@steeve Yea you should upstream that. Stuff seems pretty dated
English
1
0
0
45
Keith Smiley รีทวีตแล้ว
Chris Lattner
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: github.com/llvm/llvm-proj…
Chris Lattner tweet media
English
3
24
281
29.9K
Brady Law
Brady Law@bradysays·
Excited to announce I'll be demoing my desk companion project at @OpenSauceLive in June! It's a little device with an e-ink screen, air quality sensors (temp, co2) + wifi+bluetooth. Designed to be hackable so you can write your own apps for it, and the enclosure is 3D printed.
Brady Law tweet media
English
1
0
24
2.3K
Corentin Kérisit
Corentin Kérisit@corentinanjuna·
monorepo current status: 30k lines of Starlark 💚😅
Corentin Kérisit tweet media
English
2
1
11
2.2K
Keith Smiley รีทวีตแล้ว
Rui Ueyama
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: github.com/rui314/mold/bl…
English
4
60
323
45.3K
Keith Smiley รีทวีตแล้ว
vx-underground
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.
vx-underground tweet mediavx-underground tweet media
English
148
2.6K
18.9K
4.6M
Keith Smiley รีทวีตแล้ว
Santiago Pastorino
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
Santiago Pastorino tweet media
English
38
207
1.2K
548.3K
Keith Smiley รีทวีตแล้ว
Simon Willison
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?
English
64
39
187
291.3K
Keith Smiley
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)
English
2
1
17
4.4K