If anyone says "there are no jobs that require Rust", they've obviously not looked that recently - there are lots that mention it (if not outright ask for it).

I think we're now entering the honeymoon period of "we have to rewrite everything in $shiny_new_language because $some_advantage !!111" that Go had a few years ago.

And, as someone who has to deal with the code-strata of "go everything" 2014-2017, flanked on either side by the much more sensible (but boring) Python - context switching like that is a complete pain in the arse.

Like, I get the "use the right tool for the job", "polyglot" mentality. But in this honeymoon period, the law of instrument prevails and every problem starts to look like a nail.

There has to be a real, tangible advantage to using a completely new language for something. And a marginal performance gain doesn't count.


In the case of Rust, there seem to be some genuinely compelling cases for using it. Just being statically typed isn't enough (Go is also statically typed) - but lack of GC and memory safety enforcement at compile time, plus significant performance improvements over (for example) Python in most use cases might tip the scales.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!