108 karma · joined January 24, 2016
class Foo {
bar = () => {
console.log(this);
}
}
This basically puts `this.bar = () => console.log(this)` in the constructor, and since it's an arrow function it captures the correct context.I thought that was the article people were discussing and couldn't figure out why no one else was mentioning having trouble following the flow of the language:
But the utility, the summary configurations of suggestions that speed on these programs,
exist in fully separate condo and are merely (though the undeniable truth that here’s
that that you can maybe be additionally bear in mind is immensely worthy) translated
into the digital or paper medium.
I guess it's a previous version which hadn't gone through proofreading? Pretty confused here. Yes, technically you could plausibly run it wired until
its charged enough but now there's the extra
inconvenience of managing a cable.
You have to manage the same cable when charging it from underneath, only now it's unusable until it's done charging...I can see defending it on aesthetic grounds, and maybe even from a condescending place of not wanting the user to feel what it's like to use it tethered (I like Apple but they do this "we know what you want better than you" dance a little too much). But the point I quoted is pretty silly.
But at the moment when you drop a pebble into a pond, there are definitely parts of the surface which are moving and parts which are not, and the influence of the energy you introduced with the pebble can clearly be seen to spread outward over time.
Granted this doesn't map directly onto electromagnetic waves because the mechanisms involved in wave propagation are different.
A slash or a dot in the middle would be nice.
See this is why we need groundbreaking advancements in deep learning and we need them now.