banned VS promises-spec

I don't care about being banned. Wouldn't be the first time https://github.com/guest271314/banned.

Or, more accurately, the "teams" I have joined have tended to get all bent out of shape when their narratives are questioned, and their errors and omissions are exposed on the record - so they have banned me and just closed my issues. E.g., https://github.com/guest271314/banned. Being banned from Node.js organization - after being invited to join the single executable "team" - was ridiculous.

On the other side of that coin, there are some developers who think their code is high and mighty to the degree that if/when you question their specification goal/non-goal narrative, point out ambiguity relevant to the third-party code they promote, or advise them the configuration process for their work is unnecessarily complicated, when JSON could be used they'll ban you. Ask me how I know https://github.com/guest271314/banned.

Like, he's his essay complaining that he can't post racial slurs on Github. https://github.com/guest271314/banned/issues/2

Yes, the Deno folks banned me. So did the Node.js folks, and many others https://github.com/guest271314/banned. Weak. I ain't mad. I vet spurious claims, without exception. I don't care who you think you are. Your claims are not above or below being tested and vetted, exposed.

If you are going to take the time to ban https://github.com/guest271314/banned/issues/7 the messenger that delivers the message you are advertising false claims you must have enough time to review third-party claims in advance.

Well, those are not viable reasons to be kicked off of a team, so they had to lie and say I "attacked" another user. Then lie some more and claim I "harassed" another user. https://github.com/guest271314/banned/issues/6

Most if not all of those bans should be documented here https://github.com/guest271314/banned.

Today, I tried implementing Promises/A+ from scratch to test my coding skill. In the process, I’ve crafted this guide to share my insights and experiences with those who share a similar interest. Without further ado, let’s dive in.

That made me chuckle.

For those not familiar with the promise design controversy:

http://brianmckenna.org/blog/category_theory_promisesaplus

https://github.com/promises-aplus/constructor-spec/issues/24

https://github.com/promises-aplus/promises-spec/issues/94

If you really want to go down the rabbit hole on this one, start here

Advantage 1, nesting, is the most important here, and it's often the most-overlooked advantage. Overlooking nesting is how Promises in Javascript got to be fundamentally broken.

Have you read the infamous GitHub thread where people tried to fix this before it got finalized? It's quite a trip

1.) JS implementation of Promise is not a monad. See this StackOverflow answer or this GitHub discussion for more details

In this article, we will go over how to implement a basic version of a promise during a FAANG interview. The standard for promise implementation is called A+, but it includes a huge amount of details, making it almost impossible to implement all of them during a one-hour coding interview. Therefore, we will focus on implementing a basic variation that should be enough to show the interviewer your solving skills.

Hey, at least you weren't these guys: https://github.com/promises-aplus/promises-spec/issues/94

Total carnage