HN user

DavyJone

40 karma
Posts2
Comments26
View on HN

Not sure how much or if this had influence from Guava at all

I don't see any similarity between the two that would lead me to believe that there is influence. Why do you mention this?

This seems like a plug to your product more than anything else.

Nice! How long does `node -v` take now?

EDIT: OK, I see the main trick is to use PATH instead of shims.

rtx does not use shims and instead updates PATH so that it doesn't have any overhead when simply calling binaries

There is a good reason `asdf-vm` uses shims, and is that it does not have to interplay or worry about other tools that set PATH and tools that need a reference to an executable could be simply set to `~/.asdf/shims`.

Ill take it for a spin, but this choice might have a lot of consequences that are not easy to foresee. A good example is `direnv` which as you mention in the README now requires to be set in `.envrc` and then disable global `rtx` hook I guess.

This looks really cool, I find the mix between Zapier and Code to be :chef-kiss:

Do you plan to allow for self-hosting? eg. An org that wants to have a private version of this, or even internal version of it.

That seems like a ridiculously complex pipeline to maintain and onboard into. I personally dislike this "do it all" monorepos in most cases, there are cases were they work, but they also break a lot of other things.

I have not seen metris or blogs that prove this "uptick in build efficiency" or an increase productivity.

While I do like the idea behind bazel, I hate repeating deps in things like "go_repository" with gazelle.

I really like the idea of a new competitor on this market, and will be trying this soon, but please please stop doing a one-stop tool for everything and just let me plug and play other things, or your own things.

Used to really love things like GitLab, but I dont like bloated sites/tools and IMO things like Space or the direction GitLab has taken create bloat as they start to heavily couple their own tools and "workflows".