I won’t @ them but limiting expressivity in order to limit cognitive load and keep codebases approachable is a totally legitimate move in language design. I’d even say essential. It’s all about balance, and expressivity _does_ have tradeoffs.https://twitter.com/SeanTAllen/status/1036236006872305665 …
-
-
And StackOverflow being a testament to artifacts like Java's new <Foo>Bar<Baz>() and Qux.<Qax>zaz() or Rust's ::<> or Ceylon's class Id<T>() { T id<T>(T val) => val; // which T gets returned? } or C#'s "let's keep parsing and then go back and try to fix the tree" etc.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But I agree, "familiarity" is the only redeeming quality <> has. Every other measurement for <> is considerably worse than the alternatives.
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.