@kaffiene @asdfasdfasdf Its slow when you dont know what youŕe doing. For example, build a linked list in #rustlang is different then build one in java, because you can´t leave the variables in a wrong state. It's only a different approach, not a slow approach.

@AlbigensianGhoul Opa, bom dia tudo bem?
Eu também julgava assim, mas na verdade é o contrário. São as relações interpessoais que se tornam poder econômico e militar. Eu vou usar Gilberto Freyre e a sua bibliografia (Talvez um pouco de Maquiavel). A grande tragédia do nosso país, e da maioria dos colonizados segue um padrão que acontece por todo mundo. A formação da elite brasileira acontece com as capitanias hereditárias. O mecanismo econômico, além das grandes massas de escravos ....

@iso all the errors are the same. Missing trait implementations. Already see c++ template issue with dozens of lines. There are some tools that helps like the below. But if you had 100 missing traits implementations, you will got a 100 error lines report.
https://github.com/zkat/miette

@iso In my opninion they are pretty neat, if you use their monads correctly.

@Eufalconimorph url is broken

@sugar_in_your_tea #golang is a near perfect aproach for writing concurrency and async code, indeed, but rust already has channels in standard library. My github has a lot of concurrency code using only std library, including examples in atomics, channels, mutexes, conditional variables, etc...

https://doc.rust-lang.org/rust-by-example/std_misc/channels.html

https://github.com/jcbritobr/concprog/blob/master/src/threadpool.rs

https://github.com/jcbritobr/concprog/blob/master/src/channels.rs

@sugar_in_your_tea @wim if you write low level solutions, async rust is way more easy and less error prone than a c fork/join tool.

@sugar_in_your_tea @wim
go channels and goroutines are very good and easy to work, but thei cant acquire the performance and security of #tokio. You can write good code and solutions with goroutines, but there are limitations. #Rust async is a bit more difficult to do, but its not so or too complicated or dificult, and you will choose between the two languages by kind of problems you want to solve.

@NoRecognition84 @rodneyck its bad anyway. Why a opensource project will do something like that? Telemetry causes bad performance in production. If its opt in, no one will activate, and soon the business will force its use.

@rodneyck @octalfudge
that's very bad news. #fedora is a nice distribution, but telemetry leads the machine to bad perform.