I think the more you understand of how programming languages work - even "under the hood" - and the further back we go in programming history to see how they solved their problems early on - heck even knowing more about the hardware limitations helps a ton - I think this all contributes greatly in software development and coding.
A small change of perspective I had when looking a little more into the event loop (and unrelated prototype inheritance) was that I did not need to treat my event handler functions as complex actions being performed when that event fires. Instead it's more like you are registering methods within the ongoing event loop which are called when that event type (of many) triggers. So now I'm not afraid of writing smaller and subsequent event handler calls rather than a big one.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the more you understand of how programming languages work - even "under the hood" - and the further back we go in programming history to see how they solved their problems early on - heck even knowing more about the hardware limitations helps a ton - I think this all contributes greatly in software development and coding.
A small change of perspective I had when looking a little more into the event loop (and unrelated prototype inheritance) was that I did not need to treat my event handler functions as complex actions being performed when that event fires. Instead it's more like you are registering methods within the ongoing event loop which are called when that event type (of many) triggers. So now I'm not afraid of writing smaller and subsequent event handler calls rather than a big one.