Earlier quoted context omitted.
It's still much less dependable compared to something fully supported like Bun.
Fully supported, until they sell it to someone.
I mean, Anthropic now own it
Bun v1.3.9
51–54 of 54 posts
Re: Bun v1.3.9
#52Well, that speeds things up a lot. But I agree with spankalee, it should be a DAG. "ci": "CI=true bun run --parallel check test build docs && bun run --parallel zip zip:firefox"
The problem is that whole thing should have been its own script, which it coulda been with npm-run-all: https://github.com/mysticatea/npm-run-all/blob/HEAD/docs/npm... "scripts":{ "buldrun":"run-p check test docs && run-p zip zip:firefox" } I guess you can put `bun run --parallel` into the script too but it's a bit more verbose.
Why would I want to add an external dependency?
Re: Bun v1.3.9
#53Re: Bun v1.3.9
#54Earlier quoted context omitted.
> What you really want is a way for scripts to describe their dependencies, and then the runner figures out what order to run them in, and cache scripts that don't need to be run because their inputs didn't change. DAG + content-addressing, final binary being the target and everything resolved from there. We could have some beautiful build system that just works and is fast, but seems it never magically appears by it…
Could you clarify what you mean about Nix missing concurrency and parallelism? I often run builds using nix-output-monitor and it definitely looks like things are running in parallel, although I could be mistaken.
I meant as part of the language itself, not just the runtime or for specific parts. Say I'm processing 100 JSON files, it'd be great if I could fire that off wrapped in 'parallel' or whatever, similar to Clojure and others I guess.