banned VS manual

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.

Deno banned me a few days ago for notifying them their Web site was displaying and linking to false claims re node https://github.com/denoland/manual/issues/512.

It's about deno, OP is harassing their maintainers: https://github.com/denoland/manual/issues/512

If you're not 'trying' anything then why in both this post and your post in r/javascript are you being so coy about the fact that this is just because you picked yet another stupid fight with an open-source maintainer and they didn't have time for your tedious nonsense.

We’ll use an example from GitHub and create a small JavaScript file, s2_test.js, as follows:

Both have issues. Deno is now 91.2MB! That is 9MB more than Node.js nightly executable. I read somewhere that Deno is ~25MB executable. That is not true https://github.com/denoland/manual/pull/350. I still don't think the maintainers of Deno understand why I file the PR. They should be including "the ~25 megabyte zipped executable" in documentation. I read that, as a minimalist, taking the executable to be ~25Mb. I don;t care what size the .zip file is. A potentially misleading claim.

The PR I filed https://github.com/denoland/manual/pull/350 was closed in favor of https://github.com/denoland/manual/pull/351/commits/2b09b535e8be6463244de34db4c9af53b0372bc6.