Whilst I appreciate the changes to "this", I always find the syntax of arrow functions to be damn ugly and confusing. It just never feels verbose enough for a new javascript developer to know what is going on.
Haha, I'm the exact opposite, I love them! But they're like any tool, I think they have a purpose and a place depending on your approach. For me, they offer a great way to introduce more readable code, especially in smaller cases.
For example:
// this, is more readable, or certainly neaterconstnewArr=oldArr.map(item=>item.thing);// than this,constnewArr=oldArr.map(function(item){returnitem.thing;});
BUT...
I do agree wholeheartedly with you that terseness != readable all the time and yes, I would imagine less experienced devs (well, all devs really) could get lost with an abuse of over simplified and terse arrow functions littered all over the shop.
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.
Good article, thanks!
Whilst I appreciate the changes to "this", I always find the syntax of arrow functions to be damn ugly and confusing. It just never feels verbose enough for a new javascript developer to know what is going on.
Haha, I'm the exact opposite, I love them! But they're like any tool, I think they have a purpose and a place depending on your approach. For me, they offer a great way to introduce more readable code, especially in smaller cases.
For example:
BUT...
I do agree wholeheartedly with you that terseness != readable all the time and yes, I would imagine less experienced devs (well, all devs really) could get lost with an abuse of over simplified and terse arrow functions littered all over the shop.