We @FirstMarkCap are excited to lead @aspect_build's seed round. We're thrilled to back @Jakeherringbone and @gregmagolan - two n of 1 technologists who know their domain better than anyone - as they transform how software teams operate.
https://t.co/s8SpEPs7rF
@steeve@aspect_build @aspect_dev @bunjavascript I looked into it yesterday and I think this is pretty easy to add if one of our customers needs it.
That's assuming we continue to use pnpm as the package manager and Bun is okay with that node_modules tree at runtime.
@anton_malinskiy Sure, like if you had an A/B experiment running, but that's just like Git branching - each version of the app would still ship a layer that incrementally updates users from whatever was the "parent" version it's based on.
Why isn't it typically the case that software released as a docker image always has a single layer added to the digest of the image from the prior release? Same concept as database migrations.
@bradzacher Having lots of BUILD files (aka Bazel packages) is a good practice, and yes they should be largely machine-maintained. It's the connectedness of the dependency graph that requires care.
We were very excited to meet up with everyone at Bazel Community Day in SF. Here is a recording of @Jakeherringbone's talk, Migrating away from rules_docker to rules_oci https://t.co/RZ21GvljBY
@bradzacher Most important is to have a directed acyclic dependency graph. Enforce no cycles, and have discipline about layering and adding new dependency edges.
I used to proctor the TypeScript-in-Google3 training class, and built this training course largely on Google's model for wide adoption. It's a mix of lecture and hands-on codelab, and it's all Bazel 6 with bzlmod. Come listen to me for hours on end :)