3 ms·

It probably won't. Rust's unique selling point is in a combination of safety, performance, and minimal runtime (no garbage collection). The most difficult aspec

by pornel 6y ago

It probably won't. Rust's unique selling point is in a combination of safety, performance, and minimal runtime (no garbage collection). The most difficult aspects of Rust are a direct consequence of safe minimal-overhead memory management, and we don't know how to do much better without adding a GC/runtime or compromising safety. Rust has many quality-of-life improvements that could be transplanted to a more relaxed GC-based language, but that won't be Rust any more. Here are some musings how such language could look like: https://without.boats/blog/revisiting-a-smaller-rust/ https://without.boats/blog/revisiting-a-smaller-rust/ (OT: why OP got downvoted so hard? It's a reasonable question to ask)

steveklabnik 6y ago
> (OT: why OP got downvoted so hard? It's a reasonable question to ask) I also am disappointed that the OP got downvoted. Seems bad.
- offtop5 6y ago
  A big part of life is accepting people will disagree with you. Ultimately I did get a solid explanation here. If I want a quick, fast and dirty language , Rust doesn't fit the role. I really do love how C# gives me the ability to hack things together quickly, with still stopping me from doing things which simply won't work. Flutter takes this even a step further with the dynamic keyword( C# has dynamics too , but they aren't as robust ). I can write function calls with dynamics which is great for prototyping. Eventually bad things will happen if you use dynamics in every single call , but it helps me get started. I definitely understand why many software developers see this as a dumbing down of software engineering, which I would attribute the downvotes to.
  - rkangel 6y ago
    There is definitely an aspect of the 'the appropriate tool for the job'. We use Python extensively for 'glue' scripts on my project (build, deployment etc.). It's wonderful and convenient for programs that are 10 to 1000 lines long. The result is clear and predictable and maintainable (particularly when compared to a bash script alternative). I would never write a large production app in Python though (having done it a couple of times). The flexibility becomes unwieldy at that scale and you have to have tests that exercise every corner or you'll have problems hours or days into running.
    - offtop5 6y ago
      That's a very good way to look at it . With Rust do you need less Unit testing ?
      - rkangel 6y ago
        Yes. How much varies though. There are certain classes of test that take time in a dynamic language that you just don't have to write. They're unimportant 'just check I'm actually passing a list to this function and not a class' type tests rather than interesting algorithmic or behavioural tests.
staticassertion 6y ago
> (OT: why OP got downvoted so hard? It's a reasonable question to ask) I find myself upvoting tons of comments in Rust threads where those comments are just asking questions, but are, for whatever reasons, downvoted. Happens on the Rust subreddit too. I don't know wtf it's about.

by pornel 6y ago

steveklabnik 6y ago

> (OT: why OP got downvoted so hard? It's a reasonable question to ask) I also am disappointed that the OP got downvoted. Seems bad.

offtop5 6y ago
A big part of life is accepting people will disagree with you. Ultimately I did get a solid explanation here. If I want a quick, fast and dirty language , Rust doesn't fit the role. I really do love how C# gives me the ability to hack things together quickly, with still stopping me from doing things which simply won't work. Flutter takes this even a step further with the dynamic keyword( C# has dynamics too , but they aren't as robust ). I can write function calls with dynamics which is great for prototyping. Eventually bad things will happen if you use dynamics in every single call , but it helps me get started. I definitely understand why many software developers see this as a dumbing down of software engineering, which I would attribute the downvotes to.
- rkangel 6y ago
  There is definitely an aspect of the 'the appropriate tool for the job'. We use Python extensively for 'glue' scripts on my project (build, deployment etc.). It's wonderful and convenient for programs that are 10 to 1000 lines long. The result is clear and predictable and maintainable (particularly when compared to a bash script alternative). I would never write a large production app in Python though (having done it a couple of times). The flexibility becomes unwieldy at that scale and you have to have tests that exercise every corner or you'll have problems hours or days into running.
  - offtop5 6y ago
    That's a very good way to look at it . With Rust do you need less Unit testing ?
    - rkangel 6y ago
      Yes. How much varies though. There are certain classes of test that take time in a dynamic language that you just don't have to write. They're unimportant 'just check I'm actually passing a list to this function and not a class' type tests rather than interesting algorithmic or behavioural tests.

staticassertion 6y ago

> (OT: why OP got downvoted so hard? It's a reasonable question to ask) I find myself upvoting tons of comments in Rust threads where those comments are just asking questions, but are, for whatever reasons, downvoted. Happens on the Rust subreddit too. I don't know wtf it's about.