HN user

dochtman

8,630 karma

Professional Rust maintainer.

https://dirkjan.ochtman.nl/ https://github.com/djc https://xavamedia.nl/

[ my public key: https://keybase.io/djc; my proof: https://keybase.io/djc/sigs/8IkleSSBN9hhCZWqkfDndLYhEEfanUDBVDQdS_hqH9U ]

Posts166
Comments659
View on HN
www.bcg.com 2mo ago

The Rule of Three and Four

dochtman
1pts0
nesbitt.io 2mo ago

Weekend at Bernie's – assessing critical open source repos

dochtman
4pts0
nesbitt.io 2mo ago

GitHub Actions is the weakest link

dochtman
252pts93
security.googleblog.com 3mo ago

Bringing Rust to the Pixel Baseband

dochtman
2pts0
github.com 5mo ago

mmdr: 500-1000x faster Mermaid rendering, zero browser dependencies

dochtman
3pts0
lwn.net 7mo ago

The state of the kernel Rust experiment

dochtman
119pts130
nnethercote.github.io 1y ago

How to speed up the Rust compiler in March 2025

dochtman
3pts0
trifectatech.org 1y ago

Zlib-rs is faster than C

dochtman
341pts473
oxide.computer 1y ago

Oxide cuts data center power consumption in half

dochtman
18pts2
lwn.net 1y ago

The WordPress Mess

dochtman
4pts3
github.com 1y ago

Show HN: Pyrtls, rustls-based modern TLS for Python

dochtman
22pts1
ketanjoshi.co 1y ago

Texas builds clean power – but it isn't a climate champion

dochtman
13pts7
eclecticlight.co 2y ago

File systems can change in Sequoia with FSKit

dochtman
2pts1
jbp.io 2y ago

CVE-2024-5535: `SSL_select_next_proto` buffer overread

dochtman
7pts0
fosstodon.org 2y ago

Detecting faulty RAM hardware in Firefox crash data

dochtman
9pts1
mailarchive.ietf.org 2y ago

Proposal towards universal HTTP/3 (polyfilling QUIC over TCP)

dochtman
1pts0
www.memorysafety.org 2y ago

Securing the Web: Rustls on track to outperform OpenSSL

dochtman
8pts0
www.memorysafety.org 2y ago

First stable release of a memory-safe sudo implementation

dochtman
17pts0
blog.cryptographyengineering.com 2y ago

Some Rough Impressions of Worldcoin

dochtman
4pts0
www.pathsensitive.com 3y ago

Aspects of Good Code

dochtman
6pts0
graydon2.dreamwidth.org 3y ago

The Rust I wanted had no future

dochtman
868pts508
www.jelmer.uk 3y ago

Porting Python Projects to Rust

dochtman
2pts0
github.com 3y ago

GitHub Sponsors will stop accepting PayPal on February 23, 2023

dochtman
38pts68
lwn.net 3y ago

Rust in the 6.2 Kernel

dochtman
3pts0
lwn.net 3y ago

A first look at Rust in the 6.1 kernel

dochtman
4pts0
www.mnot.net 4y ago

What will a Chromium-only Web look like?

dochtman
267pts344
gregoryszorc.com 4y ago

Expanding Apple Ecosystem Access with Open Source, Multi Platform Code Signing

dochtman
12pts0
lwn.net 4y ago

Rustaceans at the Border

dochtman
3pts1
www.bleepingcomputer.com 4y ago

New Intel chips won't play Blu-ray disks due to SGX deprecation

dochtman
7pts0
twitter.com 4y ago

Striking Technology Advances over Time

dochtman
1pts0

GitButler now employs/has hired the gitoxide maintainer, I think? So no doubt they’re aware.

I guess they found that gitoxide isn’t good enough and/or to expensive to extend/improve for their use cases?

That's the policy, but we've been a bit more conservative in practice. `main` currently targets 1.88, but that's only because a security issue in the time crate has forced our hand (one reason I don't like the time crate all that much). Before that, it was 1.83 (from November 2024). Our last release targets 1.71 (from July 2023).

I think the way Rust checks borrows also makes it a lot more feasible to avoid allocations/copies; not because it is impossible to do in C, but because doing it in C requires writing very careful documentation and the caller to actually read that documentation. In (safe) Rust this is all checked by the compiler such that libraries can leverage it without blowing their complexity budget.

There’s also a compounding effect: I’ve heard from a hardware vendor that they spend a lot of time optimizing OpenSSL to get the most out of their silicon, so for their customers they suggest using OpenSSL to get the most out of the hardware.

I'm pretty sure private PKIs are an option that is pretty straightforward to use.

Security is still a lot better because the root is communicated out of band.

When I asked about financial support, the Senior Principal Software Engineer from Mozilla I talked to said "Mozilla has no money".

To be fair, we've gotten a great amount of code contributions from the Mozilla folks, so it's not like they haven't contributed anything.

(I am one of the Quinn maintainers.)