Clippy and Friends - Part 8 of Idiomatic Rust in Simple Steps

Поділитися
Вставка
  • Опубліковано 4 жов 2024

КОМЕНТАРІ • 7

  • @Indrini-in6lm
    @Indrini-in6lm 3 місяці тому +1

    Great video! Love the shirt! ❤

    • @FiosQuest
      @FiosQuest  3 місяці тому +1

      Thank you!! I wasn't sure how it would go down as it's quite flowery but I love it too!

  • @selvamp5775
    @selvamp5775 Місяць тому

    Nice, have a question.
    You mentioned there is less job, where(domain, use cases) it gain popularity in future?

    • @FiosQuest
      @FiosQuest  Місяць тому

      Thanks! (TLDR at the bottom)
      It's true that there aren't many Rust jobs right now though adoption this year seems to have picked up quite a bit so fingers crossed this is going to change. @letsgetrusty recently did a great video on growth areas: "Where is Rust being used?" which covers some of this.
      I generally think that companies who build tools for speed and safety should be taking a serious look at Rust right now, particularly things like; vehicle control software, robotics, automation, or any software that causes something to physically move should seriously consider moving to Rust as soon as possible because the tooling makes it much easier to write code confidently than older languages like C or C++. Indeed, that is what we’re seeing happen.
      But actually, there’s few industries that wouldn’t benefit from making the switch. Personally I’m from the web tech space and I used to argue against swapping to Rust (as much as I love it) because speed isn’t everything, what does it matter if Rust can get you an API response in 2ms if TypeScript can do it in 8ms, and that’s the technology most web developers are using?
      However, I’ve actually started to change my mind on this. The internet uses 4-6% of global energy (in 2020, mid pandemic so take it with a pinch of salt), more than the entire aviation industry. If everyone started writing APIs that were 4x faster, this would have a significant impact on the environment. But, environmentalism is a poor motivator, so it’s a difficult argument to make, particularly in smaller companies who aren’t worried about the cost of scale.
      TL;DR: I’m not sure where I see being the biggest growth area for getting a job in Rust in the near future, which is why I can’t recommend learning Rust to get a job right now. In my opinion, it’s better to find an industry that interests you, learn the most common tools for that industry and, once you’re in a position of influence, and can objectively identify problems that can be best solved with Rust, to make that call yourself. To get there though requires understanding the industry and the people within it which is why I often say, the role of a software engineer is not to write code but to solve problems, the technology (even if its Rust) doesn’t actually matter.

    • @selvamp5775
      @selvamp5775 Місяць тому

      Thanks for the kind reply.

    • @selvamp5775
      @selvamp5775 Місяць тому

      Go is good for backend development?
      Or Node/TS?

    • @FiosQuest
      @FiosQuest  Місяць тому

      @@selvamp5775 It perhaps depends on the specific kind of Backend dev. If you want to do what I might call "normal backend webdev" then there's no question JS/TS dominate. If you're looking at lower level things to do with network communication (the sort of things Cloudflare, Netlify, et al do) then the library ecosystem in Go is much richer so a lot of those companies use that.
      I'd describe myself as a fullstack web developer, and TypeScript(/JS/Flow) has been my go to for ~7 years. The big benefit for me is isomorphism which Go and Rust aren't _quite_ there with yet (though Rust is really, really close with things like Dioxus which is what the Fios Quest website was made with).