Not so hot take after a few days of tinkering:
Deno is the new Python.
Deno solves Python's problems much better than Python 3.x does.
For my use case (cmdline tools) the advantages are:
- a Deno install is just an exectuable and nothing else (much like Hugo)
- no package manager mess, it's all just "imports", even the Deno stdlib
- builtin WASM+WASI support allows to integrate cmdline tools or libraries written in C/Zig/Rust
- VSCode is a slightly nicer Typescript IDE than Python IDE
@floooh did you happen to look at bun as well? interested in what you think is the main difference https://bun.sh
@kkukshtel I'm aware of the project, but AFAIK it uses an npm-like approach to dependency management (e.g. there's a package.json and "bun install") which makes a lot of sense for a drop-in node.js replacement, and for "proper" backend- or frontend-dev work.
But IMHO the ad-hoc "direct import" approach of Deno is better for command-line tools.
@kkukshtel e.g. in Deno I can simply do:
deno run https://examples.deno.land/hello-world.ts
...and it just works, even if hello-world.ts has complex imports of its own.