Textual VS HomeBrew

Textual's source is on GitHub, and the most recent commit was only 4 months ago, so it appears it's still being worked on.

Textual¹ is open-source but sells the precompiled app. Keka² has the app available for free on GitHub but charges for it on the Mac App Store, to support development.

¹ IRC client for macOS: https://github.com/Codeux-Software/Textual

² Un/archiver for macOS: https://github.com/aonez/Keka

Textual is often the most recommended IRC client for macOS. You can buy it for $7.99 or you can simply build it from source. Let us look at how to do exactly that.

Textual is a good example of this working IRL for me. Their app is one of the best IMO IRC clients on MacOS, is open source [1] and is also sold on the App store and their site.

1. https://github.com/Codeux-Software/Textual#original-limechat...

2. https://www.codeux.com/textual

Textual: https://www.codeux.com/textual/

Two quick examples: Keka and Textual[2] are both open-source and you can pay for them on the Mac App Store or by direct payment. The former gives you compiled builds either way, the latter only if you pay.

[1]: https://github.com/aonez/Keka

[2]: https://github.com/Codeux-Software/Textual

Homebrew - The Missing Package Manager for macOS (or Linux)

Homebrew is a highly popular package manager on macOS and Linux systems, enabling users to easily install, update, and uninstall command-line tools and applications. Its design philosophy focuses on simplifying the software installation process on macOS, eliminating the need for manual downloads and compilations of software packages.

Homebrew - package manager for linux-based OSs.

Package Manager: Homebrew

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

Are you using SQLite that ships with macOS, or SQLite installed from homebrew?

I had a different problem in the past with the SQLite that ships with macOS, and have been using SQLite from homebrew since.

So if it’s the one that comes with macOS that gives you this problem that you are having, try using SQLite from homebrew instead.

https://brew.sh/

Before we begin, make sure you have Homebrew installed on your Mac. Homebrew is a package manager that makes it easy to install software and dependencies. You can install Homebrew by following the instructions on their website: https://brew.sh/

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

I have always either installed Node from the installer provided by the Nodejs website or, via Brew in macOS. I have also used nvm in the past but did not know that there was a best practice to guide us.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq: