Project tasks break across tools and execution environments
Developers want a dependable way to run project scripts, but task workflows differ across Make and Python packaging tools, and VS Code remote setups can run tasks in the wrong environment. People moving from Rye or Hatch to uv miss familiar task-runner workflows, while another developer wants a more adoptable Make replacement with good interoperability. A compatibility-focused tool could address these related needs without requiring teams to rewrite every task at once.
For developers maintaining multi-toolchain projects. Mentioned from Jul 2019 to Dec 2024 on GitHub and Hacker News.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 4.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
But I don't feel confident investing in a new tool that has widespread industry adoption. I wish there was a 'better make' that tries to replace make the same way Zig wants to replace C, where they have great interop and make it easy to rewrite code into the new language
For those of us migrating over from Rye, one of its nice features is the built-in task runner using rye run and [tool.rye.scripts]
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks