Deno is part of the golden three
flowchart LR
%%subgraph g [golden three]
%%direction LR
j[justfiles]
d[deno]
docker[docker]
j --> d --> docker --> j
%%end
click j "/one-justfile-to-bind-them-all"
click d "/deno-and-tool-ecosystems"
style d fill:#fff,stroke:#999999,stroke-width:2px,color:#000
style d fill:#fff,stroke:#999999,stroke-width:2px,color:#000
click docker "/docker-wasm-web-containers"
Deno: why it’s good
Problem: scripts and utilities written for one repository, and you want to share them with other repositories
- python: it’s painful, and tied to the python ecosystem. You have to publish
etc which is slow
- this applies to most other languages
- specific languages mostly require a lot of specific install/tooling
With deno:
- a single binary
- URL imports, so you don’t ever have to manually install modules/libraries
- URL imports can point to anywhere, e.g. a github repo
- You can publish distinct packages, if you want, but you don’t have to
- The entire npm ecosystem is available. Size matters.
Having used it for a while now, it definitely fits well into my ability to create / build / deploy servers as quickly and simply as possible, allowing me to effectively maintain a larger set of deployable code than before.