Coding lessons 101, it shouldn't be that fucking hard to understand what a pointer is but that's where we currently stand

@CatSharp needs to know

I'm stuck at javascript having a memory leak...

"what a pointer is" <- what does this have to do with the comment? I mean, even C has function pointers, but using one doesn't magically construct a new function.

Pointers are easy to understand. References are made more complicated than they really should be by dumb language designs such as Java or JavaScript.

Man, we should start passing functions as values, so that I can just write the same function again to unregister a bind or check for correct function equality. Who's with me?

There shouldn't be an operation that means both referential equality and value equality depending on context in high level languages. Ref and value equality are never interchangeable. These should be different operations, and they should both fail if they're not applicable to the types they're given.

the only reason we even call identity "equality" is that on the lowest levels it's implemented as an equality comparison, but it has about as much to do with equality as a concept as if has with jump or return has with pop.

Oh, wow! You mean I have to have the appropriate value attached to my dingaling? 🤣

To fuel your hating even more, I remind you the existence of symbols. They are also a primitive.

Im pretty sure that if that was the reference i was given as to what a pointer is... id need some serious extra help-- and ive known what a pointer is for >20yrs.

@atheist you place some event listener, forget to remove it when the component is gone, there's your memory leak.

@IHateForALiving also the reason why we have so many base classes on js frameworks. Even the Custom Elements standard has a default assumptions