linux did not move to rust they just introduced it to some parts of their code base. and the main goal is to decrease memory related security holes. also rust is not going to replace js, I think of rust as a new category where SOME code bases could move into because it might be more suitable which is a good thing. but rust is definitely not going to replace neither js nor c.
Programming languages never get replaced, this is just a fact of the universe, just look at COBOL and Fortran. Heck, languages don't even get replaced by newer versions. Python 2 and C89 are still more alive than anyone wants them to be.
@@kebien6020 Yup. Replaced in computer science really means more like "we stop making new projects" as opposed to rewriting existing code in the new language. But eventually it gets to a point where nobody wants to write new projects in COBOL for instance and it's used purely to update the existing COBOL codebase that nobody wants to rewrite. True full rewrites of software pretty much don't happen.
Well, Rust is not meant to replace either of those. TypeScript is already a good replacement for JS, and C has a bunch of offspring languages of its own already. Rust is doing it's own thing with its borrow checker and friendly compiler, and people (me included) seem to like it.
I don't quite get the hype behind rust, it's the panacea for every problem. Kernel - rust, static website - rust, backend - rust. Your summary is quite correct, "write too much code to get small things done". Your js code is simple and with a glance I can read it and even debug it without running, while the rust code overflows off the screen only for the declaration of the method signature. The whole argument about being fast does not make sense, because few years ago the hype was python and JS. What speed are we fighting for, when we've mindfully chose programs built using them? It's clear that there is a tradeoff, and for a pretty long time people were OK with that tradeoff, now for some reason, all software is too slow for us and everything needs to be rewritten in rust. The same analogy can be made using ORM, ORMs are slow, hand written queries are fast, but when developing hand written queries can be a cascading nightmare. Rust is good, but it has it's domains, using it for everything, like JS devs creating website wrapped desktop apps is not OK. It's a degression from all the computer advancements that were made.
I agree Rust shouldn't be used for everything. A web server is probably not where it excels. But the comparison to JS is unfair because the JS code was already using an underlying library (Express) and JS being a high-level language already takes care of many relevant web features because they're written into std. The JS code has just abstracted all that away. Imagine if he had to try to explain Express' source code as well. A C++ web server would be more comparable, and likely would have a similar amount of code. But I still wouldn't recommend using C++ for a web server, for the same reasons. Code maintainability is incredibly important, and I would say Rust should mostly be used where it has an impactful performance advantage.
" The whole argument about being fast does not make sense, because few years ago the hype was python and JS " there was no hype for speed of python ever, wtf are you talking about?
@@user-dc9zo7ek5j The reason could be that we already had speed because people used C++/.NET/Java but if the codebases were unmaintainable then more maintainable approaches would be attractive. Then maybe after people started using JS/Python they realized what they had lost in the process. And now they want both?
Packages are well documented, and if you see that your compiled rust code has a high response time compared to the nodejs code, know that something is wrong with your rust code, and i think it s coming from the db implementation.
1:10 - missunedstanding. Rust has memory leaks. Even in safe code. As simple as `std::forget(my_vec)` or `my_vec.into_boxed_slice().leak()`. And also possible to happen in less obvious context - rc-loop is the reason why `forget` and `leak` are novadays safe functions (pre 1.0.0 they were considered unsafe). Mem leaks are safe.
Yes, but that is on purpose. The vast majority of memory leaks in something like C is forgotten pointers and dangling references, which are guaranteed to not exist in Rust. If you on purpose use Rc, which is said in the documentation that can achieve memory leaks, then you know what you are getting into. The best solution is to not use Rc unless it is literally the only thing that can solve your problem in a meaningful way. Most people do not even know what Rc is, so they are memory leak safe.
@@JackDespero Honestly not sure if any decent Rust programmer wouldn't know what Rc is. It's one of the basic heap allocated types along with Box. I'd say it's pretty essentially to know that one since it's useful for a variety of applications.
when they said this and that will replace c or c++, I heard many times since numbers of years but end up as a dream. keep dreaming folks.. C will be always there because He is the KING, C++ soar much higher than today keep my word
I learn rust since about a year and at first I had similar problems you had with messy files and many "failed" attempts to implement something. One of the most frustrating differences in rust is its efforts to make global static variables unattractive and supress their use. But it encourages you to try other (often better) approaches without the global. For example with the database connections. I don't know how rocket works since I didn't work with webservices yet. But I'm sure there is a way to register a shared variable for the endpoints. If not it's not to difficult to create a "static mut" variable and a (unsafe) setter for it. It isn't the most elegant solution though. Edit: Also the documentation in rust is really hit or miss. Many libraries (including std) are super well documented. But some just aren't and that's the authors fault, not the language. The language actually makes writing documentation really easy since it includes doc comments directly to the crates io website in a nice and uniform format. Regarding the amount of code, me coming from c++, c# and Java don't really think it's any different in the amount compared to those.
How do I add English subtitles/caption for this video? UA-cam's auto-generated captions often get your words wrong, and I want to fix them. Edit: Uh, it took 24 minutes to caption 3 minutes' worth of video... I guess your accent is clear enough for humans. Maybe I should've just opened up the transcript and watched for corrections rather than captioning the whole thing.
0:00 So if you've been hearing a lot about Rust lately, why a lot of developers, companies and teams try to adopt Rust into their ecosystem and move away from JavaScript, C, and C++, or even Node.js. So in this video, I'm gonna take a look at Rust, why it's super cool, also I'm gonna see why a lot of people are preferring Rust vs something like Node.js, also I'm gonna take a quick look on two projects, and compare them side-by-side for Rust and Node.js. So you're probably wondering why a lot of developers are interested in Rust, as well as like why so many teams, developers, and companies particularly, are moving from old codebases from like, JavaScript, Java, C, C++, into Rust itself. There's actually a couple different reasons for me I would choose Rust compared to other ones because I've been trying Rust for the past couple of weeks, and it's more like 2 weeks when I started learning and using Rust, and actually trying to build a project using Rust. So the first, and most important one: It's new. Which means it provides and it brings all the new design patterns, all the awesome features and syntax of all the languages we love and developers like, it brings them to the table. It's also very very safe. It doesn't have memory leaks, it doesn't have CPU bottlenecks, it controls everything and it controls it super well, as well as when I talk about safety here, it has no Garbage Collector. Because most of the time, for languages like JavaScript or maybe um, Python, those are the kind of languages that, you know, it gives you really decent performance, but they all use a Garbage Collector, so it has like a good side and a down side. And for Rust, it literally ignores that Garbage Collector, and it does use the borrow checker. And as well as because Rust is a compiled language, not interpreted like JavaScript and Python, and that code gets compiled down to binaries and native binaries that can run literally anywhere. And there are actually many, many companies that have moved from older languages, like they were using for example C, C++ for like, native code, and some of these companies are like Dropbox, Cloudflare, Figma, the beloved Figma we all love and we all use, Shopify in here, Linux Kernel. Yes, you're hearing it right. So if you take for instance for example Figma and how they were (been) able to migrate from the old JavaScript implementation, (their own,) they moved from TypeScript into using Rust for their like, multiplayer kind of system. They've seen huge difference when it comes to memory bandwidth, or memory usage, and as well as like CPU bottlenecks and how CPU was eaten up before, and after. It's actually incredible how it took the memory usage from like, 4.2 Gigabytes on the TypeScript implementation, and when moved to Rust, it became something like 1 Gig, it's crazy, and that's what Rust is actually capable of doing. So, because how crazy Rust is, and what I've heard from the community, either on Twitter, UA-cam, or just like, literally everyone is talking about Rust and how cool it is, well, I actually decided to, you know, take Rust, and give it a try. 2:58
A bunch of companies, like 10 or 20 that handle millions of requests per day, or have applications that are so resource intensive that going with rust makes sense.
The biggest drawback about Rust for me is that it's very hard to find some friendly tutorial/crash courses like in JS/TS world. For me it's hard to learn a language just from documentation. Also it seems like a very hard to learn language for me coming from typescript background...
@@EllipsesDots I can’t learn just from theory, documentation is not enough for me. I need real world examples, demo apps, etc to understand the theory. But apparently I’m just a bad programmer.
I got your point since I am having hard time to understand through the documentation. But the thing is that many good developers are good at implementing apps based on documentations. Since they know how to follow/read the documentation very well, they don't have any problems for building apps with real world app since they already know what is required for the specific architecture. This is also one thing I am trying to learn; learning code through documents, not by the tutorials from the udemy or youtube. Plus,,,, all those good devs are saying that Rust Documentation is amazing too...
Good video comparing the developer experience with creating a simple auth server with NodeJS vs with Rust -the cons of Rust mostly just come with it not being widely adopted yet and good to point out. I think the title is clickbait however because you don't say Rust is better than TypeScript/JS -just comparing with a simple example.
Why bad? Other than the constant juggling between &str and String, I didn't find anything TOO annoying... Of course, you need to know about borrowing and ownership, that's the trade-off that you have to make to gain C++like speeds without doing the memory management yourself.
It is a pity that Rust has so awful syntax. If it would have normal syntax like C, it would be easier to learn and maybe somewhat easier to port existing code.
Rust is definitely a good language, but library ecosystem is not yet matured and grammar is rather difficult as well as Job market is quite small or narrow. I am sure that it will have more popularity within 5 to 10 years but not at this time. Only a few of big techs are going to experiment and adopt this language to their products, so It's not ready for developers to earn money with this amazing language at least for year 2022 and 2023 I guess.
I don't think Rust is out to replace TS, Rust is a fantastic language and of course a lot of TS code bases can be rewritten in Rust but that just means TS was the wrong choice in the first place, TS/JS does not compete with Rust, it's a much higher level language with abstractions for different use cases. A better comparison is Rust and c/c++, they share the most traits and have mostly the same use cases. I love Rust but I wouldn't choose it over TS unless the benefits actually outweigh the cons which unless you're making high performance applications is very seldom and even so there's nothing stopping you from containerizing different concerns with different languages given your service is complex enough. Overall I think the thumbnail is pretty click-baity. In the time since 2015 when Rust launched TS has only grown and co-existed with Rust, I think a more interesting outlook is Python vs TS. Python is the true menace.
The thing is that it builds dependencies once per update. After they are built you never have to build again and only build code after. Dependencies are locked in a file that prevents them from being updated unless you explicitly tell cargo to do so.
you'd might rather take go than Rust for backend. Golang is very performan, not as much as Rust but very close to it. It's much simpler than rust and its sintaxis very practical.
Rust isn't gonna replace literally any other language. C and C++ are here to stay. And the Linux Kernel is only accepting some drivers, plugins. And it is being tested only for now because we don't want a kernel panic due to Rust's error handling.
@@alexandergarzo9415 Unless you use a buildpack to convert it, then you will not be using ts. adding a buildpack is a big source of bugs and maintenance headaches, and at times it's highly counter productive.
Next week title. Xxx replaces Rust. Many companies moved from Rust to Xxx. Have been hearing a lot these catchy titles. Move in to cloud. AWS replaces its xxx service with Yyy service. Get to know so that your org uses zzz service which is still in beta😢
Why the heck are front-end devs concerned with rust ?? Rust is being overrated/overhyped by the wrong kind of devs. Why should someone who has mainly done webdev/frontend stuff be excited for things like safety, compiled, when all they use is crap like js/react/css/html. You never really understand or appreciate something like rust if you haven't actually suffered through the the problems rust tries to fix.
WASM, performance, backend+Frontend interoperability, safety (TypeScript isn't used because people don't have anything to do at work). People are moving on from React, because it is not the end of development, and there is pain and room for improvement
also, WebAssembly isn't able to "run anywhere". It still relies on something to compile it into the final machine code. That something (whether it is a browser or wasm runtime) will need to be installed on the host machine. That's not to say it isn't very portable, but I wouldn't necessarily say it is more portable than javascript right now
It is the opposite. Things like byte code exist in order for code that is compiled once to ne run on many platforms. The fact that Rust is compiled to binaries does not make it more portable, quite the opposite. In Java you will download the same libraries no matter whether you use Windows,MacOS,Linux, whether you use x86 or ARM. With languages that compile to machine code you need to compile the code separately for every platform.
Using rust for everything doesnt make any sense to me. Most companies you mentioned has enough budget/resources to handle Rust's complexity during a product revamp. Also they might have their own reasons as well. For almost everyone else i think we can start with whatever you know, get the product running/earn revenue and then, maybe IFF you have a real reason moving to Rust. I see this hype everywhere to replace everything with Rust, even writing webapps now
Both TypeScript and Rust are powerful programming languages that have their own unique set of features and benefits. TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. It is designed to make it easier to write and maintain large JavaScript applications by adding features like static typing, classes, and interfaces. TypeScript is particularly well-suited for building large enterprise applications, as the type system helps catch bugs early in the development process. Rust is a programming language that is focused on performance and safety. It is designed to be memory-efficient and concurrent, making it a good choice for systems programming tasks such as building operating systems, file systems, and browsers. Rust also has a strong focus on safety, with a borrow checker that helps prevent null or dangling pointer references. Ultimately, the decision of which language to use will depend on the specific needs of your project. Both TypeScript and Rust are excellent choices for building high-quality software, and which one is the best fit for your project will depend on your project's requirements and your own personal preferences.
Manual ownership juggling is always too much *_BURDEN_* for business logic focus. All of the bracket cleaning languages will *_NEVER_* win GCs at project setting up speed. On the other hand, when you have to scale up, you *_WILL_* find the GC is very big performance bottleneck/cost. At that moment, you have *_NO_* other choices other than to try to optimize that weakest link by manually ownership juggling. It's never what is prominent. It's only what the stage of business you are currently thriving.
Julia seems to obtain good speeds even with a garbage collector... not really in the realm of C++ and Rust, but quite close. I wonder how it does that. All the more remarkable is that it has a simple, Python-like syntax.
No way you can be a good full stack dev with Rust, rust is really heavy lang, so also understand frontend, and I mean with nitty gritty details like DOM manipulation in a good level, well Rust is not for you, even this lang is a great one. also, I don't think you really need this for backend, it is manly system lang.
@@eugeneganshin2934 it is the same like you don't need JS learn React straightforward, sorry not working, and if you mean learn Rust first, man that is a long long journey.
@@sunny7268 Rust is easier than people think. The biggest problem is that people have assumptions about programming languages. Some of these are thrown out of the window by Rust, which requires learning a new philosophy. Plus, as a C++ programmer learning Rust (aside from the philosophy) is trivial.
Rust compared to JS is like Shakespeare compared to a baby. At least the creators of Rust thought things through and definitely took more than 7 days to create it, unlike JS which started out as one huge hack by Brendan Eich for the Netscape browser.
Who needs to learn all of these languages anymore now that chatGPT has ruined software engineering. Even if chatGPT has limitations, it'll only be a matter of time before software engineers get replaced. GPT-4 will be released in the next few months. For comparison, it's trained on 100 trillion parameters while GPT3 was trained on just 175 billion parameters.
When chatGPT spits an answer to you there is no guarantee that the code is working or making any sense. AI does not understand the meaning of what it spits out. Its just data that was composed with an algorithm.
linux did not move to rust they just introduced it to some parts of their code base. and the main goal is to decrease memory related security holes.
also rust is not going to replace js, I think of rust as a new category where SOME code bases could move into because it might be more suitable which is a good thing.
but rust is definitely not going to replace neither js nor c.
Programming languages never get replaced, this is just a fact of the universe, just look at COBOL and Fortran.
Heck, languages don't even get replaced by newer versions. Python 2 and C89 are still more alive than anyone wants them to be.
Maybe c++ though..
@@kebien6020 Yup. Replaced in computer science really means more like "we stop making new projects" as opposed to rewriting existing code in the new language. But eventually it gets to a point where nobody wants to write new projects in COBOL for instance and it's used purely to update the existing COBOL codebase that nobody wants to rewrite.
True full rewrites of software pretty much don't happen.
Not C but I hope C++ dies a painful death. What a horrible language C++ is.
Well, Rust is not meant to replace either of those. TypeScript is already a good replacement for JS, and C has a bunch of offspring languages of its own already. Rust is doing it's own thing with its borrow checker and friendly compiler, and people (me included) seem to like it.
I don't quite get the hype behind rust, it's the panacea for every problem. Kernel - rust, static website - rust, backend - rust. Your summary is quite correct, "write too much code to get small things done". Your js code is simple and with a glance I can read it and even debug it without running, while the rust code overflows off the screen only for the declaration of the method signature. The whole argument about being fast does not make sense, because few years ago the hype was python and JS. What speed are we fighting for, when we've mindfully chose programs built using them? It's clear that there is a tradeoff, and for a pretty long time people were OK with that tradeoff, now for some reason, all software is too slow for us and everything needs to be rewritten in rust. The same analogy can be made using ORM, ORMs are slow, hand written queries are fast, but when developing hand written queries can be a cascading nightmare. Rust is good, but it has it's domains, using it for everything, like JS devs creating website wrapped desktop apps is not OK. It's a degression from all the computer advancements that were made.
This is the best rebuttal is the history of rebuttals. Nothing personal just facts!!
I agree Rust shouldn't be used for everything. A web server is probably not where it excels.
But the comparison to JS is unfair because the JS code was already using an underlying library (Express) and JS being a high-level language already takes care of many relevant web features because they're written into std. The JS code has just abstracted all that away. Imagine if he had to try to explain Express' source code as well.
A C++ web server would be more comparable, and likely would have a similar amount of code. But I still wouldn't recommend using C++ for a web server, for the same reasons.
Code maintainability is incredibly important, and I would say Rust should mostly be used where it has an impactful performance advantage.
" The whole argument about being fast does not make sense, because few years ago the hype was python and JS " there was no hype for speed of python ever, wtf are you talking about?
@@aakarshanraj1176 Exactly, there was no hype for speed back then, the main focus was the code being maintainable, please read my comment again.
@@user-dc9zo7ek5j The reason could be that we already had speed because people used C++/.NET/Java but if the codebases were unmaintainable then more maintainable approaches would be attractive. Then maybe after people started using JS/Python they realized what they had lost in the process. And now they want both?
Packages are well documented, and if you see that your compiled rust code has a high response time compared to the nodejs code, know that something is wrong with your rust code, and i think it s coming from the db implementation.
I think he isn’t closing the db connections
@@giacomoarienti that problem would be noticed if he did send too many request, but straight up the first request was slow. but idk u might be right
1:10 - missunedstanding. Rust has memory leaks. Even in safe code. As simple as `std::forget(my_vec)` or `my_vec.into_boxed_slice().leak()`. And also possible to happen in less obvious context - rc-loop is the reason why `forget` and `leak` are novadays safe functions (pre 1.0.0 they were considered unsafe). Mem leaks are safe.
Sure. A more accurate statement would be that it's hard to leak memory by accident.
Yes, but that is on purpose.
The vast majority of memory leaks in something like C is forgotten pointers and dangling references, which are guaranteed to not exist in Rust.
If you on purpose use Rc, which is said in the documentation that can achieve memory leaks, then you know what you are getting into.
The best solution is to not use Rc unless it is literally the only thing that can solve your problem in a meaningful way.
Most people do not even know what Rc is, so they are memory leak safe.
@@JackDespero Honestly not sure if any decent Rust programmer wouldn't know what Rc is. It's one of the basic heap allocated types along with Box. I'd say it's pretty essentially to know that one since it's useful for a variety of applications.
when they said this and that will replace c or c++, I heard many times since numbers of years but end up as a dream. keep dreaming folks..
C will be always there because He is the KING, C++ soar much higher than today keep my word
I learn rust since about a year and at first I had similar problems you had with messy files and many "failed" attempts to implement something. One of the most frustrating differences in rust is its efforts to make global static variables unattractive and supress their use. But it encourages you to try other (often better) approaches without the global. For example with the database connections. I don't know how rocket works since I didn't work with webservices yet. But I'm sure there is a way to register a shared variable for the endpoints. If not it's not to difficult to create a "static mut" variable and a (unsafe) setter for it. It isn't the most elegant solution though.
Edit:
Also the documentation in rust is really hit or miss. Many libraries (including std) are super well documented. But some just aren't and that's the authors fault, not the language. The language actually makes writing documentation really easy since it includes doc comments directly to the crates io website in a nice and uniform format.
Regarding the amount of code, me coming from c++, c# and Java don't really think it's any different in the amount compared to those.
A rust video!! I've been waiting for this! :) Great video, as always!
Thanks akhi
How do I add English subtitles/caption for this video? UA-cam's auto-generated captions often get your words wrong, and I want to fix them.
Edit: Uh, it took 24 minutes to caption 3 minutes' worth of video... I guess your accent is clear enough for humans. Maybe I should've just opened up the transcript and watched for corrections rather than captioning the whole thing.
0:00
So if you've been hearing a lot about Rust lately, why a lot of developers, companies and teams try to adopt Rust into their ecosystem and move away from JavaScript, C, and C++, or even Node.js.
So in this video, I'm gonna take a look at Rust, why it's super cool, also I'm gonna see why a lot of people are preferring Rust vs something like Node.js, also I'm gonna take a quick look on two projects, and compare them side-by-side for Rust and Node.js.
So you're probably wondering why a lot of developers are interested in Rust, as well as like why so many teams, developers, and companies particularly, are moving from old codebases from like, JavaScript, Java, C, C++, into Rust itself.
There's actually a couple different reasons for me I would choose Rust compared to other ones because I've been trying Rust for the past couple of weeks, and it's more like 2 weeks when I started learning and using Rust, and actually trying to build a project using Rust.
So the first, and most important one: It's new. Which means it provides and it brings all the new design patterns, all the awesome features and syntax of all the languages we love and developers like, it brings them to the table.
It's also very very safe. It doesn't have memory leaks, it doesn't have CPU bottlenecks, it controls everything and it controls it super well, as well as when I talk about safety here, it has no Garbage Collector. Because most of the time, for languages like JavaScript or maybe um, Python, those are the kind of languages that, you know, it gives you really decent performance, but they all use a Garbage Collector, so it has like a good side and a down side.
And for Rust, it literally ignores that Garbage Collector, and it does use the borrow checker. And as well as because Rust is a compiled language, not interpreted like JavaScript and Python, and that code gets compiled down to binaries and native binaries that can run literally anywhere.
And there are actually many, many companies that have moved from older languages, like they were using for example C, C++ for like, native code, and some of these companies are like Dropbox, Cloudflare, Figma, the beloved Figma we all love and we all use, Shopify in here, Linux Kernel. Yes, you're hearing it right.
So if you take for instance for example Figma and how they were (been) able to migrate from the old JavaScript implementation, (their own,) they moved from TypeScript into using Rust for their like, multiplayer kind of system.
They've seen huge difference when it comes to memory bandwidth, or memory usage, and as well as like CPU bottlenecks and how CPU was eaten up before, and after. It's actually incredible how it took the memory usage from like, 4.2 Gigabytes on the TypeScript implementation, and when moved to Rust, it became something like 1 Gig, it's crazy, and that's what Rust is actually capable of doing.
So, because how crazy Rust is, and what I've heard from the community, either on Twitter, UA-cam, or just like, literally everyone is talking about Rust and how cool it is, well, I actually decided to, you know, take Rust, and give it a try.
2:58
A bunch of companies, like 10 or 20 that handle millions of requests per day, or have applications that are so resource intensive that going with rust makes sense.
The biggest drawback about Rust for me is that it's very hard to find some friendly tutorial/crash courses like in JS/TS world. For me it's hard to learn a language just from documentation.
Also it seems like a very hard to learn language for me coming from typescript background...
I disagree. The rust docs and books are FANTASTIC. It's just the language is used for more difficulty problems.
@@EllipsesDots I can’t learn just from theory, documentation is not enough for me. I need real world examples, demo apps, etc to understand the theory. But apparently I’m just a bad programmer.
@@Zagoorland no dont worry i used rusty professionally and the libraries docs are dogshit
I got your point since I am having hard time to understand through the documentation. But the thing is that many good developers are good at implementing apps based on documentations. Since they know how to follow/read the documentation very well, they don't have any problems for building apps with real world app since they already know what is required for the specific architecture. This is also one thing I am trying to learn; learning code through documents, not by the tutorials from the udemy or youtube.
Plus,,,, all those good devs are saying that Rust Documentation is amazing too...
@@Zagoorland there's always someone on the internet who will tell you the docs are good, dont get discouraged
Good video comparing the developer experience with creating a simple auth server with NodeJS vs with Rust -the cons of Rust mostly just come with it not being widely adopted yet and good to point out. I think the title is clickbait however because you don't say Rust is better than TypeScript/JS -just comparing with a simple example.
Meet Rocket package looks like a bit abandoned. Latest release in may 2022.
"Rust is the answer and you know that for sure" -John Lennon, Mind Games
Just finished a rust live chat server with actix web.. it's truly great. I love everything about rust except its bad syntax.
Why bad? Other than the constant juggling between &str and String, I didn't find anything TOO annoying... Of course, you need to know about borrowing and ownership, that's the trade-off that you have to make to gain C++like speeds without doing the memory management yourself.
Use C & Assembler- it is smaller, no garbage collector, compiled... and has normal syntax unlike Rust)))
I wouldn't exactly call C syntax as normal, however I agree with your usage of the HLO language and its destination!
It is a pity that Rust has so awful syntax. If it would have normal syntax like C, it would be easier to learn and maybe somewhat easier to port existing code.
Rust is definitely a good language, but library ecosystem is not yet matured and grammar is rather difficult as well as Job market is quite small or narrow. I am sure that it will have more popularity within 5 to 10 years but not at this time. Only a few of big techs are going to experiment and adopt this language to their products, so It's not ready for developers to earn money with this amazing language at least for year 2022 and 2023 I guess.
i strongly agree.
You lag behind years. What you describe, already happened
Thankfully things seem to be moving, Rust has once again breached the top 20 on TIOBE.
Lol literally I'm hearing Rust everywhere. Even web frameworks such next js use turbopack ans SWC which are both written in Rust
Turbopack and*
I don't think Rust is out to replace TS, Rust is a fantastic language and of course a lot of TS code bases can be rewritten in Rust but that just means TS was the wrong choice in the first place, TS/JS does not compete with Rust, it's a much higher level language with abstractions for different use cases. A better comparison is Rust and c/c++, they share the most traits and have mostly the same use cases. I love Rust but I wouldn't choose it over TS unless the benefits actually outweigh the cons which unless you're making high performance applications is very seldom and even so there's nothing stopping you from containerizing different concerns with different languages given your service is complex enough. Overall I think the thumbnail is pretty click-baity. In the time since 2015 when Rust launched TS has only grown and co-existed with Rust, I think a more interesting outlook is Python vs TS. Python is the true menace.
Can I please know the name of the syntax theme you are using? Thanks for the content.
The theme is Halcyon
You should also tell how long it takes to compile rust code. So hit and trail changes won't work. It's extremely time consuming.
The thing is that it builds dependencies once per update. After they are built you never have to build again and only build code after. Dependencies are locked in a file that prevents them from being updated unless you explicitly tell cargo to do so.
you'd might rather take go than Rust for backend. Golang is very performan, not as much as Rust but very close to it. It's much simpler than rust and its sintaxis very practical.
Also has a habit of deleting anything in your code your program doesn't read once you hit save
Julia is even simpler than Go and probably even faster.
next video, rust for js dev crash course
i would love that!
Nice rust introduction 👍
Can you share the tutorial code repo?
2:40 for wich company is this ?
Rust isn't gonna replace literally any other language. C and C++ are here to stay. And the Linux Kernel is only accepting some drivers, plugins. And it is being tested only for now because we don't want a kernel panic due to Rust's error handling.
Go and Rust will take over quite a lot of development it seems.
It would be great if you have beginner course videos about Rust. Because it is very difficult to find comprehensive video content
ua-cam.com/video/2vxvSMkm5Lg/v-deo.html
Only docs
Search for jon rust and primeagen
You don't build web servers from scratch, I have no idea why u said that.. Using framework and already made impl is not building from scratch.
typescript is still far good enough and very popular, powerful programming language.
but it's used mainly for frontend... don't tell me deno it's popular!
@@valikonen yes, i know that. but still,, ts will become more popular,powerful in the future
@@valikonen You can use ts in backend too
@@alexandergarzo9415 Unless you use a buildpack to convert it, then you will not be using ts. adding a buildpack is a big source of bugs and maintenance headaches, and at times it's highly counter productive.
You can theoretically establish a global connection in Rust, just use a ehhh CLOSURE?
I find annoying when a certain technology becomes all trendy all of sudden and people won't stop worshipping it. Last case was Python, and now this.
Why? Python was very successful. Until now.
Next week title.
Xxx replaces Rust. Many companies moved from Rust to Xxx. Have been hearing a lot these catchy titles. Move in to cloud. AWS replaces its xxx service with Yyy service. Get to know so that your org uses zzz service which is still in beta😢
Actually it is already out there😅
ua-cam.com/video/qAYFepR4GcE/v-deo.html
Hype.... In d end it's money related everything
Your Nodejs runtime is faster than rust wtf
Why the heck are front-end devs concerned with rust ?? Rust is being overrated/overhyped by the wrong kind of devs. Why should someone who has mainly done webdev/frontend stuff be excited for things like safety, compiled, when all they use is crap like js/react/css/html. You never really understand or appreciate something like rust if you haven't actually suffered through the the problems rust tries to fix.
rust not safe if we compare it with runtime langeges
@@baxiry.dude lol
WASM, performance, backend+Frontend interoperability, safety (TypeScript isn't used because people don't have anything to do at work).
People are moving on from React, because it is not the end of development, and there is pain and room for improvement
Yeah, I also like Wuast
1:48 compiled binaries are much worse for "run anywhere" than interpreted languages or jit compiled languages. Otherwise, great video
Not with WebAssembly.
@@JackDespero for sure. I highlighted this because the default compilation options with rust will create a platform dependent binary.
also, WebAssembly isn't able to "run anywhere". It still relies on something to compile it into the final machine code. That something (whether it is a browser or wasm runtime) will need to be installed on the host machine. That's not to say it isn't very portable, but I wouldn't necessarily say it is more portable than javascript right now
It is the opposite. Things like byte code exist in order for code that is compiled once to ne run on many platforms. The fact that Rust is compiled to binaries does not make it more portable, quite the opposite. In Java you will download the same libraries no matter whether you use Windows,MacOS,Linux, whether you use x86 or ARM. With languages that compile to machine code you need to compile the code separately for every platform.
Using rust for everything doesnt make any sense to me. Most companies you mentioned has enough budget/resources to handle Rust's complexity during a product revamp. Also they might have their own reasons as well. For almost everyone else i think we can start with whatever you know, get the product running/earn revenue and then, maybe IFF you have a real reason moving to Rust.
I see this hype everywhere to replace everything with Rust, even writing webapps now
Both TypeScript and Rust are powerful programming languages that have their own unique set of features and benefits.
TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. It is designed to make it easier to write and maintain large JavaScript applications by adding features like static typing, classes, and interfaces. TypeScript is particularly well-suited for building large enterprise applications, as the type system helps catch bugs early in the development process.
Rust is a programming language that is focused on performance and safety. It is designed to be memory-efficient and concurrent, making it a good choice for systems programming tasks such as building operating systems, file systems, and browsers. Rust also has a strong focus on safety, with a borrow checker that helps prevent null or dangling pointer references.
Ultimately, the decision of which language to use will depend on the specific needs of your project. Both TypeScript and Rust are excellent choices for building high-quality software, and which one is the best fit for your project will depend on your project's requirements and your own personal preferences.
Chat gpt
Lol stop being lazy and write your own response instead of ChatGPT's
Use the right tool for the job...
Manual ownership juggling is always too much *_BURDEN_* for business logic focus. All of the bracket cleaning languages will *_NEVER_* win GCs at project setting up speed. On the other hand, when you have to scale up, you *_WILL_* find the GC is very big performance bottleneck/cost. At that moment, you have *_NO_* other choices other than to try to optimize that weakest link by manually ownership juggling. It's never what is prominent. It's only what the stage of business you are currently thriving.
Julia seems to obtain good speeds even with a garbage collector... not really in the realm of C++ and Rust, but quite close. I wonder how it does that. All the more remarkable is that it has a simple, Python-like syntax.
lol golang here
No way you can be a good full stack dev with Rust, rust is really heavy lang, so also understand frontend, and I mean with nitty gritty details like DOM manipulation in a good level, well Rust is not for you, even this lang is a great one. also, I don't think you really need this for backend, it is manly system lang.
WASM
@@eugeneganshin2934 it is the same like you don't need JS learn React straightforward, sorry not working, and if you mean learn Rust first, man that is a long long journey.
for me ill learn rust for creating cli tools
@@sunny7268 Rust is easier than people think. The biggest problem is that people have assumptions about programming languages. Some of these are thrown out of the window by Rust, which requires learning a new philosophy.
Plus, as a C++ programmer learning Rust (aside from the philosophy) is trivial.
Rust compared to JS is like Shakespeare compared to a baby. At least the creators of Rust thought things through and definitely took more than 7 days to create it, unlike JS which started out as one huge hack by Brendan Eich for the Netscape browser.
And one year later: "Forget all what you know about Rust, this new lenguage will blow your mind..."
The benchmarks speak for themselves. At the moment, Assembly, C/C++, and Rust are in a league of their own when it comes to speed.
rust instead html
Very cool. Now, try finding a job that would hire a Rust developer
"oh, you found one? try to find one that isn't crypto."
ok
Guys, just use c#
C# does not even work for many jobs I use Rust for.
@@heater5979 example?
@@rizaanjappieperformant WebApps that even work without JS, see Leptos;
System development,WASM libs, ...
Its a incomplete lang, i will wait for native async implementation
Thanks
idk I feel like rust is overrated
Why?
thanks
Try do an eccomerce project using third parties apis with rust 😂😂 . Comeon man… who pays you to do this video
LoL, Sequelize? You, people enjoing to create a pain for your self... Use Prisma, god damn!
they're the same thing bro, why use an orm with a sql database?
make no sense
No
Go is simple, powerful, fast 🔥
Rust is just complicated
also safer than rust
@@baxiry. lmao 🤣
@@baxiry. I hope you are kidding 😂
It's rarely the case that companies use rust in production, it's like 1%
And here I was wondering why NextJS uses turbopack and SWC. Or why Linux kernel is starting to integrate Rust into its source code.
rust coders will never be real developers. Or women.
rust has memory leak..
Who needs to learn all of these languages anymore now that chatGPT has ruined software engineering. Even if chatGPT has limitations, it'll only be a matter of time before software engineers get replaced. GPT-4 will be released in the next few months. For comparison, it's trained on 100 trillion parameters while GPT3 was trained on just 175 billion parameters.
bullshit!! we've heard this for a decade now
When chatGPT spits an answer to you there is no guarantee that the code is working or making any sense. AI does not understand the meaning of what it spits out. Its just data that was composed with an algorithm.
Now thats just ignorant 😂
@@nulled7888 Tell us why
No they won't be replaced, they will just be more powerful, knowing how to utilize the ai tools to their maximum ability.
The code is just too much, Rust is kinda making things hard LOL