banseljaj

For quite some time, I have gathered this set of Rust CLI tasks that are exactly the same. I have used them as template generators for cargo-generate. This became a problem recently when I was writing a monorepo that had mixed projects (Rust server, Svelte Frontend, and Terraform deployment). This comes at just the right time for me to utilize this without going insane.

Also, I had a not-so-great experience with other builders/managers, including lerna so I love this.

@jdxcode, how long before I can replace Emacs with mise?

What are you talking about? You don't need to install node for this. It's a self-contained rust binary.

I started using mise back when it was still called rtx. I was a little annoyed by asdf's quirks and having it replicate that behavior while being faster and less intrusive in my shell configuration was great.

Since then, mise has folded in two capabilities that I needed the most: Task Running and Env Vars.

Overall, it has been a fantastic experience for me. I love how the developer has spent a lot of time ensuring compatibility with existing tools while still building future capabilities.

I will add one thing that I knew I needed but couldn't find anywhere was added through the recent backends feature. I do a lot of trust and R development and there are dev tools that I need installed that I don't use as libraries, just the binaries. It was a problem making sure that those dependencies were installed in a new environment. Now, it's just so easy: I list those in my `mise.toml` file, and that ensures they are installed and installable.

I have used GitHub Copilot since it came out. I mostly use it for code explanations and writing tests.

My experience is that you can't trust it completely for obvious reasons, so you need to know what you are doing before you can rely on these tools.

I have tried Amazon Q and was severely disappointed.