The same arguments about learning vi/vim/neovim holds for ed. It’s not intuitive, you need to get used to it, you need to learn, etc. People choose not to learn vim for the same reason vim users don’t want to learn ed.

It’s a text editor. It all began with the ed editor, which is very simple and does one thing, it edits files. Then someone extended it into the ex editor. Then someone added a new feature: being able to visually see the file you’re editing, which became vi, the visual editor. Then someone improved that, into vim. What began as an editor where you needed to be fluent in regular expressions but otherwise was simple, is now a very complex editor, moving the functionality of the old UNIX tools into the editor itself.

Curiously, I also got milk and irish passport in bing.

I got a similar result in DDG.

After reading this I was at the local grocery store and counted 17 different kinds of bearnaise they sell. Sweden loves bearnaise.

One time I figured out why a strange dependency was needed in a LaTeX book. It’s part of the official documentation of a project and the author had opened an issue about it. I dug deep into the package code and figured out why, came up with a fix, and contacted the author about the solution. That was two years ago and they have not replied or fixed it, but just worked on different things. I don’t demand anything, but I haven’t felt motivated to help out since then in that documentation project.

This reminds me of Rob Pikes paper from the year 2000.
http://doc.cat-v.org/bell_labs/utah2000/utah2000.html

If we want to do something radically different, there’s always gopher and gemini browsers.

ed is sadly not installed by default on some modern distros. Even vi is often a symlink to vim in vi-mode.

It’s intuitive if your previous editor was ed(1) and you’re using an ADM-3A-like keyboard.

What are main things you’ve found that BSDs lack to make you prefer GNU+Linux? What are things from the BSD world you wish that GNU+Linux had?

How do you decide what to archive, and what is the long term plan? If Annas goes down it can be pieced together again? Or is it served to users now too?

The archive team sounds interesting!

What can an ordinary user do at this point that would help?

That’s how I think about it too. I guess the original description was a bit vague, what they did to the americas. It includes both. First invasion, then immigration.

I could be wrong, but to me those words describe the initial phase. Once established as a society, the rest involves people moving into this society, which I would call immigration.

What would you call it instead?

It’s more that changes can be made with coordination across the OS, with a shared vision and goal. Linux distros are primarily integration projects, putting together the components from other peoples projects. BSDs are in control of the base OS project as one coherent project.

I see what you mean now. I thought you meant as in upstream/downstream.

Tumbleweed is not a derivative of Leap.