Live data from Hacker News

Rust All Hands 2026 Retrospective

blog.rust-lang.org

51–60 of 63 posts

Re: Rust All Hands 2026 Retrospective

#51

Earlier quoted context omitted.

i think rusts composition is problematic. you can have two abstractions that if you mix them the outcomes are not what you expect unless you have a deep understanding of the details, (e.g. clone/iter) and rust is all about hiding details from you.

I really couldn't disagree more. Rust doesn't hide those details at all. APIs tend to be extremely explicit. I have never run into the issue you're describing in rust, I have run into it far more in other languages where mutability and sharing are implicit.

the existence of iter is to hide implementation detsils from you.

Re: Rust All Hands 2026 Retrospective

#52
post #34

Earlier quoted context omitted.

With a beefy desktop, or some Apple wonder CPU, right?

M2 air. Pay to play brotha

Which is why devs on other world regions will chose something else, more ammendanble to their pockets to stay productive.

Re: Rust All Hands 2026 Retrospective

#53
post #39

Earlier quoted context omitted.

The experiences still fails short of XCode or Playground, hence why Slint has its own scripting language.

Sure, I don't disagree. It's just not clear to me that developers actually index that heavily on hot reloading to begin with.

Devs doing graphics and game development care so much, that there are companies like Live++ selling hot reloading tools for C++.

Like, devs actually pay for having hot reloading.

Re: Rust All Hands 2026 Retrospective

#55
post #52

Earlier quoted context omitted.

Which is why devs on other world regions will chose something else, more ammendanble to their pockets to stay productive.

Ok and?

And less language adoption in regions whose devs aren't able to afford beefy computers to use Rust ergonomically.

Which is why then they go back other languages,

https://loglog.games/blog/leaving-rust-gamedev

Re: Rust All Hands 2026 Retrospective

#56
post #55

Earlier quoted context omitted.

Ok and?

And less language adoption in regions whose devs aren't able to afford beefy computers to use Rust ergonomically. Which is why then they go back other languages, https://loglog.games/blog/leaving-rust-gamedev

Gamedevs usually have the most powerful machines of all types of devs because of it's very nature. Yes you can't compile Rust on the GPU but big gpu's come with big CPUs usually.

Re: Rust All Hands 2026 Retrospective

#58
post #57

Covid policy at Rust All-Hands [0] > On Thursday, Friday and Saturday, at the All-Hands and Unconf, we expect all attendees to test themselves in the morning. I thought Covid is long gone. What did I miss? [0] https://2026.rustweek.org/covid-policy-all-hands-and-unconf/

long gone in the sense of media coverage perhaps? the virus hasn't gone anywhere and it's not like we have vaccines that give permanent/longterm immunity

Re: Rust All Hands 2026 Retrospective

#59

Earlier quoted context omitted.

I really couldn't disagree more. Rust doesn't hide those details at all. APIs tend to be extremely explicit. I have never run into the issue you're describing in rust, I have run into it far more in other languages where mutability and sharing are implicit.

the existence of iter is to hide implementation detsils from you.

I don't understand what you mean at all. Iter is just a trait. There's nothing special about it.

Re: Rust All Hands 2026 Retrospective

#60
post #57

Covid policy at Rust All-Hands [0] > On Thursday, Friday and Saturday, at the All-Hands and Unconf, we expect all attendees to test themselves in the morning. I thought Covid is long gone. What did I miss? [0] https://2026.rustweek.org/covid-policy-all-hands-and-unconf/

long gone in the sense of media coverage perhaps? the virus hasn't gone anywhere and it's not like we have vaccines that give permanent/longterm immunity

Nowadays I am more concerned about measles and ebola viruses. Over-indexing on covid makes little sense in 2026.
Post reply on HN