61–66 of 66 posts
Earlier quoted context omitted.
You absolutely can implement an OS or a garbage collector in a GC-enabled language.
Well, sure, if you want completely unpredictable timings on everything. GCs have real problems in certain domains.
Earlier quoted context omitted.
>and upload each of those chunks to S3 in parallel, using no more than N worker threads Do you use a crate like Rayon for this? I'm just starting with Rust, and my current understanding is that without using a library, one can only spawn threads and distribute load by hand (as opposed to automatic scheduling a-la OpenMP). Is this correct?
We're hoping to open source our streaming S3 uploader. Behind the scenes, it uses the `crossbeam` crate (for scoped threads) and BurntSushi's `chan` crate (for bounded, blocking mpmc queues, which is how we get backpressure from a worker pool). One of the cool things about Rust is that it's possible for third-party crates to implement threading primitives. `rayon` is awesome, and it uses `crossbeam_dequeue` internall…
Earlier quoted context omitted.
> Why are developers (since this is an issue that shows up with cargo) running Windows 7 without security patches installed? Especially since the issue only shows up on Windows 7 installs that haven't received security patches since June 2016. Enterprise. It’s only recently I’ve stopped seeing XP boxes around, but Windows 7 is everywhere.
Even in Enterprise environments, having boxes which haven't gotten security patches from 2 years ago is just careless.
Earlier quoted context omitted.
> It doesn't require manual tracking of object ownership. You just have to say when you're passing ownership and when you aren't […] Call it whatever you want, but there are languages where you don't have to "pass ownership" manually for every frigging thing.
And you won't see them being used for systems programming because of their overhead. So without Rust, we'll be stuck with stupid, avoidable security vulnerabilities at the base of all our software, forever. On top of that, Rust's ownership system also prevents data races and none of those other languages are capable of that.
Earlier quoted context omitted.
Iterators in nim are also weird because many of them are not first class types and cannot be assigned to variables. I do not consider that to be a particularly good concept to be honest.
There are two types of iterators in Nim. The inlined variant is more efficient, and you can fairly easily wrap it in the other type: the "closure"" iterator. Why do you not consider it a good concept?
Earlier quoted context omitted.
>Why are developers (since this is an issue that shows up with cargo) running Windows 7 without security patches installed? Especially since the issue only shows up on Windows 7 installs that haven't received security patches since June 2016. The issue shows up on patched machines. The patch does not enable TLS 1.2 by default. You have to add reg keys for it. https://github.com/rust-lang/cargo/issues/5065#issuecommen…
I've never understood why Microsoft adds support for new crypto protocols but turns them off by default.