There are MANY (so, so many) scams in crypto, but the underlying protocols are just protocols.
Just like there are MANY (so, so many) scams that operate with dollars and in the traditional banking system.
Humans are gonna be humans.
757 karma · joined October 8, 2020
There are MANY (so, so many) scams in crypto, but the underlying protocols are just protocols.
Just like there are MANY (so, so many) scams that operate with dollars and in the traditional banking system.
Humans are gonna be humans.
If they're independently managing their own parts of the DOM, it can work (though still a dev headache imo).
If its a "react app", ie react is managing the entire dom, having two representations of the dom is a v bad idea in that one can make changes that the other is unaware of. Or visa versa.
Not relevant?
Silly proposal for a rule.
There are many carve-outs that will dismiss WARN liability: if severance packages are offered and accepted (with appropriate conditions), the WARN act is irrelevant.
Then better is faster, less annoying, easier to integrate, better UX, etc., even if it sits in the same spot in the workflow.
Take the meeting, it'll be good for your career.
People have very different preferences in the format of content they consume.
> the practice of claiming to have moral standards or beliefs to which one's own behavior does not conform; pretense.
Andreessen has vocally argued (for years) that we should build more housing. Then when the opportunity comes to do it where he lives - he and his wife NIMBY their way out of it.
Pretty simple point to understand.
new airport != new housing is my entire retort to your argument.
Many, many approaches solve organizing your code; React is in the middle of a large pack here.
jQuery lets you imperatively manipulate the dom.
They're different use cases; calling one useful and the other not isn't a very accurate representation.
I guess most the JS is just visual changes, but i wonder if that brings live view out of sync with the dom.