Yeah, flatter is better, but "flat" doesn't mean as flat as it used to. Higher-order fns are everywhere. Classes add a level of nesting.
In his new book, @munificentbob argues against implicit variable declaration. But pretty code is flat! Really! Don’t closure irrelvant vars!pic.twitter.com/ILb5EwnsoT
-
-
-
Even w/ classes full of methods with higher-order fn’s, you still don’t really want intentional shadowing in a given lexical scope. No need.
-
Probably not, but how do you *know* if adding an outer variable changes the meaning of an existing inner one?
End of conversation
New conversation -
-
-
100% with Bob on this. "var " is not much clutter to avoid a misspelling becoming a brand new variable. What does that last sentence mean?
-
“Avoiding typos" isn’t a great reason for prog’n syntax. `http://obj.property =` has same misspell concerns. Autocomplete, testing, etc.
-
Yes 'obj.propety =' has the same concerns which is why I'd never want a lang that allowed that. Should be an error at compile- or run-time.
End of conversation
New conversation -
-
-
R has two different assignment operators to overcome this issue: <- binds locally, <<- reuses existing
-
Interesting! I had a hobby language that worked that way too, but I didn't realize it had been done before.
End of conversation
New conversation -
-
-
+1. The best languages IMO let you make important stuff look important, unimportant stuff look small, and irrelevant stuff disappear
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.