I believe Golang is winning on the long race with Rust. More companies jumped on the Golang train for their products, even bigger ones like RedHat, SumUp and Docker
-
-
-
If you read the article you'd note that the work he discusses would not be possible to write in go.
- Još 2 druga odgovora
Novi razgovor -
-
-
I enjoy writing Rust. I got really fed up with Cargo once my needs extended past simple builds. Building crates with cross-language dependencies turned into a nightmare of debugging build tools.
-
It's a pain point but manageable. I think within a year or so this will be much easier.
- Još 5 drugih odgovora
Novi razgovor -
-
-
Any
#Dev that wants to build on#Holochain has almost unlimited options.#RAD#javascript#rustlang#SocialMedia#CloudStorage#Crypto#hosting#P2P#App#Holofuel#CloudComputing#cloudpic.twitter.com/kAhR0hIZD6
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Rust is doing everything C++ *wants* to do, but hasn't yet. C++ allows Barbara Liskov's and Alexander Stepanov's work to be expressed, even if it doesn't enforce such expressions the way CLU/Argus or Rust/Swift try to.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I learned the nuts and bolts of Rust and then decided to learn C++. learning the latter actually improved my knowledge of Rust because I'm constantly comparing the two. it helped especially in understanding the subtleties of refs and smart pointers in Rust. call me crazy
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Gotta love no_std
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
That article is pretty convincing but to be pedantic, the author did make a few small mistakes about C++. That said I don't blame the author because C++ is so complicated that hardly anyone can write about it in depth without mistakes.
-
A few nitpicks: the author claims that in Rust it is possible to pass a reference to a fixed-size array without having it decay to a pointer and implies that this isn't the case in C++. It's wrong: char get_element_3(char (&array)[10]) { return array[3]; }
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.