sh_tinh_hair

That's what I'm getting from the safe features emphasis and the fiercely C/C++ competitive slant argued by the evangelists in this thread.

I was looking through the pointer safety portion of the safety brochure: https://doc.rust-lang.org/book/unsafe.html#what-does-safe-me... and wondering how to approach unwrapping an ethernet packet on the wire in the easy unsigned pointer-specific way it can be done in C and came across a pcap implementation in Rust (sample source): https://github.com/ebfull/pcap/blob/master/src/raw.rs Are you serious? Rust is not for me, thanks.

io::stdin().read_line(&mut guess).expect("failed to read line");

My eyes have seen the glory of RUST, it's really javascript, right?

Safety stopped here: "curl https://sh.rustup.rs -sSf | sh" So did my interest.

Agreed. My first choice for a project on *nix is usually in C: it feels like real coding rather than including half the packages/modules from 'pick your glue language here' where the opacity is blinding. But many times I'll stop after working through the first data structures and IPC elements and decide to go higher level in the interest of time and energy (and for other (younger) people being able to maintain it).

I'm highly skeptical of your approach to this problem.

MFA is basically another key|password. If I am not careful with my secret key and password what difference does it make that there are two of them?

No, security is tough. The better security the less useful it is. NIST got this right. Do what you can, don't kill the user and implement security on the aaa side.

As an autodidact I will only note that you can learn at pace (given intelligence and aptitude) only so long as you give it 110%. That extra 10% wears on you. Eventually you will not be able to keep up. The old saying is 'learn from others mistakes'; being self taught leaves you open to not understanding others mistakes and learning a lot from your own. Time++.

Of course they are. Any significantly tasked sysadmin probably uses them on a daily basis and as *nix systems programmer I'll find myself using manpage reference when I jump into something that I haven't used for awhile.

Many situations they are much more convenient and accessible than online or html docs.

Yes,there is ageism but there is also some remnant of meritocracy in IT development and operations (though both the evolution of devops and enterprise agile + ci/cd tool culture will eventually kill that imo).

The only way to remain in the IT game at the age of 45+ is to learn constantly and use your aggregate experience to determine what is good and bad and necessary. When most of the 20+ year IT veterans are in set piece environments they enabled or abetted...technological advent and invention is the enemy.

All the musings on how great a person you really are contra|outside tech are band-aids on reality. If you make your living in technology: be better than the other guy or be useful to them. That's all there is. Otherwise your days are numbered.

We can ramble on about salad days and personal achievement but the younger guys snicker and say 'listen to this fossil' and do their thing. As you would have in their shoes.