@confusingbits@sweggles1 Blizz nukes addons in an admission they make the game impossible to tune and you say it’s perfectly playable. They just also happened to fail on their mission to nuke them. Are you a sheep?
@rickyfm Just thinking ahead to how many times I’ll now have to tell junior peers “no “use”is a special hook” or “no you can’t call that other hook conditionally”. It’s just a bad name. I can live with all the bloated additional user land hooks but this one needs to be relabeled.
@rickyfm All comments are about the name yet React team seems committed to it. It’s not really a full hook and it pretty much leaves no room for growth. No one here is looking out for the junior devs that will now inevitably struggle more to understand hooks vs regular functions vs “use”
Bass has kicked it out of bounds on the kickoff three times this year. It is not hard to boot it through the end zone. Why do we do this to ourselves? There is nothing to gain from the extra 3 yard radius you get kicking it to the corner of the field.
Bills went into week three down both starting safeties, both starting corners, both starting DT's and their starting center and left down their backup center, starting RG, RT, 3rd CB, and 5th WR.
@yitzi@KolbySisk@jayphelps There is more than just syntactic sugar to use an anonymous function. Namely the fact that it has no `this`. So no, this is not basically what I’m saying. You can choose to enforce a style or not but the most future proof anonymous function is the explicit form in all aspects.
@yitzi@KolbySisk@jayphelps Bad take. Almost always more annoying long term when you want to add more logic to add the brackets and do the work. Having the curly braces (and the parentheses on the single arg) is always better and more consistent. Favor the solution that works in all scenarios.