Python: keeps driving while pitstop people are running EDIT: Golang car being a garbage truck that weighs 10 tons with a 500 horsepower engine EDIT 2: C car driving at 1000 mph and skipping pitstop, occasionaly catching on fire
@@meninoesperto2773 Average leetcoder mindset, theres a reason why python/js cannot be used to power any realtime app of large scale. And interop with C doesn't count, thats just writing C and then attributing all the performance to JS/python
For real. I’m out here compiling UE4/5 for like 2 hours. At least it only takes that long the first time you build, and every time after that it’s like a minute at most…
@@that_guy1211 so u know that if u have like more than one (1) template it immediately slows down a lot? lots of templating in a c++ project can make it as slow as rust
Assembly is like an indestructible tire moving close to the speed of sound. But just the tire. The engineers gave up on putting together the rest of the car.
Nobody uses Python for performance (or lack thereof), it is famously slow. It does have some very useful features and fields where it excels, but speed (at any stage) has never been one of them.
@@j.r.r.tolkien8724 You do realize that I am not the one who brought up the "speed of Python" right? The entire video and title is about compilation, so yes, I fully realize this, and was merely replying to another's comment.
Assembler is actually not "fast compiling", it is not compiling at all, it is "translating" = direct reflection of ASM in text form to ASM in binary and that is much faster than reading the file from SSD.
Python is like 4 people on top of a race car changing the tires while the car goes at two km/h, but sometimes the 4 people randomly can’t figure out how to screw in the nuts of the wheel.
Rust glazers are gonna learn soon 😂😂 in 2 years everyone will regret wasting their life learning/using rust and c++ will prove superior to Java and rust and python and all goofy ahh languages
@@ZihadJoy python is interpreted, and interpret time is pretty much the same as runtime, because interpreting is going line by line through the program and doing what it specifies, which takes as long as running the program does.
Coding in Rust, I don't think compilation time is the worst experience about it. But given the single factor you consider on using Rust or not, I assume that you also don't know the best things in Rust.
once you get past the initial compilation of your dependencies, rust's incremental compilation combined with debug releases tends to make it a very tolerable experience
@@rule6elur still compiled. Machine code or not. The byte code could then be ran by either a JIT compiler or an interpreter. The actual process of running python still involves compiling one way or another.
How to use C/C++ well: - Remember to free and null each malloc'd pointer - The above rule only applies if you use the heap, you don't have to use the heap - Signed int overflow is undefined How to use Rust well: - Do countless cargo-cult programming techniques to appease the borrow checker - Don't bother making a safe doubly-linked list - Executable size doesn't matter How to use Java well: - You have no real-time guarantees (the GC will interrupt safety-critical code) - You have no guarantees that it will work at all (The JVM has every right to seppuku) - Portability is barely better than in C How to use Python well: - Be patient
Python is a interpreted language, we're talking about compiled language. Interpreted means it runs the code directly (That's why Python is slow), compiled languages convert your source code to machine code before running it, that's why C++ and other languages that are compiled are so fast.
@@GDT-Studio Kind of incorrect. Python is an interpreted language, yes; however, it is primarily just the bytecode that is interpreted. Initially, the Python code is compiled to bytecode with a JIT compiler and then is sent off to an interpreter that then runs the bytecode. Python would technically fit in this race, it's just that the pit crew would be trying to change the tires while the car is driving on the track. xd (referenced from susamogus11111's comment)
Nah we busy pitying the c/c++ devs who don't have proper toolchain tech and have 50 years of duct tape tech debt slapped together and kept running by hopes and prayers.
@@fredesch3158 that he does. For curiosity sake just checkout any meme on rust. There will be a joke about butthurt rust devs and a huge amount of replies from actually butthurt rust devs doing exactly this, it gets funny how they try to actually refute a joke.
I haven't worked with java , but i have tried kotlin recently and its awful in terms of speed , so i thought java compile time should be close to it@@theshermantanker7043
@@user-uf4lf2bp8t the thing is that python code is mainly interpreted so that's why it compiles fast(interprets fast) but actual code is slower than a snail
C++ can be fast and slow. Anyone who has compiled a large project with winrt knows how long it can take. But c++20 brought modules, which allows for incremental builds and speeds up compile times. (and is overall much much better than #include)
Nothing prevents a programmer against writing buggy code: 95% of bugs (c++/c#), which I fixed were related to business logic - no language can solve that. Also there is no problem to make a lot of errors in Rust related to the deadlocks.
"Language safety" is a joke. No language design or static analysis can protect against business logic errors, and most of Rust's "safety" features can be done by static analysis tools for C. Just because a gun has a safety lever on it doesn't mean that you should aim it at yourself and slap the hammer.
@@notjebkerman6207 i am using sarcasm I mean When you write Rust code,it takes years to compile already And If you are gonna mistakes again and again and don't abide by compiler rules then its gonna take you ages to finally compile your code.
@@mr_sauce_cooks whether u wait 5 seconds or 10 seconds for a compilation is the last concern when choosing a language rust’s compile time is high not cos of the compiler itself but its inherently more work to do the borrow checking and all the other safety things that rust has to do
I work primarily in Rust on a T420. First compile in a complex project will be relatively slow, but if you're regularly waiting on long compilations, you're doing some dumb shit.
An advanced C++ teacher i TA for said it like this: Python is like your driving an armored car with training wheels, C++ is like your in a racecar with the hood off flying at 200mph while making an engine repair as you drive
I dont think they do, but Python (at least CPython) does actually compile the source code to intermediate instructions for a virtual machine which then end up being interpreted.
Rust rebuilds whole car using a modern factory. C++ uses some archaic car parts, and reassembles large parts of the car. Golang has pluggable parts to build the car from. The golang car looks verey very retro (because almost all golang concepts are from the late 80s, early 90s or so), but it is actually very new and modern.
Never seen a comparison which values compile time and nothing else. Thats like the least valuable virtue. Especially since many times you don't have to recompile the symbols if they haven't changed.
@@pruthweeshasalian3688 yep, its funny. Could have done the same thing with C++ performance in comparison. But I guess its funnier putting Go as the fast one.
@@macicoinc9363 really? It's a one time cost. My big tech has massive server farms that run multiple builds in parallel CI/CD. Consolidating stable prebuilt libs solves having to build everything from source. While it may take a long time to build one instance, development can also multi-task. This is fundamentally what you call DevOps. I will always compromise compile time for production performance.
@@idontknowanygoodnames1498 Have you actually used Rust or C++? If you use a bunch of traits and macros, yea Rust is slow. C++ is slow if you use tons of templates. Otherwise they will both be tolerable. But both can be made slow by using "zero-cost abstractions". That's because they aren't zero-cost. They are zero runtime cost. Obviously if you do a bunch of complicated computation in the compiler, compile times will be slower. Where are you getting this idea that rustc is slower than clang or g++?
@@idontknowanygoodnames1498Only because Rust is actually getting used by people other than C++ programmers, who compare it to the compilers and interpreters in their previous languages.
@@idontknowanygoodnames1498 On an average day for Rust, it's a bit slow, but clear on what it wants. On an average day for C++, compiler has a stroke and leaves the programmer to also have one trying to figure out the problem. Then when he gets back from the hospital he either scraps half the code since it would be easier to make some new noodles from scratch than make their existing spaghetti edible. Or if they figure it out but end up taking a similar amount of time debugging as rust did compiling a working end result. Your average user doesn't write pristine C++, and it certainly isn't the most forgiving when compiling. So depends on the scenario, if you want to talk expert C++ programmer optimizing their code to compile and run efficiently, you need to look at the other side in the same scenario. Optimizations can be made to Rust projects as well, and planning ahead goes a long way for any project in any language. Plus it's not like the Rust dev will ever be stuck debugging, while the C++ dev just might.
It's true. Of course, rust has advantages in that it's faster at runtime, safer in terms multi threading smd also the compiler does a lot more thorough error checking.
@rico_1617, do you know the llvm ecosystem? Clang, as well as the rust compiler, are just syntax variations with other rules. They ultimately get optimized by llvm. Clang and Rustc just parse the language (do eventuallchecks) and feed llvm the tokens needed for compiling.
@@luigidabro It's actually even worse for Rust. Compiler frontend MUST do optimizations as well. How else would C/C++ be able to optimize out entire memory allocations? 20 lines of basic self contained code? Maybe you'll get the exact same result in C, C++, Rust and Zig, but it doesn't scale much further. It will eventually diverge and language + your language proficiency + compiler frontend starts playing the main role.
You shouldn't compare Rust compilation time with other languages, you should compare Rust compilation time with the time you average developers taken to debug in other languages.
No in fact. The most time spent in the compiler is codegen and linking bc rust relies on llvm and does everything statically. Getting the compiler in debug to split crates into dylibs automatically and maybe utilizing cranelift would grant rust much more bearable recompile times.
Nope, I program in Go, Rust, C and now Zig, anyone with that tought of "They all feel incomplete" are just wrong because they feel so good being baby sit by the compiler, unable to deal with memory management in other languages
Employee: "Boss, I already told you. This project is time-consuming. You can't speed it up, just by assigning more people into it." Meanwhile in Formula One:
Both have their use cases. Comp speed is kind of trivial though, as you only compile the finished project once. Also, with rust, the second compile is much much faster because it doesn't recompile dependencies.
![Эффект Джанибекова [Veritasium]](http://i.ytimg.com/vi/N9HlQ-XVnFk/mqdefault.jpg)
![NOSFERATU - Official Teaser Trailer [HD] - Only In Theaters December 25](http://i.ytimg.com/vi/b59rxDB_JRg/mqdefault.jpg)
The C++ car catches fire after driving off.
The Golang car weighs 5 tons.
🤣🤣🤣
Golang car also has to stop every once every km to take a dump.
@@uoweme5grand Same as me.
@@uoweme5grandLMAO Garbage Collector
😂😂😂
the rust compiler is rebuilding the entire car
And making sure the car actually works.
Rust is first reinventing the wheel and then rebuilding the entire car
@@thekwoka4707 and still it never does even after rebuilding it a thousand times.
@@meninoesperto2773rush reinvents the wheel. Then reinvents the second wheel. Then third and fourth. Seperately.
@@br0ken_107 skill issue
Python: keeps driving while pitstop people are running
EDIT: Golang car being a garbage truck that weighs 10 tons with a 500 horsepower engine
EDIT 2: C car driving at 1000 mph and skipping pitstop, occasionaly catching on fire
The car also drives at 2 kilometers per hour
Nice one
python isn’t compiled
@@benjamin4736 Well "aktually", python has a compilation phase, where it basically decides where to look for variables (in global scope or local).
Python isn't compiled, so it doesn't have a compilation time.
rust compiler is an airplane checklist
Good observation
Also generating unnecessary slower code 😕
@@tensor5113 Rust generates unnecessary assembly code. For big values of "n", an O(n^2) algorithm probably never run faster than an O(n) algorithm.
@@meninoesperto2773 Average leetcoder mindset, theres a reason why python/js cannot be used to power any realtime app of large scale. And interop with C doesn't count, thats just writing C and then attributing all the performance to JS/python
@@tensor5113 this is the most retarded thing I have read in a while.
I'm watching this while my rust program is compiling because it is taking too long
For anybody wondering: That wasn‘t a joke
@@Zwiebelgian what were you compiling though ?
@@RishitSrivastava007 a personal project with 600 dependencies
@@RishitSrivastava007 A personal project with a total of 600 crates
@@Zwiebelgian dear god
i’m convinced y’all have never written any c++ past like a homework assignment
In the school days i done all my homeworks assignments in C++ to learn more about the language.
Years later now i am Python Programmer.
i have, lol
For real. I’m out here compiling UE4/5 for like 2 hours. At least it only takes that long the first time you build, and every time after that it’s like a minute at most…
@@that_guy1211 so u know that if u have like more than one (1) template it immediately slows down a lot? lots of templating in a c++ project can make it as slow as rust
@@JoyousUnicorn i've never used nor heard of templates until you replied to my comment, lol
Meanwhile, Assembly is running on indestructible tyres that don't need replacing.
You still have to compile assembly, it's just super quick
only took 8 years at the factory to make, for a specific customer
But you need different tyres for each track. All coming with their own type of screws, of course.
Assembly language is like an almost-zero friction tire with every bolt being different
Assembly is like an indestructible tire moving close to the speed of sound. But just the tire. The engineers gave up on putting together the rest of the car.
Python is like Arabs changing tires while driving
E o carro capotando
Nobody uses Python for performance (or lack thereof), it is famously slow. It does have some very useful features and fields where it excels, but speed (at any stage) has never been one of them.
@@ForeverZer0 You realize that we're comparing compilation time and not running speed right? But then again python is interpreted not compiled.
@@j.r.r.tolkien8724 You do realize that I am not the one who brought up the "speed of Python" right? The entire video and title is about compilation, so yes, I fully realize this, and was merely replying to another's comment.
bro its not a performance comparison, you know what compilation mean?
*Assembler completely forgets it even needs pitstops due to how short they are*
Assembler is actually not "fast compiling", it is not compiling at all, it is "translating" = direct reflection of ASM in text form to ASM in binary and that is much faster than reading the file from SSD.
@@Bukuzoid🥸
This comment section needs to learn the difference between compilation speed and running speed. Like jeez...
When you only work in interpreted languages, you never get to learn the difference.
@@michawhite7613Laughs in Scala
Even worse, script kiddies don't even know what a programming language is (they probably think it's bashing the keyboard with a hacker typer)
100% agree
@@susamogus11111 I think it's just some old red-eyeers can't learn anything new
Everybody gangsta until assembly language pulls up
C is already in space
If it doesn't explode before reaching space.
Houston, we have a problem💀
C means speed of light.
In void
No low-level language in race
Python is like 4 people on top of a race car changing the tires while the car goes at two km/h, but sometimes the 4 people randomly can’t figure out how to screw in the nuts of the wheel.
LMAO best description!!
Inside an airplane. God forbid Python ever has to drive on its own.
so like the ferrari pit stops
"I see you play games all day".
"Mom, it's compiling."
Rust: debugging today for next year race lol
In rust you don't debug, you just wait for compilation and it works
Notice how the C++ driver is not even wearing a helmet with that dubious sports car...
Helmets are for quiche eaters.
Where we're going, we don't need memory safety.
Tell me you never coded C++/Rust without telling me you never coded C++/Rust
я компилировал проекты на go, c и rust так что да есть с чем сравнить)
Why? It’s true that Rust doesn’t have a very fast compiler
Rust glazers are gonna learn soon 😂😂 in 2 years everyone will regret wasting their life learning/using rust and c++ will prove superior to Java and rust and python and all goofy ahh languages
@@randomperson5454source?
it's true though. however compile time != code quality
If this was about runtime speed, python would be like the first one but the car wouldn't have to stop because its top speed is 1 meter per hour
python is not compiled and doesn't need compilation
@@ZihadJoypython is both interpreted and compiled
I wasn't talking about compile time, I was talking about runtime
@@Smurdy1 the video is not talking about run time.
@@ZihadJoy python is interpreted, and interpret time is pretty much the same as runtime, because interpreting is going line by line through the program and doing what it specifies, which takes as long as running the program does.
C compiles faster than Go 🔥🔥🔥
C:
Complied while you blinked.
As a Golang Developer, you got the wrong F1 team pitstop.
as someone who worked with C++ and now learns Rust, it's so true
I've had worse compile times in C++ than in Rust, dunno if my experience was wrong.
@@Luxalpa maybe you are too noob for c++ ? XD lolz and btw how big is Hello world program in rust ? 15MB ? or 100MB ?
Same here, Moraletherapy.
@@Phantom-lr6cs Bro a hello world program in rust is like 3 lines of code.
fn main() {
println!("hello world");
}
@@Luxalpa I've noticed that heavy usage of nested templates is an overkill for compilation time.
THE VIDEO BUFFERED AT THE FIRST PIT STOP IM DYING
The Rust compiler sends the car back to R&D.
thats a really good analogy of compilation times lol
Good things take time to be built 👍🏻
Well, the same says it all "RUST"
With rust you'll never have to change the tyres ever. 😂
Maybe what you mean is during the first compilation, for the first compilation Rust is very slow, but not for subsequent compilations
That's because is using cache (already compiled code)
Most C/C++ compilers are also like this unless you change a header file somewhere that a lot of files are using.
Missed C man
Assembly is the car and when needed creates its own replacements team on the fly.
Meanwhile, Machine Languages, And Binary Codes :- ☠️
FORTRAN, COBOL,…
I was gonna learn Rust, because I am sick of slow C++ compilation speed ... but the video and the comment section made me change my mind 🤣
Coding in Rust, I don't think compilation time is the worst experience about it. But given the single factor you consider on using Rust or not, I assume that you also don't know the best things in Rust.
still, this short vid made me chuckle.
once you get past the initial compilation of your dependencies, rust's incremental compilation combined with debug releases tends to make it a very tolerable experience
Rust has one advantage thou... most of the time you only compile once and it works
@khhnator c++ does the same thing. In fact most languages do the same thing.
nope Python is still figuring out whether it has to put Wheels or Engine
it somehow got its engine out
Python is not a compiled language…
Bro, what python is doing here?
@@PR0MINENCEit gets compiled to byte code before going through an interpreter
@@notaidan2 byte code it's not machine code, it's two different things.
@@rule6elur still compiled. Machine code or not. The byte code could then be ran by either a JIT compiler or an interpreter. The actual process of running python still involves compiling one way or another.
meanwhile, lua driving while pitting😅
Python: randomly reverses mid pitstop and drives over one guy because the driver mistook a call sign
C++: Segmentation fault, core dumped
Skill issue
segsfault 🤫
Git gud bruh
Skill issue
How to use C/C++ well:
- Remember to free and null each malloc'd pointer
- The above rule only applies if you use the heap, you don't have to use the heap
- Signed int overflow is undefined
How to use Rust well:
- Do countless cargo-cult programming techniques to appease the borrow checker
- Don't bother making a safe doubly-linked list
- Executable size doesn't matter
How to use Java well:
- You have no real-time guarantees (the GC will interrupt safety-critical code)
- You have no guarantees that it will work at all (The JVM has every right to seppuku)
- Portability is barely better than in C
How to use Python well:
- Be patient
Impressive. Very nice. Let's see Rust's segmentation faults.
Oops, I have solved race conditions and memory safety at compile time again. DAMN!
@@nubuntoit doesn't prevent general race conditions, just data races.
@@user-uf4lf2bp8t true, you can still deadlock things if not careful
@@nubunto In my experience sometimes i caused race conditions and deadlocks, trying to satisfy the borrow checker when i still wasn't used to it lmao
would love to see an example
python laughing in corner😅😅
c just takes a quick glance and sends it off before it can make a full stop
You forgot Python, change tires by hand
Um… I think you’re on the wrong race track. The scripting languages are over there… 🔥🔥🔥
"compilation speed"
Python is a interpreted language, we're talking about compiled language. Interpreted means it runs the code directly (That's why Python is slow), compiled languages convert your source code to machine code before running it, that's why C++ and other languages that are compiled are so fast.
-while its running
@@GDT-Studio Kind of incorrect. Python is an interpreted language, yes; however, it is primarily just the bytecode that is interpreted. Initially, the Python code is compiled to bytecode with a JIT compiler and then is sent off to an interpreter that then runs the bytecode.
Python would technically fit in this race, it's just that the pit crew would be trying to change the tires while the car is driving on the track. xd
(referenced from susamogus11111's comment)
Just Zig it.
🗿☕👍
Erlang/Elixir zooms past changing tyres and more wherever it feels like 😅
Rust compiler making sure that everything is ok
Butthurt Rusticians in 3, 2, 1… 😂
Nah we busy pitying the c/c++ devs who don't have proper toolchain tech and have 50 years of duct tape tech debt slapped together and kept running by hopes and prayers.
@@thegoldenatlas753 y'know you're proving their point, right?
Crustacians not Rusticians
@@thegoldenatlas753 You must have felt so cool typing that inaccurate shit. 🤡
@@fredesch3158 that he does. For curiosity sake just checkout any meme on rust. There will be a joke about butthurt rust devs and a huge amount of replies from actually butthurt rust devs doing exactly this, it gets funny how they try to actually refute a joke.
but rust has check feature that anticipates compilation errors and when compilation is done...completely safe
rust: turtle
c++, golang: rabbit
who finish first in the story?
@@youraccountissuspended multithreading
@@twelvetican 💀
@@twelvetican😮
@@youraccountissuspended the fastest one did
You guys go change your tires, while I'm here ZIG'ing on a Jet plane
As a rust compiler , can confirm 😂
Java was so slow it didn’t compile in time for this video
javac compiles pretty fast, if you're trying to make fun of Java for having a slow runtime you've completely failed
I haven't worked with java , but i have tried kotlin recently and its awful in terms of speed , so i thought java compile time should be close to it@@theshermantanker7043
Java compiles extremely fast compared to C++ or Rust
Compiling and running java apps is pretty much instantaneous.
Python: changes tyre while moving
Python slow as shit
@@Reloadman99yet compile time is very fast, which is what this video is about.
@@user-uf4lf2bp8t the thing is that python code is mainly interpreted so that's why it compiles fast(interprets fast) but actual code is slower than a snail
@@user-uf4lf2bp8t... Python isn't compiled
@@Cargren18 obviously, but the video is about compile time. Bytecode generation is fast.
Rly thought that was gonna be Ferrari but this is even better
C++ can be fast and slow. Anyone who has compiled a large project with winrt knows how long it can take. But c++20 brought modules, which allows for incremental builds and speeds up compile times. (and is overall much much better than #include)
RUST compiler disciplines you to write the bug free code in one way else....
Nothing prevents a programmer against writing buggy code: 95% of bugs (c++/c#), which I fixed were related to business logic - no language can solve that.
Also there is no problem to make a lot of errors in Rust related to the deadlocks.
"Language safety" is a joke.
No language design or static analysis can protect against business logic errors, and most of Rust's "safety" features can be done by static analysis tools for C.
Just because a gun has a safety lever on it doesn't mean that you should aim it at yourself and slap the hammer.
@@notjebkerman6207 i am using sarcasm
I mean When you write Rust code,it takes years to compile already
And If you are gonna mistakes again and again and don't abide by compiler rules then its gonna take you ages to finally compile your code.
i disabled incremental compilation so that i can still bill for 10 min compile times
So, thats's why cosmic desktop took so long to upgrade
Assembly : "Hold my beer..."
I love rust and this used to be so true a few years back 😂😂
still is
@@surajraika7821 not even close baby
If you use Bevy Engine (Rust)... oh my god, my laptop was burning like hell. libGDX (Java) in comparison is very fast.
@@surajraika7821 my game engine compiles in 3 seconds.
@@nubuntoit does take THAT long
programmers: i got the top macbook pro at $4k cos it has the fastest cpu ever
also programmers: i use golang cos it compiles faster
it's for the low end pc, a good programmer is a one who thinks worst case
@@mr_sauce_cooks whether u wait 5 seconds or 10 seconds for a compilation is the last concern when choosing a language
rust’s compile time is high not cos of the compiler itself but its inherently more work to do the borrow checking and all the other safety things that rust has to do
you can use the same CPU for 4 time less the price
@@Brad_Script can you mention it?
I am tired of laptop incompatible with linux specially Gaming. due to that at any cost I need to have mac pc
I work primarily in Rust on a T420. First compile in a complex project will be relatively slow, but if you're regularly waiting on long compilations, you're doing some dumb shit.
An advanced C++ teacher i TA for said it like this: Python is like your driving an armored car with training wheels, C++ is like your in a racecar with the hood off flying at 200mph while making an engine repair as you drive
Rust feels like the GTA 5 loading screen back when it was very unoptinised
those who are mentioning python, do you know what compilation means?
I dont think they do, but Python (at least CPython) does actually compile the source code to intermediate instructions for a virtual machine which then end up being interpreted.
python is JIT compilation, you just don't see it like that
CS students think shitting on python is cool
@@ciso well we can compare bytecode generation with compilation, but even so its not the same
@@wontcreep but bytecode is not machine code
Rust rebuilds whole car using a modern factory. C++ uses some archaic car parts, and reassembles large parts of the car. Golang has pluggable parts to build the car from. The golang car looks verey very retro (because almost all golang concepts are from the late 80s, early 90s or so), but it is actually very new and modern.
I spoke about rust and golang for the first time 3h ago
And then I see this short, someone's listening 💀
cout
Java compiler rebuilds the entire car and makes it worse lol
Yeah, I don't mind getting my compiling take its time, but when it comes to running, C++ and C are like rockets close to Golang.
Rust might be slow to put/compile, but it executes fast during the race
True. Next, show the C++ car driving straight into a wall.
Never seen a comparison which values compile time and nothing else. Thats like the least valuable virtue. Especially since many times you don't have to recompile the symbols if they haven't changed.
It's not that deep. This is meant to be entertaining, not informative or comprehensive.
@@pruthweeshasalian3688 yep, its funny. Could have done the same thing with C++ performance in comparison. But I guess its funnier putting Go as the fast one.
It’s very valuable. When a project reaches sufficient mass the compile time cripples development
@@macicoinc9363 really? It's a one time cost. My big tech has massive server farms that run multiple builds in parallel CI/CD. Consolidating stable prebuilt libs solves having to build everything from source. While it may take a long time to build one instance, development can also multi-task. This is fundamentally what you call DevOps.
I will always compromise compile time for production performance.
it's a meme bro, why are you so hurt like that?
Where did people get this idea that Rust compilation is so much slower than C++? They are on par with eachother.
No, rust is notoriously slow
@@idontknowanygoodnames1498 Have you actually used Rust or C++? If you use a bunch of traits and macros, yea Rust is slow. C++ is slow if you use tons of templates. Otherwise they will both be tolerable. But both can be made slow by using "zero-cost abstractions". That's because they aren't zero-cost. They are zero runtime cost. Obviously if you do a bunch of complicated computation in the compiler, compile times will be slower. Where are you getting this idea that rustc is slower than clang or g++?
@@idontknowanygoodnames1498 and so is c++?
@@idontknowanygoodnames1498Only because Rust is actually getting used by people other than C++ programmers, who compare it to the compilers and interpreters in their previous languages.
@@idontknowanygoodnames1498 On an average day for Rust, it's a bit slow, but clear on what it wants. On an average day for C++, compiler has a stroke and leaves the programmer to also have one trying to figure out the problem. Then when he gets back from the hospital he either scraps half the code since it would be easier to make some new noodles from scratch than make their existing spaghetti edible. Or if they figure it out but end up taking a similar amount of time debugging as rust did compiling a working end result. Your average user doesn't write pristine C++, and it certainly isn't the most forgiving when compiling. So depends on the scenario, if you want to talk expert C++ programmer optimizing their code to compile and run efficiently, you need to look at the other side in the same scenario. Optimizations can be made to Rust projects as well, and planning ahead goes a long way for any project in any language. Plus it's not like the Rust dev will ever be stuck debugging, while the C++ dev just might.
Java: wheel wrench breaks
Did you guys see C passing by right before Golang? Ka-chow!
However, compared to "C++", "Rust" is not as quick to shoot itself in the foot
how does it feel
to be objectively wrong?
He’s write though I write all 3 for work
It's true. Of course, rust has advantages in that it's faster at runtime, safer in terms multi threading smd also the compiler does a lot more thorough error checking.
@rico_1617, do you know the llvm ecosystem? Clang, as well as the rust compiler, are just syntax variations with other rules. They ultimately get optimized by llvm. Clang and Rustc just parse the language (do eventuallchecks) and feed llvm the tokens needed for compiling.
@@luigidabro It's actually even worse for Rust. Compiler frontend MUST do optimizations as well. How else would C/C++ be able to optimize out entire memory allocations?
20 lines of basic self contained code? Maybe you'll get the exact same result in C, C++, Rust and Zig, but it doesn't scale much further. It will eventually diverge and language + your language proficiency + compiler frontend starts playing the main role.
@@rico_1617 Rust is not faster than C++
If you want C's speed without C's kill count...
I am a software developer with more than 10+ years experience. But never heard programming language called rust.
Meanwhile Java & Python ?
python is not a compiler based language brother
those are interpreted languages. Java is converted to an intermediate language that then is compiled to machine code, and python is written in C.
Javac compilation is very fast, Python is interpreted (no need for compiling)
@@noturgokuxd ok brother
Fr JIT are basically the guys hanging onto the car while it's driving and somehow managing to still change the tire
You shouldn't compare Rust compilation time with other languages, you should compare Rust compilation time with the time you average developers taken to debug in other languages.
Yeah, and also take into consideration how much time is spent fighting with BC/static analysis.
First I'd have to learn it. But at 42 tears old I don't have three decades to spare.
found the rust dev
No in fact. The most time spent in the compiler is codegen and linking bc rust relies on llvm and does everything statically. Getting the compiler in debug to split crates into dylibs automatically and maybe utilizing cranelift would grant rust much more bearable recompile times.
C you need to raise the pit stop crew from birth
Okay, but the Rust car is actually a plane.
who cares compilation speed ;)
Have you try to compile Android?
Takes 20 minutes to compile some of our stuff at work. Changing one line of code and having to wait 20 minutes is not fun
@@macicoinc9363are u rewriting windows in rust or something
When you understand Rust you just can't use another language seriously again. They all feel incomplete, i know they are not but they all feel that way
Nope, I program in Go, Rust, C and now Zig, anyone with that tought of "They all feel incomplete" are just wrong because they feel so good being baby sit by the compiler, unable to deal with memory management in other languages
@@_garicas thanks for letting us know how you feel
@@user-tb5re6zs2r you're welcome
My man wishes c++ compiled this fast
I was expecting "Compilation speed: Python" and he just drives right on through the pit stop.
I am Rust developer...see you in a few days.
😅🤣
Hahahaha fixing car for next year race
Wow that’s a low quality post if I ever seen one
Employee: "Boss, I already told you. This project is time-consuming. You can't speed it up, just by assigning more people into it."
Meanwhile in Formula One:
if compilation speed was everything, people would just write everything in javascript.
oh wait...
C++ car driver does not feel anything even though his tyre got punctured a long ago.. 😅😅😅
checking both Go and Rust at the same time now. Rust really takes it time.
Both have their use cases. Comp speed is kind of trivial though, as you only compile the finished project once. Also, with rust, the second compile is much much faster because it doesn't recompile dependencies.
Python: pitstop while the car is moving.
Also python: moving at the snail pace.
Any of this is more fun than the programming itself 💀
Julia just randomly stops on track to switch a single tire
"In Rust we tRust'😊
Python doesn't have tires. It's being towed by the other languages.
Now let's talk about compilation difficulty
C++: segmentation fault (the car explodes)
Let's give a round of applause to all of the programmers who have to deal with these scenarios 😆🤙🏼
A templated C++ program would probably the rust program.
Don't forget the python interpreter, it takes the car and gives you a bike instead.