Named function is not outdated at all. developer.mozilla.org/en-US/docs/W...
Alas, the function keyword is the base in all programming languages.
Using anonymous functions is a personal preference and you lose hoisting and can be harder to debug.
Thank you for taking the time to share your thoughts. You're absolutely right that the choice between arrow functions and traditional named functions is indeed a matter of preference and context. Arrow functions offer concise syntax and lexical scoping, while traditional named functions provide hoisting and possibly clearer stack traces. Both have their merits, and it's wonderful that developers have the flexibility to choose the style that best suits their needs and the project's requirements.
I think a better advise would be to not mix them in the same project/module. Sometimes I see code that has both types of declaration used in similar ways and in the same scope, probably because of different developers acting on the project. It makes the code look ugly and a bit confusing.
If you're going to use traditional named funtions, stick to it, maybe with the exception of callbacks.
Outdated function syntax? 🤨
That is what you must avoid.
Named function is not outdated at all. developer.mozilla.org/en-US/docs/W...
Alas, the function keyword is the base in all programming languages.
Using anonymous functions is a personal preference and you lose hoisting and can be harder to debug.
Thank you for taking the time to share your thoughts. You're absolutely right that the choice between arrow functions and traditional named functions is indeed a matter of preference and context. Arrow functions offer concise syntax and lexical scoping, while traditional named functions provide hoisting and possibly clearer stack traces. Both have their merits, and it's wonderful that developers have the flexibility to choose the style that best suits their needs and the project's requirements.
I think a better advise would be to not mix them in the same project/module. Sometimes I see code that has both types of declaration used in similar ways and in the same scope, probably because of different developers acting on the project. It makes the code look ugly and a bit confusing.
If you're going to use traditional named funtions, stick to it, maybe with the exception of callbacks.
Functions and Arrow Function serve their own purpose. They are not contradicting each other. Example this binding
@brunomonteiro1 @emil
I strongly agree