I think my main point is only that you can not always use arrow function, and it should be presented as different kind of function and not replacement... and people should evaluate if its possible.
As you pointed out the arrow function does not have its own scope, prototypes... and that is why you can not use it as constructor or have "new SomeArrowFunction()".
In many cases you can not change type of function without changes to code inside function.
-> for example when using d3 library you need to use function(){}, when you need this to refer to element.
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 my main point is only that you can not always use arrow function, and it should be presented as different kind of function and not replacement... and people should evaluate if its possible.
As you pointed out the arrow function does not have its own scope, prototypes... and that is why you can not use it as constructor or have "new SomeArrowFunction()".
In many cases you can not change type of function without changes to code inside function.
-> for example when using d3 library you need to use function(){}, when you need this to refer to element.