w/ const, at least we can say "it's not reassigned, not sure about mutations though". With let, you know neither. Seems uncontroversial 
-
-
why use let then? same problem with params
-
the reason I don't find "it's uncontroversial" persuasive is that two ways to declare variables instead of one isn't free
-
it means I'm thinking about it all the time, and keeping it in mind isn't free. In small methods, the benefits are ~0 for me
-
methinks you've made a `let` believe out of me
Or at the very least, I'm completely without opinion on the matter now. -
yay! I don't really ultimately care what individual projects choose, but I don't want people to believe it's a no-brainer :)
-
it reminds me of coffeescript param shadowing gotchas now
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.