My ~/dev dir is a mess. Hundreds of cloned open-source projects. Work projects. Side-projects. And multiple worktrees for each repo.
I'm thinking of building a cli + gui tool to manage all the code on my computer.
I also think that debugging project dependencies is too difficult.
And I'm not just talking about your project's package dependencies. Or even your package's native dependencies. I'm talking about system-installed native dependencies...such as postgres, chromium, the node.js runtime, electron.
Many tools for high-level languages are being built in system languages like Rust and Go. E.g. Ruff, SWC, esbuild, etc.
All these native deps are difficult to setup debuggable local build envs for, and also difficult to integrate into your project. Think about working on a Node.js project and wanting to set a breakpoint in the Node.js runtime. It's non-trivial. Strange build instructions, pulling sub-modules, setting up your IDE, running your script with debug flags.
I think it might also turn into a replacement for homebrew. Instead of installing from bottles, repos would be pulled down along with all their dependencies, and git worktrees would be setup to link them together, and setting up your IDE for debugging would be one cli command.
The goal would be to make it super easy to set a breakpoint at any piece of code executing at any level of the stack. There would also e a simple git workflow for submitting a patch.
I also envisage a visual dependency graph to manage everything.
The final piece would be making the kernel debuggable as much as is possible.
I'd also like to have a GUI for all debugging tools for different types of problems, to avoid hunting down the right cli tools. And also a GUI for all configuration on your computer such as `~/config` stuff but also env vars, also showingl dependency graph and override chain.
I'm thinking of building a cli + gui tool to manage all the code on my computer.
I also think that debugging project dependencies is too difficult.
And I'm not just talking about your project's package dependencies. Or even your package's native dependencies. I'm talking about system-installed native dependencies...such as postgres, chromium, the node.js runtime, electron.
Many tools for high-level languages are being built in system languages like Rust and Go. E.g. Ruff, SWC, esbuild, etc.
All these native deps are difficult to setup debuggable local build envs for, and also difficult to integrate into your project. Think about working on a Node.js project and wanting to set a breakpoint in the Node.js runtime. It's non-trivial. Strange build instructions, pulling sub-modules, setting up your IDE, running your script with debug flags.
I think it might also turn into a replacement for homebrew. Instead of installing from bottles, repos would be pulled down along with all their dependencies, and git worktrees would be setup to link them together, and setting up your IDE for debugging would be one cli command.
The goal would be to make it super easy to set a breakpoint at any piece of code executing at any level of the stack. There would also e a simple git workflow for submitting a patch.
I also envisage a visual dependency graph to manage everything.
The final piece would be making the kernel debuggable as much as is possible.
I'd also like to have a GUI for all debugging tools for different types of problems, to avoid hunting down the right cli tools. And also a GUI for all configuration on your computer such as `~/config` stuff but also env vars, also showingl dependency graph and override chain.
Just some thoughts.