Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
johnthagen’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside johnthagen’s account where johnthagen opened or reviewed pull requests in the past 365 days.
Who noticed johnthagen
Everyone who starred or forked johnthagen’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories johnthagen owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
@RuskiZoomer give this to your agent or a similar guide / skill I might not be aware of johnthagen/min-sized-rust
TFA did [0] the most important stuff for minimizing Rust binaries: release mode, LTO, strip, and abort on panic. But there is a lot more you can do if you really care about Rust binary size [1]: remove location details, purge the debug formatters, rebuild the standard library for size, abort with no error message at all, and nuttier stuff. [0]: github.com/zion-sati/NetWasm/blob/main/docs/size-… [1]: johnthagen/min-sized-rust
> ultimately everything is eventually possible against any given hardware. Not everything, no. You can't run C# without the .NET runtime. Some parts of it are irreplaceable. And the Rust optimizations to shrink binary size (see johnthagen/min-sized-rust) are commonly done in production when it matters, not just in WASM but also in embedded.