3 ms·

That's okay, Rust should never be used for web anyway. I don't like the idea of Rust, C, C++, or Assembly for directly web-facing services. Any non-GC language

by zelly 7y ago

That's okay, Rust should never be used for web anyway. I don't like the idea of Rust, C, C++, or Assembly for directly web-facing services. Any non-GC language should be a non-starter. There are literally (uncountably?) infinite ways you can have memory errors in a native program. The consequences of any of these can be devastating because absolutely anyone can access your endpoint. Notice the asymmetry: One small, unnoticeable error can lead to devastation. Like running across of a field of sparse landmines, eventually you will get destroyed.

jswizzy 7y ago
Depends on how you define web. IOT should be done in low level languages. but yeah I agree that a REST server is better of in something like GO, C#, or JAVA.
- zelly 7y ago
  IOT is generally less of a target. I'm more talking about http endpoints to be consumed by browsers anywhere in the world. That makes the whole world your adversary.
  - zozbot234 7y ago
    > IOT is generally less of a target. Lol. That's the thing about IOT - the 'S' is for security, right?
umanwizard 7y ago
The set of all computer programs is countable, so I don't think there can be uncountably many ways to have memory errors.
- zelly 7y ago
  That seems right. Memory errored programs are a subset of all computer programs. The possible runtime states of a program (expanding every branch/subroutine recursively over all threads) is uncomputable. (Otherwise we would have a solution to the halting problem and be able to correctly free memory at compile time.) I'm not sure if that's the same as being uncountably infinite. It's probably a different concept.
  - umanwizard 7y ago
    Uncomputable is indeed a totally different concept from uncountably infinite.