howinteresting

84 ms·

1081.
by howinteresting 6y ago
Have you ever had to deal with tail latency due to memory pressure on web or backend services? Command-line tools are also ideal for Rust because startup performance matters a lot there.
1082.
by howinteresting 6y ago
Thank you for writing this. Real world, qualitative experience reports are vital. My experience using Rust vs C aligns with yours as well.
1083.
by howinteresting 6y ago
If you're writing safe, parallel Rust code, you don't really need to use TSAN. You may hit a deadlock sometimes, but those tend to be easy to figure out in my experience. The people implementing the libraries you use (e.g. Rayon)
1084.
by howinteresting 6y ago
Bothsidesism is unhelpful in technical discussions just as much as in politics. If you have specific critiques please share them. I have a number of specific critiques of Rust, chief being that APIs and implementations are bound too tig
1085.
by howinteresting 6y ago
Rust is a constructive proof that your assertion is simply false. It comes at the cost of some complexity—every Rust type carries thread-safety information with it—but the benefit is that writing correct parallel Rust code becomes very easy
1086.
by howinteresting 6y ago
Some stick to C FFI, some enforce that the Rust compiler version is the same which makes ABI issues irrelevant.
1087.
by howinteresting 6y ago
But restrict is very hard to reason about correctly, and the consequences for making a mistake are potentially catastrophic. There's a very real difference between what's possible in theory and what humans do in practice. I wish H
1088.
by howinteresting 6y ago
Dynamic dispatch (vtables are one way to do it, and so is a function pointer) is incredibly common in C, because there's no language-built-in way to perform monomorphization.
1089.
by howinteresting 6y ago
I'd call mmaping data structures into memory an advanced systems programming trick which can result in a nice performance boost but which also has some severe drawbacks (portability across big/little endian architectures and inter
1090.
by howinteresting 6y ago
Ehhh, inheritance hiearchies are the well-worn grooves of OO, the paradigm encourages them even if it doesn't strictly require them. I don't buy this argument. Typeclasses are a much better way to do polymorphism.
1091.
by howinteresting 6y ago
Explicit variance, especially for types, is just really confusing. Implicit variance has the risk of breaking APIs or overpromising a particular variance without developers realizing. If you have subtyping you need to think about variance.
1092.
by howinteresting 6y ago
One of the fundamental issues with OO subtyping continues to be how variance works. I wish the author spent more time talking about how they envision variance. My other big problem with OO is the spaghetti code that results once you start m
1093.
by howinteresting 6y ago
I wrote a parallel iteration (map-reduce) last week in some CPU-heavy code, took 5 minutes with Rayon. Sped my code up by around 10x on a 12-core machine, example benchmark going from 7 seconds to 700 milliseconds. It's serious busines