1. 9
  1.  

    1. 1

      Watch at 56:00 for my question and James’ answer on finalization.

      1. 1

        “Oh man…”

        I liked his reply.

      2. 1

        Weird how he would prefer Java to have no if statement and only the ternary (10min10sec). It sounds like the core idea is really that he wants it to be an expression.

        I think Rust showed that you can absolutely get away with it being an expression. So I think he made the wrong call on that one back then. In this talk he makes it sound like he’s being the weird one, but Rust shows that’s not true. Just don’t spell it with question mark and colon! Come on, you’re not making an APL variant.

        Ironic how a designer of one of the worlds most verbose languages likes compact code so much.

        1. 1

          All decisions are made within a context. Later in this talk, he highlighted that making syntax very close to C was essential, even if it resulted in a subpar experience at times.