Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bun v1.3.9

bun.com

Post reply on HN
Print view View original

31–40 of 54 posts

Re: Bun v1.3.9

#31

Post by spankalee »

pyrolistical wrote: post #19
spankalee wrote: post #17

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…

If only we could make something like that But now we would need each script to independently do their own caching, which isn’t all bad. At least you have more cross runner compatibility and resilience

Wireit really is that. The script declares dependencies and input, Wireit caches based on the direct inputs and dependency outputs.

Re: Bun v1.3.9

#32

Post by spankalee »

embedding-shape wrote: post #21
spankalee wrote: post #17

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…

> 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…

Wireit does both DAG and content-addressing. It figerprints the inputs and outputs of dependencies. And you run scripts externally with plain `npm run` commands. It's really beautiful.

Re: Bun v1.3.9

#33

Post by mattnewton »

dpe82 wrote: post #24
embedding-shape wrote: post #21

Earlier 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…

Google's build system Bazel is what you describe.

I should really give it another look, I usually ended up not adopting it for projects because of the boilerplate and high setup overheard, but those are both things that ai agents can usually be trusted with. Maybe the calculus has changed.

Re: Bun v1.3.9

#34

Post by sestep »

embedding-shape wrote: post #21
spankalee wrote: post #17

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…

> 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.

Re: Bun v1.3.9

#35

Post by aziis98 »

spankalee wrote: post #17

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…

Why didn't I know about this before

Re: Bun v1.3.9

#36

Post by zdragnar »

giorgioz wrote: post #2

Is it more common in English to use there terms Parallel and Sequential or Parallel and Series ? Made a React Library to generate video as code and named two components I was wondering if those were two best terms two use...

Series would be perfectly fine, though out of context it might be a bit confusing because it's also used to describe data on a chart.

Using the singular "Sequence" might also be appropriate for a component name, as the component represents the collection entity, rather than referring directly to the things within the collection itself (which I presume are either a prop or the children of the component).

Re: Bun v1.3.9

#37

Post by dpe82 »

mattnewton wrote: post #33
dpe82 wrote: post #24

Earlier quoted context omitted.

Google's build system Bazel is what you describe.

I should really give it another look, I usually ended up not adopting it for projects because of the boilerplate and high setup overheard, but those are both things that ai agents can usually be trusted with. Maybe the calculus has changed.

Yeah Bazel is a PITA to do yourself. I haven't tried but I'm confident Claude et al. would handle it just fine. By similar logic I recently adopted NixOS for a lot of my servers; Claude is perfectly happy to slog through the pain of Nix configs for me.

Re: Bun v1.3.9

#38

Post by _bittere »

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.

Re: Bun v1.3.9

#39

Post by hxtk »

dpe82 wrote: post #37
mattnewton wrote: post #33

Earlier quoted context omitted.

I should really give it another look, I usually ended up not adopting it for projects because of the boilerplate and high setup overheard, but those are both things that ai agents can usually be trusted with. Maybe the calculus has changed.

Yeah Bazel is a PITA to do yourself. I haven't tried but I'm confident Claude et al. would handle it just fine. By similar logic I recently adopted NixOS for a lot of my servers; Claude is perfectly happy to slog through the pain of Nix configs for me.

I’m not a fan of generative AI for the use case because it’s rote enough to do deterministically, but deterministic code generation is getting better and better.

Gazelle, the BUILD file generator for Go, now supports plugins and several other languages have Gazelle plugins.

I’ve used AI to generate BUILD file generators before, though. I had good luck getting it to write a script that would analyze a Java project with circular dependencies and aggregate the cycle participants into a single target.

Re: Bun v1.3.9

#40

Post by hxtk »

mattnewton wrote: post #33
dpe82 wrote: post #24

Earlier quoted context omitted.

Google's build system Bazel is what you describe.

I should really give it another look, I usually ended up not adopting it for projects because of the boilerplate and high setup overheard, but those are both things that ai agents can usually be trusted with. Maybe the calculus has changed.

It’s gotten easier of late because Bazel modules are nice and Gazelle has started support plugins so it can do build file generation for other languages.

I don’t like generative AI for rote tasks like this, but I’ve had good luck using generative AI to write deterministic code generators that I can commit to a project and reuse.

Post reply on HN