yeah, the same thing happened in MULTIPLE renditions, especially in JavaScript. I lost track of how many coders had something like that in their preloaded but didn't have a clue it was there when they published, lol
The fact that the definition of class _() stayed in that forked code is quite funny.
It's also showing how hard it can be to maintain a good architecture even for simple code, because when you are not the one that made the code, you don't know the location of every piece of code, and you easily forget to remove some.
yeah, the same thing happened in MULTIPLE renditions, especially in JavaScript. I lost track of how many coders had something like that in their preloaded but didn't have a clue it was there when they published, lol
haha, also the possibly misleading intentional misspelling of the class
The fact that the definition of
class _()stayed in that forked code is quite funny.It's also showing how hard it can be to maintain a good architecture even for simple code, because when you are not the one that made the code, you don't know the location of every piece of code, and you easily forget to remove some.
I really stared at that one for a minute before searching for the additionnal preloaded code !
So funny solution...
holly molly, would you be kind to explaim how this works?? thx