Should your team adopt the Rust programming language?

แชร์
ฝัง
  • เผยแพร่เมื่อ 24 ธ.ค. 2024

ความคิดเห็น • 27

  • @GoogleOpenSource
    @GoogleOpenSource  2 ปีที่แล้ว +2

    Missed our live event? Google Open Source Live is a monthly event where open source experts provide discussions around their areas of expertise, answer questions in a Q&A forum, and so much more! Check out and register for our upcoming events with this link → goo.gle/GOSLNextEvent. See you at the next Google Open Source Live event!

  • @Andrew-jh2bn
    @Andrew-jh2bn 2 ปีที่แล้ว +9

    Typo in the title?

  • @richardyao9012
    @richardyao9012 2 ปีที่แล้ว +1

    Why do you not replace Kotlin in Android with Rust?

    • @gerardm.5047
      @gerardm.5047 2 ปีที่แล้ว +1

      I’ve only spent a few months with all three but Rust is considerable harder than Java and Kotlin

    • @jcfawerd
      @jcfawerd 2 ปีที่แล้ว +4

      I would prefer official support of writing android apps with rust. It would be much faster than using VM and properly use less memory

  • @kelvinpraises
    @kelvinpraises 2 ปีที่แล้ว +14

    Everywhere I go, I'm being convinced to learn Rust. I've got a course on it, I just have to make up my mind.

    • @jesusgarciamanday9048
      @jesusgarciamanday9048 2 ปีที่แล้ว +1

      Hey Kelvin, which curse have you got? I would be very interested to start a new one. Thanks!

    • @rallokkcaz
      @rallokkcaz 2 ปีที่แล้ว +1

      You probably won't learn Rust very well form a course. The compiler will teach you, and punish you. Just try to write code and get your ass beat.

    • @imnikhil3831
      @imnikhil3831 2 ปีที่แล้ว +1

      Golang is far better than Rust

    • @gerardm.5047
      @gerardm.5047 2 ปีที่แล้ว +1

      @@imnikhil3831 golang is much easier but only has one domain of use it seems while Rust has three or four

    • @gerardm.5047
      @gerardm.5047 2 ปีที่แล้ว

      But Rust is probably three times harder haha

  • @saaddahmani1870
    @saaddahmani1870 2 ปีที่แล้ว

    Good, thanks.

  • @erlangparasu7524
    @erlangparasu7524 2 ปีที่แล้ว +1

    👍 #google #rust #rustlang

  • @kchaitanya39
    @kchaitanya39 2 ปีที่แล้ว +15

    You guys invented carbon right? Why so much love on rust suddenly

    • @rustdev1
      @rustdev1 2 ปีที่แล้ว +15

      As far as I know, the reason carbon was created is to be able to use C++ large codebases which are difficult to rewrite in Rust.

    • @merlin6962
      @merlin6962 2 ปีที่แล้ว +23

      The carbon site even mentions that you should use Rust if you can iirc

    • @merlin6962
      @merlin6962 2 ปีที่แล้ว +13

      "Existing modern languages already provide an excellent developer experience: Go, Swift, Kotlin, Rust, and many more. Developers that can use one of these existing languages should. Unfortunately, the designs of these languages present significant barriers to adoption and migration from C++. These barriers range from changes in the idiomatic design of software to performance overhead."

    • @AlexanderHyll
      @AlexanderHyll 2 ปีที่แล้ว +4

      @@rustdev1 they’ve been adopting Rust for longer than work has officially been done on Carbon if I’m not misstaken. And the adoption has not been very sudden.
      There is also a difference in the uses and approaches of the designs of languages. Carbon is a successor of C++ and Rust is not. The upside is a language with full backward compatibility but getting rid of the built up technical debt of C++. That is awesome, but it also doesnt include everything Rust has. Carbon is aimed at being safer, but not inherently mem-safe as a paradigm. So its kinda apples to oranges. Perhaps both have a place, perhaps not. Carbon is also only being experimentally developed currently, whereas Rust is getting pretty mature.

    • @fantasypvp
      @fantasypvp 2 ปีที่แล้ว +1

      @@merlin6962 in pretty sure that kotlin was never intended as a replacement for c++ but instead for java as it runs on the JVM and is compatible with existing java code
      Similarly for swift (swift is the suggested language used to build apps on MacOS *correct me if I'm wrong*) which was intended as a replacement for objective-C

  • @chrisdaman4179
    @chrisdaman4179 2 ปีที่แล้ว +3

    No they shouldn't.