11–20 of 996 posts
Rust is the "frontend wave" of the backends. All the woke kids gravitate towards it. A suffix of "Written in Rust" is a thing here so I'm throwing away my internet points now.
> Making a fun & interesting games is about rapid prototyping and iteration, Rust's values are everything but that I feel like this is the core of the author's frustration. Rust is a systems language. It's for writing tight fast C-like code but safely and with a much more powerful type system. The facilities you need to do this are somewhat at odds with what you want for rapid iteration. Seems like Rust was the wrong…
Exactly!
Rust -> move slowly and don't break anything
> Making a fun & interesting games is about rapid prototyping and iteration, Rust's values are everything but that I feel like this is the core of the author's frustration. Rust is a systems language. It's for writing tight fast C-like code but safely and with a much more powerful type system. The facilities you need to do this are somewhat at odds with what you want for rapid iteration. Seems like Rust was the wrong…
That seems to be the crucial point. Rust is optimized for writing complex systems software in large teams. That’s not a great fit for a small team hacking on something that is at least in part an art project. You wouldn’t choose something like Ada for that either.
> Making a fun & interesting games is about rapid prototyping and iteration, Rust's values are everything but that I feel like this is the core of the author's frustration. Rust is a systems language. It's for writing tight fast C-like code but safely and with a much more powerful type system. The facilities you need to do this are somewhat at odds with what you want for rapid iteration. Seems like Rust was the wrong…
Sure, but the problem is when you have a community around that tool that insists otherwise.
I've never before been so condescended to as when attempting to ask questions there. Their lack of care for perf also drives me up a wall. Anytime they propose adding an extra layer of indirection to get around the borrow checker, I have to explain yet again that with the way modern CPUs work, extra layers of indirection have serious cache-related perf costs. Then I get told that I am yet again doing it wrong, computers are fast enough, and I am worrying about the wrong thing.
Rust is great from lots of stuff but game development or building UIs isn’t among that (yet).
Rust is the "frontend wave" of the backends. All the woke kids gravitate towards it. A suffix of "Written in Rust" is a thing here so I'm throwing away my internet points now.
I think most people here understand that a language that is great for kernel development isn't necessarily great for everything else.
Just try finding e.g. an MQTT or WebSocket or etc library that doesn't drag the whole mammoth tokio ecosystem (which is really geared for Web Scale! projects) in with it.
Rust is becoming the language that tokio ate, and Cargo/Crates.io the new NPM.
That is, Rust is the systems language that a wave of non-systems developers insist on using, leaving behind a trail of non-systems-appropriate crates and projects.
Parent commenter's comment was crap by HN's commenting standards... but the underlying point about trendiness I think is in fact accurate.
NOTE: I'm not a game dev