3 ms·

Agree, better shout out would be Rust. Also referring the complete interview[1] which the TC article quotes, which seems to be favouring Rust. [1]. https://www

by __Joker 11y ago

Agree, better shout out would be Rust. Also referring the complete interview[1] which the TC article quotes, which seems to be favouring Rust. [1]. https://www.codementor.io/rust/tutorial/steve-klabnik-rust-vs-c-go-ocaml-erlang https://www.codementor.io/rust/tutorial/steve-klabnik-rust-v...

steveklabnik 11y ago
Two things: First, I'm on the core team, so I obviously have bias. I try to remain as objective as possible at these things, but still. Second, that interview was from October. Not a lot has changed, really, but it is an eternity in Rust-time.
- akulbe 11y ago
  Question for you, sir. When folks like you and the rest of the team set about making a new programming language, is it ever with the new programmer in mind? Or is your primary purpose to fix a shortcoming in another language, and as such, you're not really thinking of the beginners? The reason I ask is because I went to look at the docs for Rust, and they still seem incomplete. As someone on the outside looking in... I'd have a hard time recommending Rust over C, because the learning path isn't complete yet. C is extremely well-documented. I want to learn Rust, because it's the new hotness, but it seems difficult to do right now. That said, I'm very curious to hear your thoughts on this. Also, if you have advice on how best to learn Rust, I'd love to hear what you have to say on that. My professional experience has been almost entirely with scripting languages, and nothing more low-level than that.
  - steveklabnik 11y ago
    > is it ever with the new programmer in mind? New programming languages are almost never designed with the new programmer in mind. I've spent a _lot_ of time teaching people to program, and they all have really serious hurdles. There are some good projects in this space, but they're a very, very tiny minority. Don't underestimate how hard "Hello world" is, which is actually something that that PDF I linked points out. > they still seem incomplete. Can you elaborate on this, with specifics? It'd be really helpful.
    - akulbe 11y ago
      I created a video with ScreenFlow. https://www.dropbox.com/s/vuax1ocki846llu/rust_example.mp4?dl=0 https://www.dropbox.com/s/vuax1ocki846llu/rust_example.mp4?d... Downloading and installing Rust, no problem. Then I tried doing the "Hello, World!" example. Pretty sure I had it typed right in vim. It didn't work. Then, I typed it in Sublime Text, it still didn't work. Then I thought, I forgot to set +x on the file, and I remember I hadn't set anything on the shebang line in the file, so I went on in the docs. As you can see... I got to the "Learn Rust" page, and it wasn't ready yet.
      - steveklabnik 11y ago
        Thanks for making this! It was _very_ instructive. First of all, I submitted a patch to remove that link to the old intro this morning, so that should go away. Second, the issue was that you compiled the program, which worked just fine, but you never ran it! on http://doc.rust-lang.org/nightly/book/hello-world.html http://doc.rust-lang.org/nightly/book/hello-world.html , the example shows: $ rustc main.rs $ ./main # or main.exe on Windows Hello, world! You did the rustc, but not the ./! As for "Learn Rust", that's one of two paths through the documentation, as the first page of the book mentions. I've been focused on the "Syntax and Semantics" section, which is the other path. "Learn Rust" is coming over the next two weeks.
        akulbe 11y ago
        Now I see that there was an "hw" file, now. I ran it and got the desired results. Should have paid better attention. Hopefully, the instruction was more than, "Wow, this guy is a bonehead." :D I think some mindset changes are needed here, in that I'm used to dealing with interpreted languages, rather than compiled ones.
        steveklabnik 11y ago
        It's all good! Seriously, I've taught tons of people to program, and the beginning is the hardest part. Yeah, the two-step process is different. In the next setup section, when Cargo is introduced, you end up with a 'cargo run' command that does the build and runs your code in one step.

by __Joker 11y ago

steveklabnik 11y ago

Two things: First, I'm on the core team, so I obviously have bias. I try to remain as objective as possible at these things, but still. Second, that interview was from October. Not a lot has changed, really, but it is an eternity in Rust-time.

akulbe 11y ago
Question for you, sir. When folks like you and the rest of the team set about making a new programming language, is it ever with the new programmer in mind? Or is your primary purpose to fix a shortcoming in another language, and as such, you're not really thinking of the beginners? The reason I ask is because I went to look at the docs for Rust, and they still seem incomplete. As someone on the outside looking in... I'd have a hard time recommending Rust over C, because the learning path isn't complete yet. C is extremely well-documented. I want to learn Rust, because it's the new hotness, but it seems difficult to do right now. That said, I'm very curious to hear your thoughts on this. Also, if you have advice on how best to learn Rust, I'd love to hear what you have to say on that. My professional experience has been almost entirely with scripting languages, and nothing more low-level than that.
- steveklabnik 11y ago
  > is it ever with the new programmer in mind? New programming languages are almost never designed with the new programmer in mind. I've spent a _lot_ of time teaching people to program, and they all have really serious hurdles. There are some good projects in this space, but they're a very, very tiny minority. Don't underestimate how hard "Hello world" is, which is actually something that that PDF I linked points out. > they still seem incomplete. Can you elaborate on this, with specifics? It'd be really helpful.
  - akulbe 11y ago
    I created a video with ScreenFlow. https://www.dropbox.com/s/vuax1ocki846llu/rust_example.mp4?dl=0 https://www.dropbox.com/s/vuax1ocki846llu/rust_example.mp4?d... Downloading and installing Rust, no problem. Then I tried doing the "Hello, World!" example. Pretty sure I had it typed right in vim. It didn't work. Then, I typed it in Sublime Text, it still didn't work. Then I thought, I forgot to set +x on the file, and I remember I hadn't set anything on the shebang line in the file, so I went on in the docs. As you can see... I got to the "Learn Rust" page, and it wasn't ready yet.
    - steveklabnik 11y ago
      Thanks for making this! It was _very_ instructive. First of all, I submitted a patch to remove that link to the old intro this morning, so that should go away. Second, the issue was that you compiled the program, which worked just fine, but you never ran it! on http://doc.rust-lang.org/nightly/book/hello-world.html http://doc.rust-lang.org/nightly/book/hello-world.html , the example shows: $ rustc main.rs $ ./main # or main.exe on Windows Hello, world! You did the rustc, but not the ./! As for "Learn Rust", that's one of two paths through the documentation, as the first page of the book mentions. I've been focused on the "Syntax and Semantics" section, which is the other path. "Learn Rust" is coming over the next two weeks.
      - akulbe 11y ago
        Now I see that there was an "hw" file, now. I ran it and got the desired results. Should have paid better attention. Hopefully, the instruction was more than, "Wow, this guy is a bonehead." :D I think some mindset changes are needed here, in that I'm used to dealing with interpreted languages, rather than compiled ones.
        steveklabnik 11y ago
        It's all good! Seriously, I've taught tons of people to program, and the beginning is the hardest part. Yeah, the two-step process is different. In the next setup section, when Cargo is introduced, you end up with a 'cargo run' command that does the build and runs your code in one step.