Hacker News new | ask | show | jobs
by nosideeffects 4041 days ago
Anytime I see "Not needed" instead of "No" in a feature comparison chart, I am inclined to just stop reading.
2 comments

In this case, as in many others, "not needed" means that one abstraction that is present makes other abstractions unnecessary. For example, if blocking is free, a non-blocking API is not needed, or if actor receives are selective, then message stashing is not needed. Saying "no" would imply that the functionality is missing, when in fact it is present only doesn't require a separate abstraction.
Here are two examples of this in action: http://imgur.com/a/YaQyn#1