This is just the standard precision/ recall tradeoff with recall being prioritised at the extreme (which is usually the wrong way to go for legal field).
A standard situation of 1% positive rate and even if your diagnosis method having 90% accuracy (for both sensitivity and specificity), more than 90% of the positive detection would be false positive.
> A few hours later another programmer came up with the prototype of a much faster terminal renderer, proving that for an experienced programmer a terminal renderer is a fun weekend project and far away from being a multiyear long research undertaking.
I read through the Github issue and can't find the prototype mentioned here. Can anyone link the PR/code if they know it please?
> True, that is a good selling point -- in theory. Indeed BEAM's process isolation is better than the JVM's on paper. In practice, so many Erlang systems have so much C in them (because Erlang isn't fast enough for the data plane), that they can still bring down the entire VM (not as if there aren't other ways of doing that even without native code), or they interfere with one another in other ways because of BEAM's poor support for shared concurrent data stuctures.
From my limited knowledge of Erlang, both of your points seem to be off the mark:
- Erlang systems have a lot of C code, but the purposes of BEAM was to manage those individual pieces and have those C component isolated such as they can crashed without causing system-wide issue.
- Actor model does not require programmer concurrent data structure to be effective. Actually that's the whole point of it...
A standard situation of 1% positive rate and even if your diagnosis method having 90% accuracy (for both sensitivity and specificity), more than 90% of the positive detection would be false positive.