
They tried to formally verify this feature. LEAN said "contraction". They shipped it anyways.

@ApacheArrow / Databases / Compilers. (past @SDFLabs, VoDa, @Spotify). Rust/C++/TLA⁺🇧🇷 → 🇸🇪 → 🌎

They tried to formally verify this feature. LEAN said "contraction". They shipped it anyways.

You can pay LinkedIn to see who visited your profile. Other people can pay even more so that you, who pays to see who visited your profile, can't see that they visited your profile.

Congrats to @changhiskhan and the @lancedb team!
The next generation of models needs a data stack built for AI. We just raised a $57.5M Series B to help researchers turn petabytes of video, images, and audio into better models, faster. Read the announcement: lancedb.com/blog/lancedb-ser…


You coding agent is adding TOO_MANY_ENV_VARS to your service. Ask it to design a hierarchical configuration file format based on the KDL language and stop dealing with this mess. Keep secrets and passwords outside of the config file of course. Your agent knows this too!

Compiler engineers bad at databases (see rustc target/ dir). Database engineers bad at language tooling (see every SQL dialect).
Someday it's gonna come out that the Rust compiler team got infiltrated by SSD salespeople

Binary size optimization is a funky business. Sometimes you reduce the bloat caused by one function being inlined in too many places but that allows callers to shrink. Then the callers themselves end up qualifying for inlining. By being inlined, they add back a lot of what was saved.

*stops changing so fast

Changes will be added in the easiest, most polished places. That generic layer everything can rely on? Perfect place for a hook that now does surprising things behind the scenes.

Any build time improvements will be seized by the programmers adding more dependencies or making the build graph less amenable to parallelization. UNLESS the product starts changing so fast that you can do some polish.

IME, programmers usually start with a laudable but misguided intuition that because crashes inconvenience users, crashes should be avoided. Takes a while to understand that aborting when you notice a logic bug is doing your users a favor.

So you have a 10-screens long Claude Artifact you shared with me so I can read it?

We can fix everything, but the same bugs keep reappearing.

Who is going to tell Elon that all these compilers generate LLVM code and in many cases LLVM can optimize the code that rustc produces better than it can optimize what clang produces?
So easy to trigger Rust programmers 😂 Rust is a good language, but C is what you use for optimal performance on bare metal. With great power comes great responsibility.

It’s all so tiresome. Combining C++ compute kernels in C++ itself takes so much effort. One is better off being able to quickly try many different configurations and see what works best. And Python helps achieving that!

It would be hard to enforce this on a large team with competing priorities that do not include performance. This is largely why retained mode UI systems won the industry adoption contest.