Good article, thanks for the link! In the context of this conversation, I can agree that being exposed to different ways of solving problems will make you better and faster at doing just that.

Common criticisms here would be that these endeavors stifle creativity and show the adoption of modern solutions. That said, I find conducting “code archeology” to figure out the idiomatic way of doing something in an old project very rewarding. Because computer programs exist in people’s mind’s, doing that with the support of original developers or subject matter experts is some of the most effective knowledge transfer I’ve ever witnessed.

My take on a summary: like C/C++, Rust can be relevant in a variety of use-cases and one could conceivably build a long-term career on it, while adjusting to market/technology interests.

Seems like a reasonable prediction?