4 ms·

Dabbled with Rust a few years ago. It was not a true joy coming from the C#, Java, Javascript world because it was comparatively verbose to do similar things. I

Dabbled with Rust a few years ago. It was not a true joy coming from the C#, Java, Javascript world because it was comparatively verbose to do similar things. It felt like it was meant to be an improvement on the C development paradigm.

spoiler 4y ago
At the risk of sounding naggy, I think you could maybe give Rust another go. A lot has improved recently, and depending on how long ago you tried it, maybe even radically. A lot of limitations in the language are now lifted thanks to a smarter compiler (NLLs, GATs, more ergonomic error handling syntaxes, etc)
- pjmlp 4y ago
  Still not enough for GUI / graphics coding versus compiled managed languages, including those in the ML family.
  - spoiler 4y ago
    I agree that the state of GUI in Rust is not quite mature. As an aside, there's https://github.com/StarArawn/kayak_ui https://github.com/StarArawn/kayak_ui that seems nice, but I've not actually used it, so I can't vouch for it.
pjmlp 4y ago
I enjoy hobby coding in Rust, however I see its main use case being deployment scenarios where no form of automatic memory management is considered a viable option (tracing GC, RC, mixed RC/GC, ARC, whatever). Additionally I see a possible future with automatic memory management + linear types for low level coding, like Haskell and Swift are looking into, as more interesting. The sweet spot of productiviy of automatic memory management, with the control of type system for low level coding, if really needed.
Ygg2 4y ago
It depends, I worked on SS14 engine a bit. It's a custom C# engine. Versus a Bevy engine in Rust. And most stuff SS14 devs are trying to enforce in their custom C# engine comes for free in Rust. ECS? Mandatory. Systems can't store state? By design in Bevy - systems are functions. Components need to be ported from class to struct? In Rust you don't have to choose. That said some issues like faster iteration and sandboxing might make more sense for a C# engine, but so far there wasn't some huge obstacles for developing other kinds of games.

spoiler 4y ago

At the risk of sounding naggy, I think you could maybe give Rust another go. A lot has improved recently, and depending on how long ago you tried it, maybe even radically. A lot of limitations in the language are now lifted thanks to a smarter compiler (NLLs, GATs, more ergonomic error handling syntaxes, etc)

pjmlp 4y ago
Still not enough for GUI / graphics coding versus compiled managed languages, including those in the ML family.
- spoiler 4y ago
  I agree that the state of GUI in Rust is not quite mature. As an aside, there's https://github.com/StarArawn/kayak_ui https://github.com/StarArawn/kayak_ui that seems nice, but I've not actually used it, so I can't vouch for it.

pjmlp 4y ago

I enjoy hobby coding in Rust, however I see its main use case being deployment scenarios where no form of automatic memory management is considered a viable option (tracing GC, RC, mixed RC/GC, ARC, whatever). Additionally I see a possible future with automatic memory management + linear types for low level coding, like Haskell and Swift are looking into, as more interesting. The sweet spot of productiviy of automatic memory management, with the control of type system for low level coding, if really needed.

Ygg2 4y ago

It depends, I worked on SS14 engine a bit. It's a custom C# engine. Versus a Bevy engine in Rust. And most stuff SS14 devs are trying to enforce in their custom C# engine comes for free in Rust. ECS? Mandatory. Systems can't store state? By design in Bevy - systems are functions. Components need to be ported from class to struct? In Rust you don't have to choose. That said some issues like faster iteration and sandboxing might make more sense for a C# engine, but so far there wasn't some huge obstacles for developing other kinds of games.