There are some cases when it's actually simpler or more maintainable or more useful to do the dispatch locally. A language that allows you to both is tougher to learn and can have a higher risk of pitfalls, but also means that a seasoned practitioner can apply the right tool in the right situation.
In terms of the classic 'patterns', it's the difference between standard dispatch and the 'Visitor' pattern. There are cases where you want to specify each case of data structure locally, and others where you want to specify each method of each variant locally. Welcome to the expression problem!
There are cases in Java where you do want a true POJO - just a bag of structured data. This is probably a very strong candidate for using along side that.
This may be somewhat tangential, and if it is too much so, then ignore this and move along.
Isn't the key axiom - preservation of information - a presupposition, and not a formally evidenced law? As best I can tell, it's mostly been assumed as a required premise for a larger axiom - the eternality of matter.
The difference is that the words you cited in the HTML spec are all rooted in English vocabulary and words, without modification. Creating an entirely new set of vocabulary - not mere jargon, but full-on /new words/ with their own declensions. Those are very different beasts.
I believe this is a very rose-tinted slant on what the intent is, especially that worldview has shown itself quite willing and ready to generate oppression along some categories in order to purportedly alleviate oppression along other categories, so long as the tables are being turned.
Not quite sure that was the message of Seveneves; there was quite a bit of rancor and political sniping that escalated to a horrible climax once the mission was already underway. A 'humanity at its best and worst' book, as Stephenson is fond of making.
His B-reel books are usually decent ideas, but you can tell when it's Brandon's voice leaking through the characters instead of the characters themselves. He tends to take a bit more care of his larger, mainline books.
Mostly for understanding any stack traces you might see while running the code, I'd say. Other than that, you can use the bulk of the core language without needing a deep level of Java knowledge. Those bits of Java you may touch can be used as 'incantations' until you learn more.
And yet, NFTs grant no 'rights to use': licensing, copyright, terms of use, or any other legal terms of the sort. At its heart, it's because blockchains are not widely recognized as legally authoritative. They /cannot be/, since there is no guarantee that an image is uniquely identified by one NFT across all blockchains, and therefore a court would be required to pick and choose 'winners' when considering which blockchain rightly determines ownership.
Hypothesis for why there could be an actual /defense/ for the existence and even utility of flat earthers and similar groups: They act as a continual, low-grade chaos assault on scientific institutions, thus encouraging the institutions to maintain resiliency and not stagnate. The more you simply shut these groups down without tackling their actual arguments, the less benefit you'll receive, and the more likely it is to take on the magnitude of a true threat. On the other hand, too much of this would lead to significant wasted effort.
Consensus protocols 101? It seems to boil down to, 'who will subordinate' - it doesn't matter who, so long as someone does. There is a risk of interminably failing to come to consensus on a means for finding consensus, though, an infinite regression that would necessarily need to be broken by one or the other...
I believe what's being stated is that TCP isn't some mathematical inevitability, falling out of some discovered law, but rather a tool that was adopted because it had utility, and was certainly based on more formal findings or hypotheses.
Maybe less useful, but in fiction, Ted Chiang's 'Division by Zero'[1] is a fascinating window into a human response to such a discovery as Gödel's, because it's not /just/ about math. Major breakthroughs in theory often have deep philosophical consequences as well, and the ramifications can readily break whole worldviews for those who actually and acutely understand what they've found.
I take this approach for internal divisions within the same file. For external APIs, you're operating under a completely different set of constraints. As I recall, similar advice was in the original Clean Code: context guides which principles you apply.
Only if said functions are illogically split along non-obvious boundaries. Very frequently, though, I find I can break down concepts to two-three statements in a way that makes it very concise. But also not a hard rule, because there are cases when long-and-drawn-out work as well.
Format migration seems to me to be a key feature - the ability to lift ephemeral discussions into more permanent and deliberate mediums as required. Something like chat -> forum -> wiki, for example. Have set processes in place for determining when something can usefully be pushed upwards. Also encourage a culture of pointing to documentation /first/ to ensure the more permanent documents are well-maintained and robust.
Stack Overflow got close to this, but is still quite a ways off. The chat element is present but very much cut off from the site, and it lost its way over time as its focus changed. It may be worthwhile trying to assemble recommendations for how to select your own tools that give you these benefits, and perhaps to ease migrations between them.
Genuine question: is it necessary to get vaxxed if - all else held the same - the cost is not significantly higher for the antiviral? Wouldn't that cut the risk down so significantly that we can safely say, "Vaccinate if you're at-risk for your own protection, and have negligible risk otherwise"? This changes the entire risk calculation.
One major one that seems to have set its course for the ensuing years is its response to the infamous Charlottesville rally, wherein they attempted to argue that they now considered liberties to have precedence among one another. [1]
Their response to reforms of Title IX to restore the rights of the accused was to intentionally lift up the rights of the accusers over and above the rights of the accused. Their statement regarding it dishonestly claimed that they were balancing the scales, whereas anyone who has examined Title IX can easily see it leaves the accused without their constitutional rights to due process. [2]
In a similar theme, they inserted themselves into the confirmation process of Brett Kavanaugh, taking a clear side on the issue instead of standing for principles of legal representation and initial presumption of innocence. [3]
There are other recent articles on continued churning against their prior positions, but unfortunately they are behind a paywall and I do not yet have access to read them. I may be able to find other sources later. [4]
They are explicitly picking and choosing which speech they believe should be free - and it's not just selecting cases, but actively militating against some speech.
EDIT: Not just speech, but also other basic rights they have stood for, such as legal representation and rights of the accused.
You have to deal with every idiosyncrasy as soon as you begin using external dependencies (and even many standard browser features), because there is no standard convention at any one time, much less over time. There is no fixed paradigm, no common way of doing things, and so the student must first understand how each library frames the world differently, and then work out how to composite those worlds into anything approaching coherence.
I don't think this is a good read. A standard library is very concrete - it's the core of the language in action, and the shape that its code takes will likely be repeated regularly in 3rd party code written in that language. There's nothing academic or abstract about it.
EDIT: As others note, a good chunk of a stdlib may involve system interop that isn't representative, so that tempers my comment with regards to whether that code is idiomatic. But my case still stands regarding concrete vs. abstract.
The gag to this song[1] is a bit crass, but one of the visualization tools in particular has always caught my eye: the hexagonally-arranged note visualization. It seems to capture a number of chord relationships in a very intriguing and intuitive way.
That's a pretty current view of Chinese national policy, actually, so it doesn't come as a surprise at all. From what I recall, Liu takes a party line; I believe he defended their treatment of Uyghurs in recent interviews, for example.
Certainly agreed the water is muddy, and that only the kooky fringe hold to all these, but that fringe is growing. The widely-hailed current sources for this kind of thinking are Ibram X. Kendi and Robin DiAngelo; the latter, specifically, is being hired by companies nationwide to run seminars for employees to train them with this kind of worldview.
It's also pushed strongly in academia, and is quite common to hear about among young progressives as compared to older ones. For concrete examples, look into the Mike Nayna documentary on the Evergreen State College's 'Equity Council'; it's an extreme example, but you can hear the same process happening to lesser degrees elsewhere.