Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Some just make it easier than others.
hitko1566120d@M1sf3t Yeah, but simply declaring something won't cause a memory leak, at worst gc will take care of it, and there's a good chance minifier will remove that declaration anyway.
If you're concerned about serious memory leaks, there are tools like TypeScript, eslint, closure compiler, ... to detect potential problems at build time; however, if you're not employing any build steps, there's simply no way to check for potential leaks, which isn't just a JS thing, but a thing with interpreted languages in general.
Lor-inc4680111d@M1sf3t I used to write tutorials as a summer job for a few months. And API docs, update logs, help pages, little info popups, whatever they needed. Being technically literate but completely oblivious to the clusterfuck that was the internal logic of the app, after a thorough explanation of the problem domain I could write text that outsiders would understand.