disclaimer #1: I work at tea
to that end, we think the kind of people that enjoy discovering projects on github intersect with people who, first and foremost, want to use them. so, how can we build on homebrew with its simplicity to remove the only barrier between a package that you find and your using it?
a core principle we focused on was to develop a package manager that eliminated the package management for end users. tea focuses on usage, allowing you to use anything you discover on GitHub, as long as it is packaged by us. We built on Homebrew's simplicity, by replacing `brew install foo` with a much simpler `tea foo` -- effectively bypassing the install step, so you can use it without any additional steps.
disclaimer #2: i am a python developer, so package management to me by definition is along the lines of virtual environments, making sure i get numpy before pandas, etc. etc.
one standout feature of tea is that it sandboxes everything. tea automatically injects virtual environments with the required packages into project directories with a readme and .git. i found this feature particularly valuable, especially when dealing with `graphviz` and `pygraphviz`. tea consistently solves such issues, ensuring a smooth development process.
disclaimer #3: I am learning bash right now, but prefer a front-end app.
the gui is what you hope GitHub's discover page was. we've got some fun AI tools right now, including stable diffusion's web-ui and openai's whisper trained on llama -- all open source.
