3 ms·
What I've seen with the current generation of languages with a lot of compiler-enforced guarantees is that they introduce a lot of needless complexity to the va
by cube2222 4y ago
What I've seen with the current generation of languages with a lot of compiler-enforced guarantees is that they introduce a lot of needless complexity to the vast majority of problems, which are very often simple.
Overdoing monadic constructs is probably the biggest offender here, but Rust (even though I like the design overall) lifetime checking will usually also cost you way more time getting right than just using a GC (if you don't need complicated concurrency).
Main point being, it's not that easy to contribute to libraries written in these.
- kaba0 4y agoI believe that it is a different axis - GC solves the whole concept on a different level (runtime), but where they choose to not take those tradeoffs that complexity has to live somewhere. Monadic constructs are just a convention though, I think it is different.
- mlindner 4y agoGC languages just move the complexity around. I've never done it but I've heard GC tuning is an incredibly difficult problem.
- kaba0 4y agoIt is a trivial problem to solve at runtime, so it definitely decreases complexity. Also, you really don’t have to GC tune almost ever (hell, most runtimes don’t even expose you the knobs)