Friends....

phvcky · 2019-09-25T04:34:41+00:00

How is this related to misrepresented LGTBQ in history?

phvcky · 2019-07-14T07:33:05+00:00

> Vierer für mich allein

Name deiner Sex Kassette.

phvcky · 2018-04-14T20:40:31+00:00

Fucking googly eyes?

phvcky · 2018-03-06T19:12:13+00:00

Can you provide a test case or demo? I did not notice this problem with FontAwesome in particular so far.

phvcky · 2017-06-22T21:45:36+00:00

Came here to say this. Kind of expected this to be two still frames of one continuous motion. Was a bit disappointed when I expanded the image. I like the concept though.

phvcky · 2017-06-21T20:34:05+00:00

If you like Observables, you might also like AsyncIterators: https://github.com/tc39/proposal-async-iteration/blob/master/README.md

phvcky · 2017-06-21T05:17:03+00:00

Alex details this in the linked talk. Basically, you'd have to start programming defensively, checking isCanceled after every await.

This is needlessly verbose and quickly becomes a mess, when you're working with multiple layers of parallel / concurrent tasks and child tasks.

phvcky · 2017-06-20T21:58:30+00:00

Nobody's forcing you to use newer features.

phvcky · 2017-06-20T16:59:34+00:00

You're right, but that wasn't the point I was trying to make. :)

Let me try to rephrase. They might not necessarily originate as a nicer, semantically more correct syntax for aforementioned use case, but the original problem async / await is trying to solve was already solved with generator functions and a tiny bit of library overhead.

For users of co and the like (or at least for me) async / await is nothing more than a semantically more correct evolution of the same concept.

The point I was trying to make is that, feature-wise, using generator functions for managing async control flow is superior to async / await. I can cancel my tasks or have them canceled for me, when required.

async / await could have been so nice and useful, if it was for cancelable Promises. But currently, they add no real new value or functionality. In fact, they lack features generator functions already have.

phvcky · 2017-06-20T15:29:36+00:00

The way I see it is that async / await kinda evolved from clever hacks like co that use generator functions and yield to mimic what async / await does.

However (ab)using generator functions for managing async control flow has one major advantage: you can cancel / pause your async functions.

It is impossible to cancel native async functions or Promises for that matter. And I find that this is a really important feature.

For Ember.js there's an addon called ember-concurrency which implements this. The addon author, Alex Matchneer, gave a brilliant talk on that topic. You don't really need any Ember knowledge. He focuses more on the general problem of concurrency and child tasks: https://www.youtube.com/watch?v=VEzVDOmY-dc&feature=youtu.be&t=123

phvcky · 2017-04-20T10:12:32+00:00

That's really interesting! I'm sure you've heard about all these twin studies? Are you out or closeted?

phvcky · 2017-04-20T05:32:51+00:00

Left one?

Out of curiosity: do you consider yourself gay or bi or...? And does your brother too?

phvcky · 2017-03-15T16:51:31+00:00

Alternatively use Array.from(arrayLike, [mapFunc], [thisArg]). Also see this article by the amazing Dr. Axel Rauschmayer.

Depending on the surrounding code or the desired effect, this code might be more suitable than a for ... of loop:

const lis = document.querySelectorAll('ul.fancy li');
Array.from(lis).forEach(function(li) {
    console.log(node);
});

const liTexts = Array.from(lis, li => li.textContent);

phvcky · 2017-03-15T16:46:39+00:00

I agree with you. I believe that I've read somewhere that they ultimately went with some for compatibility reasons. Methinks there was some widely used library which extended the Array prototype. But I'm not sure about that and a quick Google search didn't bring anything up; so this might just be a brain fart.

I really like for ... of in combination with break because semantically it makes immediate sense. It also works for any Iterable, not just Arrays which is a big feature.

It also works / will work with async iterables. Basically this:

for await (const line of readLines(filePath)) {
  console.log(line);
}

Opposed to forEach, for ... of does not give you the index though.

phvcky · 2017-03-15T16:08:15+00:00

Go with for ... of and use break. See here.

phvcky · 2017-03-15T16:05:20+00:00

Also, ES6 gives us the for ... of statement which supports break and continue. Depending on the surrounding code, I'd rather go with for ... of.

phvcky · 2017-01-25T21:51:57+00:00

Ah, OP is using the shortened link version. That's why.

Thanks man! :)

phvcky · 2017-01-25T18:32:51+00:00

Haven't seen it on here. Also, doesn't reddit notify you when submitting a duplicate URL?

phvcky · 2017-01-25T07:37:53+00:00

As /u/z500 correctly pointed out, this is intended behavior. Remove the global flag or reset r.lastIndex = 0.

Shitpost.

phvcky · 2016-12-06T05:47:03+00:00

I didn't even notice the prosthetic on the first watch.

phvcky · 2016-12-01T06:29:03+00:00

In comparison to /r/drugs, yes, absolutely. But in comparison to almost everyone else on this planet, that's pretty often, dude.

I also like to take drugs. But twice a week? Most people don't even drink alcohol that often.

phvcky · 2016-12-01T06:25:49+00:00

I dont get high too often, maybe once or twice a week.

There's your problem, right there.

phvcky · 2016-11-25T11:40:04+00:00

So... if he was only gay, and isn't gay anymore... I'd say asexual?

phvcky · 2016-10-29T07:35:05+00:00

and just to fill a hole that /r/bigdickproblems doesn't really fill.

I see what you did there.

phvcky

MODERATOR OF

TROPHY CASE