> Rust ... how computers actually work under the hood.

A curious C++17 programmer, how does Rust teach you much about "how computers work under the hood?" I thought Rust wrapped most of the ugly bits in 'unsafe' and tried to keep programmers from them?

OP is coming from JS.

I'm not a rust guy myself (Fascinated by the memory/thread model but totally disinterested in the rest of the language) but to understand rust (or C++, D, blah blah) you do need to have some concept of a how a computer actually works. The really ugly stuff is hidden but in order to actually do work (thermodynamically rather than REST apis) you need to know what your code actually does (or acts like?)

"Under the hood" is far too complicated to learn from programming as soon as you go below the surface.

Ah, I was hoping for some kind of thing about concurrency or reference sharing. Like look out for dangling pointers or something. My brother if you want to learn how a computer works try writing a multithreaded C++ program, the compiler will not help you much if at all. And you will make mistakes. Everyone does, even google as a whole.

I forgot to mention my background is computer science and I wrote Ruby, Perl and Java for the first 3 years of my career before focusing on JS during the last 5. Thanks for your input, I'm leaning towards Rust or Go; hoping to get some input from the community on what is preferred and what is viable in the market.

> I'm leaning towards Rust or Go; hoping to get some input from the community on what is preferred and what is viable in the market.

If you care about work opportunities - Go, and it's not even close.

Thanks, I'll go through the docs and build a few toy apps over the weekend.

If you're experienced in Rust, what problem spaces are associated with Rust stacks?