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 Arrow functions since it’s neater especially if written on one line. 👨🏼💻
@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 because I like that functions are just values.
@JavaScript Traditional function syntax user here... 🥹
@JavaScript utility functions are mostly traditional for me... but member functions are always arrow syntax as I don't want the burden of binding scope.
@JavaScript `function` tells the reader that the line contains a function declaration, var/let/const doesn't until you keep reading. I only use arrows if I need a one-liner or to bind `this` to its lexical context, otherwise, you're adding noise to the code IMO.
@JavaScript I use a mix of both. When its a short one I will use an arrow function to keep it compact and cleaner when I have more going on I opt for a traditionally defining function
@JavaScript I'm learning JavaScript, so I mainly use traditional functions as of now. Also, I couldn't make my program work when using arrow functions in one part of it. It was related to removeEventListener...
@JavaScript Each has its purpose and so I will use the one that fits my use case the best.
For all the JS veterans and ninjas out there, please help me: - What was your biggest obstacle when you first started with JavaScript? - If you were designing a tutorial for absolute beginners in 2025, what would be your essential first chapter? - Looking back, what resources or explanations do you wish had been available when you started? - In your experience, what crucial element is consistently missing from existing JavaScript tutorials and books? Your insights could be invaluable in helping shape the next generation of JavaScript developers. Even a brief reflection could make a huge difference! Thank you very much! #JavaScriptCommunity #JavaScript #WebDevelopment #CodingEducation #TechLearning #WebDev #Programming #CodeNewbie #100DaysOfCode #Developer #SoftwareEngineering #FrontEnd #FullStack #JSdeveloper #TechEducation #CodeLearning #LearnToCode #DeveloperCommunity #JavaScriptDeveloper #WebDevCommunity #TechTutorials #CodingTips #ProgrammingEducation #ReactJS #NodeJS
@JavaScript react: functions on components, arrows on regular functions
@JavaScript Depends on how/where I need to access `this`… and what `this` needs to reference.
@JavaScript i do => whenever i try to keep context
@JavaScript When you know what you are typing: Arrow Functions When you are thinking and staring at the screen: Function Syntax
@JavaScript It depends on the situation. I use the regular function keyword when I can But when I want to make a simple function that returns a value or making an anonymous function I use arrows =>
@JavaScript I use => unless I need function this or argument. Might be irrational I just assume => doesn’t add a context and therefore is lighter
@JavaScript I prefer arrow functions more. There is not only a difference in syntax but it is a lot more, you can check it out here. freecodecamp.org/news/the-diffe… @JavaScript #javascript #LearnInPublic
@JavaScript Use arrow functions for anonymous callbacks (e.g. filter, map, forEach) and functions generally elsewhere. Sometimes use function expressions when adding functionality to an object.
@JavaScript I'm all about that arrow function life! 🚀 They're just so clean and concise, you know?
@JavaScript Both, I am a still getting a foothold with programming in general,and learning how to use both interchangeably is a cool milestone
@JavaScript I use the traditional way only when I want to use this