pkgx

Impressive work so far. I'm a fan

This rebrand was handled absolutely horribly. Breaking every installation of tea for a rebrand pretty much makes this project persona non-grata in anyone's playbook. If there was communication, it was ridiculously brief. The decision to break EVERY INSTALLED tea installation just to rebrand pretty much makes it obvious there's no interest in stability. Why would I possibly adopt pkgx after this? I'll just adopt NIX, which I was avoiding.

It would be nice to be able to set up a fixed (voluntary) monthly contribution amount to distribute among the used packages authors automatically. (I saw that you plan to add some monetization, I’m just suggesting the model that makes sense to me.) Something along the lines of SetApp. PS There’s a typo on the “open in terminal” image. “S” is missing in the word “constrained.”

It helps me to manage my virtual machines for builds

Don’t know what to think. I’ve been using Tea for months with about 8 packages installed. Today I decided to update Tea itself (via update menu option within the GUI) and bam…the app disappeared from my apps folder with no trace of what happened. Now I see Tea has been replaced with pkgx (on Product Hunt and Github, not my computer), however some type of warning or info would have been helpful.

🎉 Congrats to team tea on launching their free, open-source GUI package manager! 🌟 Here is my honest opinion: One-click installs, easy updates, and more security with sandboxed environments. 💪 Excited to see what else they have in store! 👀 What are your thoughts on the future of open-source funding?

Congratulations on the launch of the Tea sounds like an exciting new cross-platform package manager that offers a seamless and efficient way to automate dependencies and browse through hundreds of packages. Its focus on speed and smoothness is especially appealing, as many other package managers can be slow and clunky. This revolutionary tool is sure to be a game-changer for developers and programmers looking to streamline their workflows and simplify the process of managing dependencies. The ability to browse through a large number of packages and automate dependencies will undoubtedly save time and effort, while also ensuring that software projects are running smoothly. Kudos to the team behind Tea for developing such an innovative and useful tool. It's exciting to see how technology is constantly evolving and improving, and Tea is a great example of this progress. I look forward to seeing how this tool will continue to transform the world of software development in the future.

I need some clarification I just attempted to replace brew with tea ( its a healthier lifestyle choice for me) Because it is fantastic until I realized the --magic isn't happening for me. I wanted to reinstall iterm2 or pnpm via cli and the tea just sobered me up. I expected a full replacement - the same simple cli command interface where I can look up tea install iterm2 and i can copy and paste the code. or a very nice tutorial in the docs or youtube explaining the subtle difference, I was told it's the "homebrew replacement by the makers of home brew" and sure once I drink the tea ill be chill massaged into the tea's awesome long-term game plan of putting projects in pantries and repos on the blockchain saving open source for always. But in order to get people to use it (like me), especially from the simplicity that is brew I need more from this tool then the promise of magic - I need it to work. so please point me in the right direction because I need some tea. ASAP :).

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.