200M Speed Comparison :: Python Vs Rust | Closer To Machine Code

[@laabiditarek1122]

You can optimize the python code by setting count to 200000000 before the loop :)

[@BekBrace]

cool, a valid optimization suggestion but I don't think it will drastically change anything :)

[@meqdaddev4341]

Python next feature: Implementing the Python popular packages using Rust with just a Python wrapper 🤣

[@BekBrace]

Nothing is impossible 😂

[@BRISKLYHIDDEN]

😂😂😂

[@timothyking3759]

rust: 0.70 seconds; matlab: 0.17s seconds here's the matlab code count = 0; startTime = tic; for i = [1:2*10^8] count = count +1; end toc(startTime)

[@contentpump2537]

You even forgot to enable Optimizations on the Rust side, so it might be slightly to infinity faster depending on if the rust compiler can tell that the result is always going to be 200_000_000.

[@BekBrace]

So true (your second part of the statement), I haven't forgotten though, it was deliberately written this way.

[@falkez1514]

please post a video to tell us when python is done!

[@BekBrace]

😂😂😂

[@BRISKLYHIDDEN]

😢

[@ggsap]

This test is still taking into account the timing code. Instead use the time command. Also why no optimizations are enabled for rust?

[@BekBrace]

Thanks, I didn't know about optimization till a video later -_-

[@vladyslav-py-js-cs]

It was predictable😂

[@BekBrace]

I want to test Haskell, C and Rust in the next one :)

[@vladyslav-py-js-cs]

@@BekBrace Wanna see it😁 it's gonna be fun

[@CosmicSilhouette]

Since both C and rust are closer to machine than python will the difference in speed be minimal and more unpredictable?

[@bekbraceplus]

Absolutely true, I am doing that test this week, and for more spicy flavor I'll add Haskell to the game ! Stay Tuned!

[@jaroslavhuss7813]

Here again, please, use --release flag with Rust... IT would be 0.0000000....

[@BekBrace]

Again, learnt that lately - thank you

[@mr.michaelsomeone5667]

Use iterarors instead of "for" cycles in Rust

[@BekBrace]

Thank you, Michael, I will do in the next Test video 👍🙏

[@andreasmastronikolis3987]

just checked on my machine with c++ ... 0.05 seconds.

[@BekBrace]

What the .... 😲😲😲

[@Maxawa0851]

You sure the compiler didnt just optimize the loop with a count = 200000000?

[@oskwon72]

How about vs. Golang or vs. C++?

[@BekBrace]

I guess we'll figure out soon 😉

[@lmnts556]

Try to do it with cython or even numba.

[@BekBrace]

I should

[@gustavojoaquin_arch]

Heil Rust

[@BekBrace]

Hail to Rust 😁

[@josephusophia]

i don't think this comparison is fair especially rust is compiled and python is an interpreted language

[@BekBrace]

No it's not you're right, but just to show the difference 😉 Correction for you: Python is an interpreted language, true, but it's also compiled into bytecode which is done automatically and after execution. But still, doesn't help I know 😂. In the next one, I'll show you rust vs two other languages.

[@josephusophia]

@@BekBrace What about comparing production time over execution time ration When you calculate the time needed to write the code and divide it by the execution time. That would be very interesting

[@BekBrace]

​@@josephusophiaI'll do that between Rust, Node, C and Python

[@waelmohameddd]

Please C next video, man

[@BekBrace]

Done

[@furiousmilk6559]

what abt c++ and rust?

[@BekBrace]

I have never coded in C++, however I do C and I'll make the next Test with C

[@furiousmilk6559]

@@BekBrace nice, I've never tried rust but I could do a quick c++ to compare to your rust code iyw

[@cloudcoder01]

This is not fair .. where is Mojo🔥?!!!

[@BekBrace]

Somewhere

[@FreePizza007]

Try pypy.

[@BekBrace]

.