732 karma · joined September 25, 2013
https://chomsky.info/19670223/
Spoiler: It's to tell the truth.
Colonial animals are the edge case here. Most would be hesitant to say an ant colony is "an animal", but are happy to refer to a Portuguese Man 'o' War as such, despite also being a colony.
If the not-overriden method isn't commonly called, it's possible for the non-meaningful / raise an exception version to make it to production. Not so if the error happens at typecheck time.
Abstract base classes require everything to extend from a base-level object, and also inherit it's default implementations. This is a nominal (name-based) mechanism.
Protocol (structural-based) subtyping instead only declares what methods something has to have, without requiring it tie itself to either to a concrete parent class and its behaviours.
Edit: since you partially address this, you ask why you'd use structural typing rather than an abstract base class. I'll turn it around and ask why you would use an abstract base class, which requires modifying the children accordingly, when you could instead use a structural type. The usual preference comes down to whether you want to be explicit about implementing it or not, and whether you want to pull in default behaviour.
> "It is no surprise that search engines replicate biases that are not exclusive to the technology, but rather cultural ones. Women of certain nationalities are pigeonholed into sexual and services roles by a male English-speaking culture," she adds.
You could potentially pipe every command output into a separate FIFO file and then run them in the background.
In doing so, we see what lessons there are to take from each other, and gain a better understanding of both fields. For example, the author cites that version control is an innovation that traditional engineering could hugely benefit from.
That said; which engineering field are you basing this on? I thought that generally only lead engineers or architects were responsible in that way.
If such a news organization became mainstream, do you think this would lead to people being more or less informed?
Regardless, I think the "zero editorializing" idea is self-defeating. As others have said; there is near infinite information and finite webpage space and broadcast time.
For those curious if how it works, Paul Irish did a breakdown of it quite a while ago: https://youtu.be/Z2ZXW2HBLPM
TL:DW - Vornoi Diagrams[1] and manual tagging, no machine learning needed.
I imagine this is partly tongue-in-cheek, but I think the real difficulty here is that CSS doesn't differentiate between "user-configured sans-serif font" and "the system fallback sans-serif font". As a result, you can't allow users to override your font choices without disregarding custom fonts entirely.
None. This is a legally protected right.
I tend to agree, but I have difficulty when you scale the problem. No individual person benefits from having their computer rebooted enough to counteract the issues, but might everyone collectively? The utilitarian calculus becomes difficult.
Though parallel solutions: better security testing or a capacity for live updates without a reboot, may be an answer.
Likewise, selecting a column not present in a GROUP BY leads to random values being returned.
Edit: perhaps with some difficulty for the last hop to a virtual device on Electron, to be fair.