macports-www VS micro-editor

macports - https://www.macports.org

I switched to MacPorts after becoming tired of Brew tainting my filesystem.

MacPorts keeps things clean in /opt/local.

https://www.macports.org/

https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-pack...

gh is available via Homebrew, MacPorts, Conda, Spack, Webi, and as a…

I've read the article but some questions still remain. Does Retroactive install the shared dylibs of previous macOS releases? Or does it use an approach similar to https://www.macports.org/ ?

I highly recommend using yt-dlp to download videos in the highest quality available from a wide variety of web sites (notably YouTube, hence the "yt" in the name, but it supports a ton of sites). The best way to install it is with an open-source package manager, either Homebrew or MacPorts. These make it easier to install dependencies like Python 3.11 and optional (but highly recommended) utilities like ffmpeg. Both Homebrew and MacPorts are great, and you can install both side-by-side. I guess I'd recommend Homebrew over MacPorts because it downloads pre-built binaries instead of compiling from source, so it's faster. But again, they are both great.

This is Reddit so they will most likely be people who say to download Macports, but frankly, I don't care, and homebrew is enough for me. I'm not smart, but I know not to download programs/random things without prior research, don't use sudo commands on things you don't know and don't enter your password if you feel unsafe.

The initial setup was quick and painless, but I quickly realized that MacOS does not ship with a package manager (to my surprise!) the Apple Store won't be enough to cover my needs, so onto Google I went. I learned that the two most popular package managers are Homebrew and MacPorts. After reading for a while, I found some users concerned about how Homebrew managed folder permissions (here and here), and with the fact that it installs already compiled binaries, which may be a security/privacy issue. However, it seems that the folder issue was addressed with the ARM release of Homebrew, which now installs under the /opt/homebrew folder.

On Linux, most distributions come with their own package manager out of the box (e.g. Ubuntu / Debian has APT). One annoying thing about macOS as a development platform is that it does not come with one out of the box, and Homebrew has emerged as the most popular third-party management by far. There are other ones like MacPorts as well but I think this is the kind of thing where the popular one tends to become more popular because people don't want to learn/use multiple package manager. I actually used to use MacPorts before I switched to Homebrew just because it's been getting a lot more momentum / features / development and it's where every package is.

Others have offered solutions, but for future reference the actual Terminal commands that failed would be useful; "File not found" sounds like a path error, "Command not found" sounds fixable via Homebrew or Macports

TL;DR, about the section that states software from other UNIX-like OSes is hard to port to MacOS, how about homebrew and macports?

To see more screenshots of micro, showcasing some of the default color schemes, see here.

Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:

- gdu: a NCDU clone, much faster on SSD mounts [1]

- duf: a `df` clone with a nicer interface [2]

- massren: a `vidir` clone (simpler to use but with fewer options) [3]

- gotop: a `top` clone [4]

- micro: a nice TUI editor [5]

Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.

[1]: https://github.com/dundee/gdu

[2]: https://github.com/muesli/duf

[3]: https://github.com/laurent22/massren

[4]: https://github.com/xxxserxxx/gotop

[5]: https://github.com/zyedidia/micro

> The worst way to store and manipulate text is to use an array.

Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.

Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.

Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).

[1] https://github.com/zyedidia/micro

[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...

[3] https://github.com/cessen/ropey/pull/67

There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:

found that micro has dedicated info page for copy paste

micro: winget install zyedidia.micro