Recently Steve Klabnik called out to summarize why Rust is actually awesome to work with. I do love Rust and plan to use it next year for many many things, so I want to share my thoughts about the language, where it excels at right now and what is needed for critical breakthrough success.

Great language features right now

The more I use Rust, the more I recognize things that are flat-out awesome in Rust. But some things might be of special interest for readers who are not yet using Rust:

  • It’s a compiled language with a great type system. After having worked with Ruby, PHP, Javascript and a few other scripting languages, it’s liberating when you can refactor bigger codebases without the fear to break stuff. You also don’t have to write these enormous test suites to cover basic stuff, which is a huge productivity boost in the long run.

Usecases right now

In my mind, there are three major usecases for Rust right now, where it can really excel. Yes, there is Mozilla, building a next-gen browser with it, but I have zero experience with this or any motivation to do the same thing. These usecases are primary what I think of and use Rust for:

  • Libraries. I tend to rewrite a bunch of personal libraries for every new programming language I learn. Maintaining this stuff for languages I no longer use is a burden, really (aka: I don’t find the motivation, ever). But once I’ve written libraries/algorithms in Rust, I can use it from all other languages/projects as a native extension. Being written in Rust, a library is highly performant, reasonably correct and doesn’t have nasty exploits like C/C++ (mortals don’t seem to be good at writing exploit-free C++, see decades of bugfixing unix-y stuff). So write it once, and then call it from Node.js or Elixir or whatever you use currently.

Required Features for new Usecases

Rust currently ignores the needs of the majority of all developers I’d say.

  • Do you know what enterprise-y developers do all day? Shuffling data from SOAP-Services around, maybe analyzing them, maybe creating reports for Excelsheets for managers. The thing is, Rust could use WSDL definitions for the SOAP-Services and generate safe abstractions for it (using the great type system) to use with ease. If using Rust makes dealing with all these SOAP stuff dirt-easy and painless, corporate developers will (silently) start to use it. Database needs are already covered, Excel can be dealt with, and CSV is easy.

This is my personal wishlist for Rust in 2017, obviously. I’d love to read opinions from other rustaceans out there!

Describing myself in buzzwords: #FullstackDeveloper. #DataScientist. #GrowthHacker. #ProductDesigner. #Meteor monkey. #Elixir Alchemist. #News addicted. #Zen.

Describing myself in buzzwords: #FullstackDeveloper. #DataScientist. #GrowthHacker. #ProductDesigner. #Meteor monkey. #Elixir Alchemist. #News addicted. #Zen.