Skip to content
This repository was archived by the owner on Jan 10, 2020. It is now read-only.
This repository was archived by the owner on Jan 10, 2020. It is now read-only.

Survey for strong(er) typing #61

Open

Description

@aaronbartell

In this Node.js User Feedback meeting we discussed doing a survey to ask the community whether they're interested in having a strong(er) data typing presence (i.e. Typescript) be built into Node.js.

This issue is to kick off the conversation amongst the Node.js User Feedback group.

It was mentioned by @mhdawson that a 1hr meeting could most likely give us enough time to flesh out the survey questions. I agree.

Activity

  1. styfle commented on May 22, 2018

    @styfle
    SponsorMember

    I really like TypeScript but I'm not sure how to integrate it properly besides using something like node-ts.

    Is that what you are suggesting?

  2. aaronbartell commented on May 22, 2018

    @aaronbartell
    ContributorAuthor

    Is that what you are suggesting?

    @styfle,

    Good question.

    Part of the original conversation included pondering a survey option that asked whether we should promote this request all the way up to the Javascript specification so Node.js would inherently get it in the future.

    Also in the original conversation it was mentioned that proposing types for Javascript has already happened and declined. I am not well versed in where to look for that conversation. I first went to Mozilla's ECMAScript reference page and that gave me Git repos for both ECMA-262 and ECMA-402.

    Anyone know where else to look for the conversation where ECMAScript/Javascript types were declined?

  3. zuohuadong commented on Nov 29, 2018

    @zuohuadong

    As a user, I would like to express my own views:
    Our main motivation for using node.js comes from Nest.js, which is very friendly to typescript support.

    The biggest obstacle to Typescript is V8, and I hope node.js can learn something from Dart.

  4. mhdawson commented on Nov 29, 2018

    @mhdawson
    Member

    @zuohuadong can you add more details on how V8 is the obstacle?

  5. zuohuadong commented on Nov 29, 2018

    @zuohuadong

    @mhdawson

    V8 is not Typecript's runtime.

    1. Because the typescript needs to be compiled into JavaScript, it cannot achieve true AOP, and even typescript frameworks such as nest.js do not achieve true dependency injection (Ioc)。
    2. We were unable to compile the typescript into binary . The Flutter eventually chose Dart.

    At this stage, typescript can learn from Dart. If support for typescript is good enough, there will be a framework like spring.

  6. mhdawson commented on Nov 30, 2018

    @mhdawson
    Member

    @zuohuadong thanks for the additional info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions