@SheikhEddy
I started dying at "Rust is C++ if it was haskell"
@IamPyu-v
Rust and Go are very different languages, Rust: nyaa-meowmeow Go: has a life
@Requiem100500
I expected joke video, but this is actually mostly true
@DVRC
These days I've been digging the net to find obscure window systems for UNIX/Linux, and I found Fresco (written in C++, and leveraged CORBA and GGI). On the page it is said : "we depend on CORBA... Things you use can't be bloat" , I laughed so hard. Then I've seen that one of the people involved was Graydon Hoare, there I thought "wait a second, this name is familiar" . Then I realized... BTW the original Go toolchain was bootstrapped with the Plan 9 C compiler and assembler, while Rust was bootstrapped with OCaml (which runtime is written in C).
@JasonMitchellofcompsci
Well you sold me on not using rust. I'm not going to say which argument did it... but it was effective.
@goat-7658
I feel like this would've been the worst way to learn any of the presented factoids, had I not already known all of them. I haven't watched a more incomprehensibly chaotic assortment of abstract useless information in months. Great job on making one of the most un-educational videos on this platform.
@poonikarthu4988
To run your project (which can be done without running the build step as it automatically builds) you can do cargo run instead of pointing to the application directly.
@ivanpelykh7665
Якісний контент)) Продовжуй в тому ж дусі!
@AYoutubeHandleThatIsNotTaken
Soon what happened with the JavaScript frameworks will happen with c/c++ alternatives. You can see all the new 'fast as c but easy as python' langs out there and also carbon trying to replace cpp.
@william1106
love the video, microphone a bit wack but it's still all good <3
@jaysistar2711
I like the music selection. Can you post a track list? I like Rust better than Go, but, yes, it does take longer to get used to it. I do use inline asm, and in a conversation that I had with the Go devs, back in 2010, they told me that they'd never support inline asm. I had just translated x86 (32-bit) asm to C with inline asm as an intermediate, so I wasn't happy with Go after that conversation. Later, a project in Java had me fighting with the garbage collector to remove jank. I rewrote it in C++, and everything was fine. Being that everybody considers C (most of my projects are C) and C++ old and deprecated, my new projects have all been Rust. I can say that SCONS, Conan, vcpkg, and CMake have nothing on Cargo. Cargo is great! The learning curve for Rust is just too steep, right now. I hope that it will change in the future to be easier to pick up. Integrating cross language support is easier with Rust as well. I had a project that needed to integrate with Ada, and Rust made it easy by just doing what C does, and not imposing thread or GC restriction on calling or called code.
@wheezybackports6444
I need a compiler to compile my compiler and a compiler to compile that compiler along with a compiler to compile the compiler to compile that compiler.
@VectorAlphaSec
Honestly tried both. Rust is better.
@flamakespark
Concurrency in Go: a single keyword in front of the function Concurrency in Rust: - Staring with singlethreaded prototype - Fixing borrow-checker errors - Fixing them again in multithreading - Spending 3+ hours in resolving that deadlock - "Fk it, I'm just gonna use Rayon"
@MrAbrazildo
2:33, OO is safe, it fixes the C issue. Plus, if you keep your objects (not interfaces) in arrays/containers, it's safe and easy to translate it to hashtable, if you want to - I have personal experience on that. And array of objects can compete against hashtable, when they are on L1 cache, at least. And if that company achieved "complete unmaintainable mess" with OO, they made really bad choices, because this is the strongest point of OO. 3:20, and C++ can do both on the same level of productivity, because it's flexible enough.
@razhterize
fuck it, I'll go backward and use C
@marcels.7074
2:59 got me
@GameParrot
Video idea: When Autocorrect Destroys a Linux User's Life
@childlikedevelopermetalang4164
Very thoughtful. Thanks.
@NamasteProgramming