Prime Learns The Truth About Rust

preview_player
Показать описание
Luv u Prime ❤️

Seriously tho, dope to see him share his learnings and changed feelings after actually shipping some Rust. It's a great language. It isn't great for everything. Hope the Go era treats him well...

S/O Ph4seOn3 for the awesome edit 🙏
Рекомендации по теме
Комментарии
Автор

You had every justification to name them the *Prime* Meridian and the Theoquator but you did not. This is a national disappointment.

Upsided
Автор

I'm a Rust person. I like using Rust, even when it's not the pragmatic choice. It's my comfy zone and I really enjoy it. I do use React in my day job, and that's cool and fine. I don't hate using other tools. I just like Rust to an unreasonable degree and I realize the unreasonable part.

InnsmouthAdmiral
Автор

Lmao watching Theo react to Prime is the best. Now I want to watch a prime react to Theo reacting to Prime

TaranveerBains
Автор

It’s almost as if there is no one language to rule them all and instead different tools fit different purposes.

duckmasterflex
Автор

Theo, been following you since the old days when you gave tips for JS.
the amount of maturity you have now and you've also given to me along with awesome people like Primeagen is amazing.
It's like I grew up with you and we all done stupid things and we all learned from them and shared our knowledge each to one another.
Thanks for this video. Great content. Actually learned something more this time too.

exapsy
Автор

I don't know, I still disagree on some level. I don't think rust is for everyone, but I've used rust for years and for me I'm honestly just as fast with it than I am with typescript. The language is pretty much never the bottleneck for me. Using python slows me down more because I pretty much never use it and whenever I touch it I need to learn it from scratch.

I think your graph is missing this. Rust makes sense even for prototyping if you and your colleagues all know rust and are already good at it. I think experience with your tools is the most important factor here.

icesentry
Автор

I used Typescript since it was in alpha stage, worked with it for 6 years every single day, wrote hundreds of thousands of lines with it. In the meantime I was dabbling in Rust and switched to it full time since 2 years now and it was the best decision ever, I am now more productive in Rust, I can write faster in Rust than typescript with the added benefit of almost no runtime issues and no breaking changes and no wasted hours because some node module updated or some undefined sh*t. Rust is amazing, full stop.

o__sama
Автор

didnt prime meant he could write a csv parser in rust easily? but theo thought he said the csv parser is on the left of the line of prime. i think he misunderstood what prime said(?)

Автор

Looking forward to "Prime reacts to Prime Learns The Truth About Rust"

pastenml
Автор

He sounds like the parrot from Aladdin and always wakes me up when I fall asleep to youtube.

ThomasWSmith-wmxn
Автор

I think the flexibility comes more from the design than the language itself.

Inflexibility generally comes from tight coupling. In some languages things like interfaces abstract types and virtual methods are used for that loose coupling, while in rust is done with things like traits and dynamic dispatch, but rustaceans see dynamic dispatch and say it's too slow, and that's where they have given up some flexibility for performance. The tools for flexibility do exist in rust though.

You can also get this flexibility from things like microservices but then you introduce network latency, which makes things slower, but you can do that in rust if you're willing to make that trade off.

It's basically about premature optimization.

georgehelyar
Автор

The crossover of Prime writing more application code and Theo writing library is very funny to see in the context of arguments they had a year ago

JLarky
Автор

Iterating with Rust is really intuitive.

wtfisgoingon
Автор

I feel like I genuinely write better code with rust off the bat. I make less mistakes, I cover my bases more and the code tends to run great. I think it’s better to base rust off of performant rust code vs safe but slow rust code. Once you get it “slow” and safe, and the product gets proven you can then make it “faster”. This is how I have been doing it and it’s worked pretty well so far. I think the issue with most people using rust is until you get to a couple 100k lines of code it’s hard to know enough about the language and features to write fast, and good performing code off the bat that can be changed quickly.

xDELTAGIx
Автор

Given all of the assumptions in this video are true, I would be curious to see what this discussion might look like in 5 years once AI copilot tools become more common and mature; as highly explicit languages like Rust that avoid undefined behavior may have more accurate code completion results than the sort of crazy mayhem that TypeScript and JavaScript codebases can become. As a result of that, I imagine the "Line of Prime" would shift leftwards.

gridlocdev
Автор

This was very insightful, thank your sharing this.

paulvalladares
Автор

Theo, you gotta listen to your big bro, anytime you wear a shirt with no tie, you gotta unleash the first button

starlord
Автор

This really made me think, thank you for the insightfull comment Theo :). I think this line is the reason why Rust is such a great candidate for libraries: so many libaries are a stable base which people use to build more changing apps on. The python datascience ecosystem comes to mind with Pandas and Numpy all being written in C++. I think there is a lot to gain in that space by switching C and C++, but also 1-on-1 (a library written in the same language it is used in) libraries. The same thinking applies to most tools I think

computerfan
Автор

I don't necessarily think that using Rust is fundamentally less flexible. Since you can have more confidence that it works, as opposed to more "flexible" languages mostly means it allows stuff to just be broke as heck.

thekwoka
Автор

I run a saas platform now in its 5th year. New tech stack is rust, wasm and qwik js. It took longer to build this time until the main engine was built in rust, but with this new engine, everything is coming together much faster. Meaning rust and wasm make a great skeleton to hang meat on.

Shaunmcdonogh-shaunsurfing