Almost finish chapter 4 of rust book. I must say I'm so amazed by this language. Just like the first time I learn metaprogramming ruby.
Awesome in every level. You should try learning it too! :)

Now that I've reached chapter 4. Should I include it in my CV?

My first rant is totally ignored. So sad. :(

Your joyous tone strongly suggests that you haven't got to the lifetime management part of Rust. Buckle up, your in for a bumpy ride soon.

@benhongh I honestly don't know much about lifetime yet. I haven't even tried the snippets in my terminal. :P I was just pushing the run button in snippet boxes. But I think the complexity rust has is necessary in order for it to do its job well. Thanks for giving me heads up about that road bump.

I've looked at rust, but decided to just use go instead. Guess I'm lazy ¯\_(ツ)_/¯

@yusijs How's go? Is it interesting?

@setyadi it's amazing. Fast, quick compile, easy concurrency etc. My boss tried it with a math perl program that was doing the exact same thing, and go was 9x faster!

@yusijs In terms of performance, Rust is not bad compared to Go:
https://benchmarksgame.alioth.debian.org/...

Maybe you should try rust and compare it with your perl program too.

@setyadi don't get me wrong. The way rust handles lifetime management is what sets it apart from other languages. Even if you don't plan to use rust at all it's still worth going through those concepts.

@benhongh I have a crush at rust, so I will go through that concept. Thanks for your advice. :)

@setyadi Dont get me wrong here - Rust is faster than go. But my time is precious to me, and Rust is to low on the scale for me to devote enough time to learn it. Go on the other hand is fairly straight forward, and fast enough for my usecases.

@yusijs Well, different people have different preferences. I hope your journey with go go well. :)