5 ms·

Too complicated which means when your lead rust dev leaves good luck finding another one.

• dodobirdlord 6y ago
  If you run a Rust shop you need to invest in training and mentoring. It's probably not the right choice for a butts-in-seats feature factory.
  • Polylactic_acid 6y ago
    Seems like its mostly getting used by places doing fairly cutting edge infrastructure or other works where its going to take a fair bit of training to begin with.
• pizza234 6y ago
  If one chooses manual memory managment, the "complicatedness" (as you put it) is not a matter of the language, it's a matter of programming type. As other computer engineering concepts (e.g. referential integrity in database systems), the lack [of implementation] of a feature (e.g. foreign keys) doesn't make a system that needs that concept simple - it just shifts it to the application level.
• est31 6y ago
  As the article says, it's a chicken and egg problem. Small number of jobs, means small number of people who have had those jobs in the past and now have those 6 years of experience with Rust plus minimum 4 years of leadership experience. Means more deciders having the attitude you have instead of "let's go with Rust!".
• mhh__ 6y ago
  It definitely wouldn't be easy as finding your next web developer (or similar) but relatively niche languages (in my experience) tend to have some very clever people on their forums (or similar) so - especially for Rust which is a established language in my mind these days - you shouldn't have that much of a problem finding someone technically capable (HR notwithstanding)
• LoveHateRust 6y ago
  That is besides the lacking of the standard lib the second most important point why our team decided against Rust.