https://github.com/CyberTimon/RapidRAW is rapidly going to be a nice cross-platform alternative to Lightroom

I am wondering what vite+ will have that will really make it worth it compared to the "rstack" (i.e. rspack, rsbuild, rstest, rslint, etc.) rsbuild is already excellent and things like remote cache are on their roadmap?

Good question.

The first and most important distinction is obviously which ecosystem you are more familiar / invested in (webpack vs. vite). It does make sense for projects deeply coupled to webpack to consider rspack first.

Putting that aside:

- Vite+ is a commercial offering with a company that can provide paid support. Rstack is a big corp by-product where their primary customers are internal teams.

- The Vite ecosystem provides way more options in choice of meta frameworks (Nuxt, Astro, React Router, Tanstack Start, SvelteKit, SolidStart...), and 3rd party tooling integrations

- While both written in Rust, our tools in general perform significantly better than rstack. With the upcoming full bundle mode, Vite 8 will be at least 2x faster than rsbuild across all categories (dev server start up, HMR, production build)

- Vitest and Oxlint are mature and widely used in production. rstest and rslint are both quite new and not even feature complete.

Familiarity I guess? I've never heard of rsbuild before. In comparison, the "Vite" name directly brings me joy and makes me think of high quality, enjoyable tooling.

They seem to have less marketing for sure. If you are migrating from webpack or create-react-app, rspack/rsbuild is a no brainer. (at least worth a try IMO)

if you are heavily on custom webpack config, then rspack would be your only practical option. for all other use cases like CRA migration, vite is much better and supported option as vite unlocks entirely different migration paths for your project

With GitLab, I have found https://github.com/firecow/gitlab-ci-local to be an incredible time-saver when working with GitLab pipelines (similar to https://github.com/nektos/act for GitHub)

I wish GitLab/GitHub would provide a way to do this by default, though.

act is great. I use it to iterate on actions locally (I self-host gitea actions, which uses act, so it's identical to github actions).

One of the goal of hk is to be used with mise (https://mise.jdx.dev/dev-tools/)

mise supports an experimental bootstrapping feature: it can download itself and install the tools required for the project.

See https://mise.jdx.dev/cli/generate/bootstrap.html and https://mise.jdx.dev/continuous-integration.html#bootstrappi...

You will be able to use mise to set up any tools required for the linters. See https://mise.jdx.dev/dev-tools/

You can use this trick with mise (mise-en-place) for small tasks: https://mise.jdx.dev/tasks/toml-tasks.html#shell-shebang

  [tools]
  uv = 'latest'

  [tasks.python_uv_task]
  run = """
  #!/usr/bin/env -S uv run --script
  # /// script
  # dependencies = ["requests<3", "rich"]
  # ///

  import requests
  # your code here 
  """

Something similar is shown for uv here: https://simonwillison.net/2024/Aug/21/usrbinenv-uv-run/

I think you should give `mise` a chance. I believe it can help improve your workflow.

It's better at managing tools than `asdf`, very close to `direnv` and superior to `make` as a task runner (more verbose but much easier to understand). One of the advantages is that `mise` tasks can be standalone files (you can even write file tasks in python if you prefer, see https://mise.jdx.dev/tasks/file-tasks.html)

There is a plugin that works well to automatically configure some of the SDKs https://plugins.jetbrains.com/plugin/24904-mise

mise tasks (https://mise.jdx.dev/tasks/) are great!

IMO, mise tasks are much better than `just`. A few things that make mise superior:

— solid environment variables support

— can run tasks in parallel, has a watch task feature, support for skipping tasks,…

— mise supports file tasks (i.e., running shell scripts, as many comments are suggesting here - https://mise.jdx.dev/tasks/file-tasks.html)

— mise tasks are defined using `toml`, and not a custom syntax

Have a look at https://httptoolkit.com/ which works with a lot tools (even cli)