EventEmitter Standards Go Deeper

EventEmitter3 - Because there's also a number 2. And we're faster. eventemitter4 EventEmitter4 1. Synopsis 2. Installation 3. Browser support 9.6. Why not EventEmitter3 EventEmitter3 does not have an onAny() function. The module is not implemented using any form of set algebra either. Therefore, I did not particularly feel like extending it. eventemitter5 EventEmitter5 Because there is an EventEmitter, EventEmitter2, EventEmitter3 and EventEmitter4. Let's end the insanity and work together to fix the existing EventEmitter projects. Keywords eventemitter6 EventEmitter6 Because there is an EventEmitter, EventEmitter2, EventEmitter3, EventEmitter4, and EventEmitter5. That's a hell of them all, and because there is no setMaxEventEmitterPkg, let's make EventEmitter great again! And we will make listeners pay for it! Dependencies (5) EventEmitter eventemitter2 eventemitter3 eventemitter4 eventemitter5 🤦 Eventemitter 7 We need to go deeper

A stack of increasingly numbered EventEmitter package pages appears one after another, each introducing another competing implementation. The joke parodies the proliferation of incompatible standards and libraries, escalating from EventEmitter3 to EventEmitter7. It is used as a sarcastic reaction when an attempt to create one universal solution only produces yet another standard.

• @dev_meme / 3515 2021-08-07