Stop Using Rust Use C++ | Prime Reacts

preview_player
Показать описание
Recorded live on twitch, GET IN

MY MAIN YT CHANNEL: Has well edited engineering videos

Discord

Hey I am sponsored by Turso, an edge database. I think they are pretty neet. Give them a try for free and if you want you can get a decent amount off (the free tier is the best (better than planetscale or any other))
Рекомендации по теме
Комментарии
Автор

That article has the vibe of being written by someone who just had a week of learning Rust and then gave up.

anlumo
Автор

This is the type of guy that gets things done fast but never maintained his own code

NotherPleb
Автор

Half the comments: "Well, that's just a skill issue, but not a problem if you *really* know rust".
The other halt: "Screw c++, it's too complicated for me to learn"

sirhenrystalwart
Автор

I feel the "it works" factor is a massive positive for Rust in the embedded space. I abandonned C++ because Cargo & Cross "just works", rather than fighting with the build tooling to figure out how to get C++ libraries cross-compiling / cross-linking correctly.

TheBeardedQuack
Автор

Sometimes I'm so prepared for the rust analyzer to tell me how dumb and worthless I really am. I see the errors in the corner of my eye taunting me. They want me to give up. But then I finish some line and the warnings fall eerily silent.

I nervously hit build. It works impeccably, no issues, it's fast, it's efficient, it's beautiful.
Those are the moments.

CjqNslXUcM
Автор

5:10 The problem with MVPs is that they very easily and quickly become the production code. Once you get an MVP out, so do the requests for changes and improvements and additions. Before you know it, you have a full blown core system written in a scripting language. So do you choose what’s easiest or should you pick what you want to end up using?

brnto
Автор

after 6 months of 'fighting w the borrow checker' i never fight with it anymore. I now know how to borrow and clone and i now know that strings are completely insane in rust and why (its worth it) and now i write rust as fast as i write js. actually even faster bc i dont need to do live tests to make sure features work. The compiler is like my test suite

admazzola
Автор

"You should use a garbage-collected language just to get things out the door." Got it. LISP, HERE I COME, BABY!

mage
Автор

I found c++ really hard to master. I was insecure about where to start, what compiler package manger to use. Which courses or and tutorials to fallow. Learning rust on the other hand was straightforward because the ecosystem is not a old overgrown jungle and the rust book is an amazing starting point.

HerrSnooze
Автор

I'm a 10+ year C++ dev and also a full stack JS dev. I could say the same against C++ compared to Js or python to an even bigger extent. Truth I pick the language that's the most adapted to your ecosystem

benjamin_fdw
Автор

Rust was never really intended for startups to ship products quickly, so these takes are kind of no-brainers.

lukekurlandski
Автор

I gave up on Rust pretty much with the same arguments as him, but I haven't wrote an article because me not liking a language is not a valid argument about a language's quality

VictorHugoVideos
Автор

I totally agree with you assessment of Go. Tbh both Rust and C++ are overkill for a lot of case uses. C# gives you a lot of room for optimisation without writing unsafe code, should you need it, but you often don't. Personally I have this idea that functional-flavoured OOP languages are the best for getting stuff done quickly, because they let you translate algorithms into code very directly, but they aren't too strict when you've got to add in some imperative details or manipulate some state. So C#, TypeScript, Kotlin, Ruby, even more outright functional languages Scala and F#, are ideal to me.

akirakosaintjust
Автор

"Fighting with the borrow checker" = training your brain how to not make memory management mistakes.

mrlordbrutish
Автор

The issue is, when you *_do_* make the product, how much technical debt do you want it to be? Rust turnaround times are slower, but the final products tend to be more well put together.

robonator
Автор

Surprising that this article highlights the struggles of the borrow checker so much that it would wholly delay shipping a product. Like… it’s not THAT hard. Yeah the borrow check has kicked my sweet cheeks many a time, but has it delayed my dev speed or dev ex? Not as much as runtime errors in JS 😂😂

kingofdreams
Автор

Somebody once told me "Go is so boring!", and I thought: "Yea, this could be my cup of tea! I have kids, and I need to get things done. I don't need creativity in my daily business..." 😀

deNudge
Автор

I disagree that you can't ship products quickly with Rust. Maybe 3 years ago, but the ecosystem is much more mature now. I recently rewrote an API layer in Axum (as an example) and it took no time at all.

bravethomasyt
Автор

I typically switch between C++ and Python depending on usages, thinking of learning golang and rust in that order, but these 2 alone already covers for quite a fair amount of use cases (for me at least)

uuu
Автор

Lets talk about shipping buffer overflows to users in record time...

johanngambolputty