41–50 of 54 posts
It's fascinating to see a project like Bun, already mature enough to run in production, and yet still improving everyday even if it's a 1.1x speedup. To me, that shows how committed the team is to deliver performance.
I’m genuinely curious because there’s currently 63 open issues of reported segfaults.
https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...
Earlier quoted context omitted.
It lets developers on Windows also build and test your package in parallel mode. If you make your build scripts bash, they're Linux-only.
> if you make your build scripts bash, they’re Linux only Git bash exists on windows and is perfectly usable.
Parallel and sequential, especially at the command level, are really the wrong abstractions for running scripts. If you have multiple packages, each with builds, there's a high chance you have dependencies and multiple packages depending on common ones. 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…
Genuine question out of curiosity. Why do I want parallel and sequential when I can just write a simple bash script to accomplish the same thing? Is there some additional complexity I’m missing?
It lets developers on Windows also build and test your package in parallel mode. If you make your build scripts bash, they're Linux-only.
Seriously, my number one windows shell is WSL. Distant second and third are cmd and powershell which I only use to diagnose WSL issue.
It's fascinating to see a project like Bun, already mature enough to run in production, and yet still improving everyday even if it's a 1.1x speedup. To me, that shows how committed the team is to deliver performance.
Is it mature? I’m genuinely curious because there’s currently 63 open issues of reported segfaults. https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...
Earlier quoted context omitted.
> if you make your build scripts bash, they’re Linux only Git bash exists on windows and is perfectly usable.
It's still much less dependable compared to something fully supported like Bun.
Well, 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"
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.
even though it's at 1.x release, Bun still has so many critical issues (segfault, etc...)