rockerest’s avatarrockerest’s Twitter Archive—№ 19,129

  1. …in reply to @_atjn
    _atjn "as comments" uses a definition of comments that's only useful to an AST parser. It's a misleading definition for common consumption, and this is brought up in multiple issues on the proposal. I suppose I agree that it may not help foster constructive criticism, but I think the
    1. …in reply to @rockerest
      _atjn seismic shift here (language is dynamic, but can appear to be typed, but those types are ignored by the parser. Reserves huge areas of source code forever as ignored chunks only for type systems.) is worth strong rebuttal and clarity.
      1. …in reply to @rockerest
        _atjn This proposal suggests that future learners of the language have to note - forever - that while the language is dynamic, through and through, you may see some stuff clogging up the code that implies it is not, but is ignored by the engine (for now).
        1. …in reply to @rockerest
          _atjn This level of change should not be addressed lightly, and the misleading nature of the title is part of that. There's a tiny crowd of people who understand "comments" the way it's defined here, and it should be much more clear that it's going to be changing the way
          1. …in reply to @rockerest
            _atjn JavaScript is parsed and read forever.