388 karma · joined August 1, 2016
Go play around with Angular 1, or BackboneJS, or try building a working SPA with jQuery, and you'll get a sense of the breakthrough that react represented in 2013.
This is not new tech at all - I was selling Samsung LED TVs with this feature in 2007 or so. Samsung, Sharp, and Sony has little choice but to improve contrast, because their LED sets were right next to Pioneer KURO plasmas that were just absolutely amazing - OLEDs are only catching up their PQ now, 15 years later. First on the scene was the Samsung LN-T5781 - https://www.cnet.com/reviews/samsung-ln-t5781f-review/
Many dentists are criminals willing to drill holes in children's teeth in order fraudulently take your money.
She's now 15. Never had a cavity ever.
> { packageMgr } install { randomPkg }
Developer Andy, author of { randomPkg }, does the same thing. And so on, ad infinitum. You want to sum two numbers? > npm install node-plus
And the source code will be: import { readFile } from 'node:fs/promise'
import { dirname, join } from 'node:path'
import additionChecker from 'add-check'
// redundant useless comments
return function(n1, n2) {
// redundant useless comments
n1 + n2
}At the same time, it's quite clear that it's still not good enough - particularly the algae blooms centering on the mouth of the Maumee river (near Toledo) which turn miles of the lake into something looking and feeling like bright green paint every so often. It doesn't come near my place, but you can imagine how I feel when I picture a hundred square miles of toxic green sludge, juxtaposed with Michigan and Ohio Republican politicians proposing "self-regulation" as the solution...
HTML over the wire is often a useful approach; it doesn't follow that "the future" is there.
No. It doesn't. Nope. It presents the phenomenon as something that's always true - recall the discussion of time traveling and meeting the same dynamic with different particulars in each time and place.
Moreover, "the point of this post" is abundantly clear: the more closely your views adhere to the mainstream, the more blind you'll be to the costs of holding opinions outside the mainstream because you don't encounter those costs. It's a good point and not hard to understand.
First I declare a "foo.src.js" file to hold a module's logic, and then a test file as "foo.js" and have the test file import the logic and then export whatever is to be public. Client code imports the test file and not the source file, so the tests sit in between the logic and the client code, as it were. No more balancing testability against encapsulation.
The second is indirection. I create a mockability decorator. Then have a function (I call it 'mock') which can be used to temporarily redefine any function declared mockable, and then switch back to the real thing when the current test is through. So I get:
const readFile = mockable(fs.promises.readFile)
...
mock(readFile)(async () => 'mock file contents')
Combining these approaches doesn't so much prevent rework on tests when code changes as it makes it much less trouble to implement tests for 98% of cases.Also, some of the CSS and JS hatred is piffle. Publishers absolutely abuse these languages and it gets pretty bad on news websites especially. But I do not find that most or even many of the sites I visit perform badly on my hardware (2016 iPhone SE and a 2017 MBP). They work fine. Moreover, I appreciate nicely designed and competently implemented experiences on the modern web.
I have no interest in trading the modern web - warts and all - for some spartan plaintext utopia.