Skip to content

Consider ES6+ migration #1556

Open
Open
@Martii

Description

@Martii

The project is currently ES5.1 and it would be helpful to migrate so we can use some more features.

  1. Some of the CONTRIBUTING.md guidelines would need to be changed... especially regarding "hoisting" since the let syntax would change if it was coded hoisted. We are using some let syntax already for speed/memory considerations in key code points.
  2. I am totally not into the arrow operator and it actually makes code more difficult to read and improves laziness. 👎
  3. With the recent issue at Site sluggishness #1548 it may be prudent to dump async at some point since async and await exist. There are a few other technologies too but Promises are also a 👎 from me.
  4. I do like callbacks but when combined with our current site issue and async it seems to be error prone. Perhaps a combination of these to be allowed in CONTRIBUTING.md

While I'm at #1548 I'll do some pro tests to see how well it handles that soon after the holidays.

Open to discussion here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CODESome other Code related issue and it should clearly describe what it is affecting in a comment.DOCPertains inclusively to the Documentation operations.enhancementSomething we do have implemented already but needs improvement upon to the best of knowledge.migrationUse this to indicate that it may apply to an existing or announced migration.needs discussionBlah, blah, blah, wahh, wahh, wahh, etc.team bizThis is similar to a meta discussion.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions