John Carmack: writing Rust code feels wholesome
1–10 of 85 posts
Re: John Carmack: writing Rust code feels wholesome
#2I've been playing with Tokio and Actix for a few days. That's the same feeling I get.
Re: John Carmack: writing Rust code feels wholesome
#3C++ continues to lose mind-share. When will the community acknowledge that their tooling is lacking?
Re: John Carmack: writing Rust code feels wholesome
#4Many comments in twitter mentions rust still not being ready for server code ( which i start to feel strange since concurrency is the only major issue on the server side, and supposed to be rust strength).
Anyone can confirm ?
Re: John Carmack: writing Rust code feels wholesome
#5C++ continues to lose mind-share. When will the community acknowledge that their tooling is lacking?
A tool is a tool. It's immaterial if a particular tool like C++ and its ecosystem is no longer the best available tool for some applications. Workmen pick the tool that best suits their tasks, and if a better tool appears it makes no sense to assume that the old tool requires more attention.
Re: John Carmack: writing Rust code feels wholesome
#6Many comments in twitter mentions rust still not being ready for server code ( which i start to feel strange since concurrency is the only major issue on the server side, and supposed to be rust strength). Anyone can confirm ?
Perhaps they meant webapps:
Re: John Carmack: writing Rust code feels wholesome
#7Many comments in twitter mentions rust still not being ready for server code ( which i start to feel strange since concurrency is the only major issue on the server side, and supposed to be rust strength). Anyone can confirm ?
Wargroove, a recent game by Chucklefish, has its matchmaking server in Rust.
Many people are waiting for async/await before saying “please come try this”, as it makes the enterprise far easier. We’re quite close!
Re: John Carmack: writing Rust code feels wholesome
#8Many comments in twitter mentions rust still not being ready for server code ( which i start to feel strange since concurrency is the only major issue on the server side, and supposed to be rust strength). Anyone can confirm ?
I have used rust but I think it has another year before it really shines. 2020 is the year of Rust - async/await, tool ecosystem, various crate stability, etc is happening fast.
Re: John Carmack: writing Rust code feels wholesome
#9Many comments in twitter mentions rust still not being ready for server code ( which i start to feel strange since concurrency is the only major issue on the server side, and supposed to be rust strength). Anyone can confirm ?
[deleted]
Re: John Carmack: writing Rust code feels wholesome
#10Many comments in twitter mentions rust still not being ready for server code ( which i start to feel strange since concurrency is the only major issue on the server side, and supposed to be rust strength). Anyone can confirm ?
There's a new async/await syntax coming, which will make working with network-heavy code much more pleasant.
Currently, it's ready in the sense you can write robust, high-performance network code. It's still easier than in C or C++, but it's not noob-friendly compared to Node.js or Go yet. Code based on Futures uses owned closures a lot, so you need to "get" ownership in order not to fight the compiler.
With the async/await syntax, the compiler will be able to relax some of the memory ownership restrictions, and you'll be able to write "normal" code instead of chains of callbacks.