Message from JavaScript discussions

April 2017

— And is not a native app

— 

The fact of the matter is Chromium/Chrome is a tight ship and keeps getting tighter, and it is highly suspect to me to immediately blame it outright instead of the code running on it. My best guess for what was happening to the poor dude was buggy code made by Slack etc... more specifically an infinite loop, something known to eat RAM and CPU at the same time and be semi-hidden depending on how much abuse your machine can take

— Another very probable cause is bad GC management

— Yes, JS is a GC language, but you should code for it just the same

— If you don't, the GC is not smart enough to compensate

— So that is all the reasons I was talking about devtools, and really investigating to the heart of the problem before spouting off about how terrible a technology is

Message permanent page

— Separate from that, electron is still cancer

— I think it has it's uses and routinely gets abused, but I would not take it to that extreme

— This group feels like getting a AA meeting with alcohol

— Next up on our agenda tonight is window and how not to dump everything in it

— Found this in a high end corporate website's window object

— Had other names in there too, some NSFW