David Tolnay

🇺🇸

[David Tolnay @dtolnay]

If this is seen by a billionaire who'd like to move the needle on Rust's success in the greatest way, here is a roadmap for you.

1. Identify engineers with a minimum 2-year track record of dramatic productivity, tenacity, and low proclivity to bullshit (leadership roles, distracting side projects, thought leadership). Archetype: @compiler_errors (This one is not necessarily immediately on the market.)

2. Offer a non-negotiable flat rate that is above Big Tech "staff" but below "senior staff" compensation. Approx $800k USD/year to work on Rust in whatever way they want.

3. Make them write and maintain a "living roadmap" of everything they have line-of-sight to executing within the next 6-12 months, with frequent (monthly) revision. This can be concrete foreseeable projects, approach for coming by projects, or carved up time like "20%: compiler PR review with priority to type system". The roadmap is not for you or any other audience. It is for their perceived job security. The understanding should be if they execute on approximately this amount of value with high productivity and low bullshit, they are doing well, and will get fair warning and guidance if it doesn't trend that way.

4. Dismiss quickly and without remorse, if someone begins coasting or otherwise taking advantage of the opportunity in a self-serving manner. By this point you have already rewarded them beyond where they would be if they had kept their previous role so there will be no hard feelings. Engineers with this skill set will do perfectly fine somewhere else.

5. Do not take applications or recommendations. The roles are invite-only. The application process is performing the above described archetype on a volunteer basis or on behalf of a different employer, same as any other Rust contributor.

Disclaimers:
This is obviously not the only role it takes to make a great product. It is just the one that is most direly undervalued by the market. This is not a slight toward anyone whose work would not meet these criteria or who would not be attracted to such a role. Rather the opposite: they should feel fortunate that their archetype is not the undervalued one.

[David Tolnay @dtolnay]

I don't think you can read that from this graph. If Haskell usage was almost nonexistent by late 2024, and Rust adoption is rapidly growing in 2026, then that share is definitely coming from something other than Haskell.

A majority of the Rust usage is things that would previously have been C++ or Python.

[Charlie Marsh @charliermarsh]

"Meta engineers have written twice as much first-party Rust code so far this year than in the previous 9 years combined."

[David Tolnay @dtolnay]

https://t.co/d56WsnNFiQ

[David Tolnay @dtolnay]

Verifying myself: I am dtolnay on https://t.co/OgQ7wFmfg7. ZY9VY1kSAGr5TNwh_Qz6dxl8jWqcaYF7hItY / https://t.co/6dRuPbGGHo

[David Tolnay @dtolnay]

Verifying myself: I am dtolnay on https://t.co/OgQ7wF461Z. RNLj9GJWGwlyye52kCH1bGE4Mw1-mvRgk_Zj / https://t.co/SdbMmYxEpA

[David Tolnay @dtolnay]

openpgp4fpr:4628C5D82CFF65D68164A78AF9BA143B95FF6D82

[David Tolnay @dtolnay]

@PredragGruevski Yes. You could probably point grok at this repo and get a working version for zstd (and also xz) with minimal guidance.

[David Tolnay @dtolnay]

If you create .tar.gz containing large files, please use https://t.co/xaLmblP5nR so that individual files can be extracted efficiently and files can be extracted in parallel.

[David Tolnay @dtolnay]

https://t.co/iDGLUaV9QQ

[Filip Jerzy Pizło @filpizlo]

I wrote a document describing how Fil-C's InvisiCaps capability model works!

https://t.co/UXht7j3Aar

[levent @__alpoge__]

hello there the jacobian conjecture is false thanx to my close friend akhil for asking about it and my other close friend fable for working during the world cup final

((1+xy)^3 z + y^2 (1+xy) (4+3xy), y + 3 x (1+xy)^2 z + 3 x y^2 (4+3xy), 2 x - 3 x^2 y - x^3 z): \C^3\to \C^3, has jacobian determinant -2, and sends (0, 0, -1/4), (1, -3/2, 13/2), and (-1, 3/2, 13/2) to (-1/4, 0, 0)

[htmx.org / CEO of decade old computers(same thing) @htmx_org]

a heartbreaking work of staggering genius

[David Tolnay @dtolnay]

Now under 30 clock cycles.

[David Tolnay @dtolnay]

Printing arbitrary 64-bit floating point to ASCII at an average of 40 clock cycles is so ridiculous. Żmij algorithm is great work by Victor Zverovich.

https://t.co/J0zQZyXrMG

[David Tolnay @dtolnay]

That's a new one

[Ryan Dahl @rough__sea]

great for people submitting changes to deno

[Andrew Gallant @burntsushi5]

I've added an AI policy to ripgrep that was shamelessly copied from uv's policy. I plan to add this to the rest of my projects, but if anyone wants to offer feedback on wording, now would be a good time!

https://t.co/Lveq6HUoo1

[David Tolnay @dtolnay]

- Open backed
- Wireless
- Over-ear big enough for my genetic cohort
- All-day battery
- Impeccable build quality

Not sponsored, I am just happy that this spec finally made it into a product.

[HIFIMAN @hifimanofficial]

We are excited to introduce our new open-back planar HE1000 WiFi and Arya WiFi headphones, both stream full-resolution, lossless audio over Wi-Fi, combining wireless freedom with performance on par with wired systems! #hifiman #he1000wifi #aryawifi #headphones #audiophile

[Charlie Marsh @charliermarsh]

We've entered into an agreement to join OpenAI as part of the Codex team.

I'm incredibly proud of the work we've done so far, incredibly grateful to everyone that's supported us, and incredibly excited to keep building tools that make programming feel different.

[Andreas Kling @awesomekling]

Over the last ~2 weeks I've rewritten the @ladybirdbrowser JavaScript compiler in Rust using AI agents.

~25k lines of safe Rust (20k if you exclude comments). No regressions on test262 or our own internal test suites.

Extensively tested against the live web by browsing in lockstep mode where we run both the C++ and Rust pipelines, and then verify identical AST & bytecode.

We're making a pragmatic decision and adopting Rust as a C++ successor language. What a time to be alive!

[Mitchell Hashimoto @mitchellh]

I've been doing open source since I was a teenager (over 20yrs). And for the first time ever, I'm considering closing external PRs to my OSS projects completely. This will throw the baby out with the bathwater and I hate that, but we close auto-opened slop PRs every single day.

[David Tolnay @dtolnay]

https://t.co/K83hEfmUkf

[David Tolnay @dtolnay]

The 2-day gap in my github timeline last week is for PC building.

Parts: https://t.co/Hwm2ZGwhom