Just curious, are you using => functions exclusively or still sticking to traditional function syntax? No judgement!

@JavaScript I sometimes like old ones for hoisting or inline util functions

@JavaScript => almost all the time!

@JavaScript .then() .then() And .then()

@JavaScript Arrow functions since it’s neater especially if written on one line. 👨🏼‍💻

@JavaScript I use both, but prefer =>

@JavaScript Lambdas are faster but less readable. It depends!

@JavaScript I use normal function syntax but for array methods and stuff i use arrow syntax as it looks a lot cleaner

@JavaScript arrow functions with good naming convention all day

@JavaScript I now default to arrow functions instinctively but can’t say I “prefer” one over the other.

@JavaScript I use both lol

@JavaScript For callbacks, arrow function. For function declaration, normal function

@JavaScript Starting to use them for any instance in which I don’t need to worry about what ‘this’ is bound to.

@JavaScript It takes me 5x more time to understand the syntax everytime I try to use that. Traditional function() is longer but more comfortable

@JavaScript I dnt have a preference yet. I’m still fighting for my life learning the material. 🤣

@JavaScript I learnt the modern before i knew there was a traditional, lol

@JavaScript Using both! 💪

@JavaScript I default to the "function" keyword for most things. Hoisting is helpful for module-level functions. For inline callback functions/closures, I like that the function keyword allows me to give the function a descriptive name.

@JavaScript Depends on the circumstance. Anonymous functions use =>. If I want my reader to better understand the purpose of a function, I'll use traditional.

@JavaScript Both. There is a reason for using each.

@JavaScript Does using one over the other make any difference to the code?

@JavaScript Both, because it's required - they aren't equal. One such example of where arrow functions catch me out, is in event listener callbacks. Arrow functions don't bind 'this', which can lead to debugging hell when I forget 😁

@JavaScript Arrow functions because I like that functions are just values.

@JavaScript Though I’m into Functional Programming, I still prefer function(){} 😅

@JavaScript Mostly fat arrow (=>) functions. The only time I use traditional functions(function()) is when I need the scope of 'this' to be the function itself, instead of global scope. I guess that's a major difference between the two approaches that really sets apart their use cases.

@JavaScript When passing a #JavaScript function as an argument, its better to use the phatarrow syntax. Inside of a class, or global scope, its better for writing an "easy 2 use & understand lexical scope", and for printing better stacktraces to use the C-Style functions.

@JavaScript Arrows!! And any copy and pasted code from stackoverflow is getting arrow'd as well

@JavaScript Arrow functions and function declarations have slightly different behavior, so it depends on the use case.

@JavaScript Arrow functions all the way Becuse on this way i have no problem with this anymore😅

@JavaScript `function` keyword for everything but one-liners and inline functions (e.g callbacks on array methods, etc). The function keyword is plenty terse and the hoisting behavior is useful. I'm also positive this is the only correct opinion to have 😁.

@JavaScript Probably quite unpopular but I prefer the traditional function syntax: function doSomething (x, y) { ... } I use arrow functions mostly for one liners and some trivial callbacks.

@JavaScript Hey Js, It'd look cool if you add <= for return statements, coz => is used for functions. 🤌

@JavaScript arrow function all the time ❤️. Even in our product FansZila ( fanszila.com )

@JavaScript For tiny bits of code where the absence of 𝚝𝚑𝚒𝚜 isn't an inconvenience, sure. As a wholesale replacement for using the 𝚏𝚞𝚗𝚌𝚝𝚒𝚘𝚗 keyword, no I am not interested in trying to look cool by making everything a variable assignment.

@JavaScript You can’t use arrow functions with hoisting so in those cases I use old school functions

@JavaScript Depends on the scope required of that function 😋