One of the great advantages of Deno is the absence of a package manager, this section is practically monopolized by two corporations (MS with npm and FB with yarn); Deno has shown itself to be a more independent ecosystem with respect to its counterpart, Node. Do you think that this decision taken by the core team was the right one? would you have preferred it to become a foundation instead of a company? Will it become a more independent solution or will it end up like Node with OpenJS? being a front entity for a few big techs that lobby the ecosystem?

  • dinomugOPM
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 years ago

    Basically it’s an improved Node.js (created by the same developer of node).

    Main features/differences:

    • Build with Rust.
    • Secure by default. No file, network, or environment access, unless explicitly enabled.
    • Supports TypeScript out of the box.
    • Ships only a single executable file.
    • Has built-in utilities like a dependency inspector (deno info) and a code formatter (deno fmt).
    • Has a set of reviewed (audited) standard modules that are guaranteed to work with Deno: deno.land/std.
    • There is no concept of a package manager as external modules are imported directly into local modules.