Just so y’all stay on top of the tech world, I wanted to let you know that this relatively new software language, Rust, is gaining traction around the business and software world and, due to its advancements, will probably be what your computers will be running in the coming decades.
- It’s fast and runs on most hardware/platforms (IoT and embedded, too).
- It’s memory and thread safe (no more dreaded buffer overflow).
- It’s obvious in its structure and construction and has a growing cadre of dedicated task packages.
- And it’s got support for writing WASM – webassembly, which is writing fast binary code to run in a browser (instead of HTML & JavaScript).
This new company I’m working for is training all of its developers in Rust, they’re betting big on a young language. But then, so are many industry players.
I know this is fringe for many of you, but I consider it a good thing to be aware of.
-Mole
Anonymole - apocryphal agitators 
I’ve noticed the headlines. I’m retired, so in some sense I don’t care. But it does attract my attention. I’m kind of a Python man these days, but I have to admit I’m a bit RUST-curious.
LikeLiked by 1 person
The “rand” crate (their packaging name) was downloaded 47 millions times (it’s part of the learn-rust channel). That says to me, at least 20-30 million programmers are using/examining it. (I installed it on three of my machines.) That’s a hella count of coders.
I wrote python for my work with Quantopian and the Coursera “Comp-Phynance” course. I didn’t much care for the whole spaces as syntax, but got used to it after a while. Still miss Pandas & Numpy sometimes.
LikeLike
I’ve been coding since 1977 and I’ve seen so many Great New Things come… and go. I tend to be a late adapter, waiting to see what proves out. (And kind of a Luddite, too.) But C was one of my first heavily used languages, and I took to C++ like a duck to water (brought it’s VTAB ideas back to my C and assembly programming), so Rust really sounds interesting.
OTOH, it’d be quite happy to never write another
for (int i=0; i<whatever; i++) { /* stuff */ }loop again. After 40 years, that’s gotten so old.LikeLiked by 1 person
’77? Wow, got me beat, I didn’t get started until about ’88 and assembler (Motorola 6805). But, still shy of 65 I must toil in the boil, foiled by the coil of a constantly changing programming menagerie.
LikeLike
Yeah, I’m officially an Old Fart. My first languages were Algol, PL/1, Knuth’s MIX, and (of course) BASIC. My first machines were a Data General Nova and an IBM 360. Then came the whole “microcomputer” thing and hey wow!! My only Motorola coding was for the 68HC12. Did a lot of 6502 and Z80 and a huge amount of 808x under MS-DOS and Winders.
Ever done any Smalltalk or LISP? For a True Coder it’s a bit like asking if you’ve ever done shooms or acid… swear to God, seriously mind-expanding.
LikeLiked by 1 person
Yeah, totally a ‘60 child. 😀
LikeLiked by 1 person
What we need is something the processing horsepower (and by extension the user) doesn’t have to wait to run around in circles to execute. I did manage to get audio down to 5 samples latency, at least on the screen and via log, but it choked under load with the processor hardly breathing. Lying’ software mofos. Sure, you can set it there, and we’ll tell you it’s working. What we really need is to eliminate, redefine or integrate drivers. They’re the speed bump. We spent more money there than in hardware. Oh well, old convo.
LikeLike
From what I’ve heard, Rust is also driver capable. It’s a C and C++ replacement, (and shows it with its internal complexity).
LikeLiked by 1 person
Anything new would be grand. Drivers are still asking “can I install MS redistributable C through C++” going back to 2005. There’s even some x86 stuff they wrap to run 64 in case the 64 should fail or become troublesome. Scanners are the absolute worst. Printers right behind them. To the point that a year old HP with cobbled together drivers failed after a Win10 update and HP pretty much gave everybody the finger. My fave comment was “Hell, it was cheaper than the ink to put in it. Get over it.”
Gotta love tech. “Does this work with this?” “No.” “Will it ever?” “No.” Oh….
LikeLiked by 1 person
As long as it doesn’t rust before it gets to us…
LikeLiked by 1 person
Rust never sleeps…
LikeLiked by 1 person
Ooh, that’s a good one. I’ll share that with the trainers.
LikeLiked by 1 person
😁
LikeLike
What do you suggest would be a good starting point to learn about this stuff?
LikeLiked by 1 person
For general knowledge of the industry:
Ars Technica
Engadget
Deeper:
Reddit/r/programming
Hackernews
CodeProject
If you actually want to learn to code, or just some understanding then search youtube for how to learn Javascript — that’s the easiest, most fun language to start with. Khan Academy, and many others on youtube are great ways to learn. And you can write code straight in your browser.
LikeLiked by 1 person
Thank you. I’ll check it out sometime.
LikeLike
Maybe someday an antique Model T Ford will be able to run on Rust.
LikeLiked by 2 people
😂😂👍
LikeLiked by 1 person
Lots of Iron Oxide jokes with this one.
LikeLiked by 1 person