using Apache Bench for e2e server benchmarking (`ab -n 5000 -c 36`)

next: 72 requests/second
next-pages: 108
nuxt: 254
solid: 401
remix: 419
sveltekit: 523
leptos: 1711
leptos (islands): 2615

If server performance is your primary concern, consider... not JavaScript.

Benchmarking is easy.
Unintentionally cheating benchmarks is easier.

Creating useful benchmarks is hard.
Having those benchmarks be fair is harder.

twitter.com/i/spaces/1vOxw…

Anyone know how to enable a specific feature or set of features for RustRover, a JetBrains IDE 's code highlighting?

I reduced my Rust compile times by 75% with these neat tricks. Big compiler hates it
benw.is/posts/how-i-im…

Why is no one talking about this crate!?! #EuroRust

(╯°□°）╯︵ ┻━┻

crates.io/crates/cool_fa…

🚀 Let's hear it for RustRover – our new dedicated Rust IDE! We’re announcing a free public preview and encourage you to check it out. Enjoy this IntelliJ-based IDE with on-the-fly analysis, code completion and debugger. Head over to the 👉 jb.gg/rustrover

No RustConf for me this year 😞

Sharing as a reminder that most proposal do NOT get accepted, regardless of how much experience you have as a speaker.

You just got to keep trying!

What doesn't work for the audience/schedule of one conference might very well work for another!

Excited to say I'm now on BlueSky. wisnu kartono.bsky.social.

Looking for people to follow!

🆕🦀 Just moments ago, #rustlang 1.69.0 was released!

As usual, here's a thread with some of the highlights. 🧵

1/8

blog.rust-lang.org/2023/04/20/Rus…

Nice
blog.rust-lang.org/2023/04/20/Rus…

I'm a sucker for anything with a Peanut Sauce. Chicken Satay!

Borrow checking was one of my nightmares for pavex.

The framework must generate _valid_ Rust code, which implies that pavex itself needs to be aware of the borrow checker.

After a few days of head scratching, it's working!
There are a few edge cases left, but the core works 🚀

Thanks Sean McArthur for all your hard work getting this patched, and on hyper/h2/h3 in general

I have seen many reasonable concerns with the (first) draft of the updated Rust trademark policy (and have some myself too), but I also see some confusion about what trademark law does and doesn't cover. Blogging about Rust is fine. Naming your new language 'Rust 2.0' is not. 1/5

Anybody who hasn't experienced what it's like to work in public on something that tons of people care about has no idea what's up.

The torrent of vitriol, the personal attacks, the rush to judgement. Insanely stressful.

Be kind

Creating anything in public is hard. Hugs for the team as they go through this process.

I have faith they're doing the best they can to marry the legal requirements with the needs of the community.

Give them some time to work. Vitriol is not OK.
blog.rust-lang.org/inside-rust/20…

It is a lot more efficient to be a friendly and good software engineer who can work on a team than to be an amazing software engineer who can't work with others. The first I would hire without a second thought, the second only when forced

You've got about 8 hours left!

I fought the computer, and the computer won