#hackgineering

[w0rmei]

STARTS CHOGKGING STARTS COUCUhg ou HACKGIN wheDZIEZNG im EHEEZINF FOR FUCKGIN AIR wuachak chACKCS HAND CHCOUGHS HAEL[EP ME HEP ME HELP ME ochOKECOUHCOCUHCOCUHCOUCHOUCH hoaua hcACOKAKSPITST AN DNSSEEZES COUGH COUGH SOUHA AAH KACUAWAUU UEUE UE.. UEUUE... UEU EU. .EU.U.U.EUUEUUEU...

[hackgineer]

Getting Rusty

In the ongoing effort to teach an old Data collector new tricks, with a steadfast  desire to stay focused and undistracted, lets.....

learn a new coding language! 

why Rust? to be perfectly honest, it started with a small clickbait ad at the bottom of my screen one day. A quoted headline about this new language creating a small buzz in the industry, like a new undiscovered vacation island...click!

I also like the name. For me, it sort of embraces that feeling I get when I start to think about learning to code again, its the same feeling I get when I find rust forming on a prized metallic possession. 

Rust is touted for runtime speed, safe memory usage, and advantages using multiple processors, making it ideal for web applications and services requiring high performance, CLI applications and embedded devices.

Lastly, in my research I also became aware that Rust has a reputation of being hard to learn. That alone is enough of an invitation to try.

so then, lets get started.

I dug up an old macbook pro running OS X El Capitan 10.11.6 to use for this coding project. Rust can be installed on both Unix and Linux, an Windows.

I used an install script that can be found at rustup.rs like so:

step 2: choose option 1.

Install finished. Woohoo!

step 3: Check cargo install and setup a project folder.

step 4: Test run the compiler and Hello World code.

So far pretty simple, no issues thus far, Rust is installed and working and now I am ready to start writing some code. I think I am going to dig up a few useful scripts in some different languages, like C, bash, python, etc. and attempt to rewrite them in Rust. 

Cheers and Stay tuned!

@hackgineer