tubthumper8

12 ms·

121.
by tubthumper8 3y ago
Would you not consider "null" to be a problem that has been solved? That's the most obvious example to me, it's a problem that used to be extremely prevalent but is now a completely solved problem. I'm not saying th
122.
by tubthumper8 3y ago
line coverage but also branch coverage. Every safe navigation operator used in "defensive" coding, ex. `foo?.bar` is actually another branch that needs to be covered if that's the metric people are using. All of those tests
123.
by tubthumper8 3y ago
Tools and standards aren't really the same thing
124.
by tubthumper8 3y ago
Null reference errors are examples of errors that can be caught before runtime by a static type system. The fact that static type systems like Java don't catch this is evidence that static vs. dynamic is not a binary - some static type
125.
by tubthumper8 3y ago
I'm sure the author is aware of these - many of the code examples are in Rust which has newtypes and automatic deriving of traits (ex. Display which is the equivalent of Haskell Show)
126.
by tubthumper8 3y ago
I agree as well, having worked on both sides (and "full stack"). Not really calling "idiot", but more of the bias that frontend development is easy and not "real" programming whereas I've never personally
127.
by tubthumper8 3y ago
Maps (and lists) are other examples of exponential types. Intuitively this should make sense that these are the same as functions because any pure function could be (theoretically) replaced with a map lookup of pre-computed values. In this
128.
by tubthumper8 3y ago
This author has a habit (in this posts and prior posts) of the content of the paragraphs not connecting the dots for the claims made in the headings. > Rust is (over)hyped Whether it is or isn't, the content of the following paragra