Júlio Gardona

@winnie snap is not so mature as flatpaks yet. Dont know if its really a nice descision.

@ghariksforge @Gecko No one supports Win 10/11 telemetry and updates. And also, there are a huge rejection to win 11 from 10 users.

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

@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.

@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.

@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

@snaggen not for me also. #vscode or #helixeditor are pretty neat in my opinion.

@snaggen Cyber security problems seems to be a major issue to fix in this decade.

@snaggen @kicolobo

@onlinepersona @snaggen

people write oo code in linux source code using c. With rust is simple. Just use composition, and you can explore the traits, that serves as and is better than interfaces.