I’m at my age now and I’m just starting programming. My plan is to never do it for money, only because I want to as a hobby.

I just feel that it’s technically wrong to call it x64. x86 is the architecture. The x belongs there, so x86-64 makes more sense, but not “x64”. It’s a marketing term, but it still bothers me.

Isn’t “x64” still an x86 architecture?

The picture called “Upstream and Prism programs” has the old logotypes for Yahoo, Hotmail, etc, and the old garamond version of the google logo, they must have been doing this for a while.

No, my passport has my real name of course, with “å”. In the airport system and on the boarding pass my name was spelled with “aa”.

I had to convince people to let me on board a plane because my name contain a swedish letter (å). Their computer system translated it into “aa”, which then didn’t match my passport.

And after you have learned Linux, download any distro that lets you work on your projects with the least hassle and get work done without fiddling around in every aspect of the OS. At least that’s what I’ve observed among older users who see the OS as a tool and not a hobby in itself.

Where I work, the fax was a way to ensure that information could be sent in multiple ways, if one way would fail. In the medical field (at least where I live) we must have systems with backup systems in a few layers. We have a nice digital medical chart system, and I still have to print out many things and put in a binder that no one ever reads. Because the internet could stop working, or electricity could fail. We even have routines for which types of pen and paper can be used if we need to write things by hand while electricity is gone.

https://sverigesradio.se/avsnitt/the-pirate-bay-skakade-hela-medielandskapet-nu-kommer-serien

Peter Sunde said that the show is not a fair description of what happened and that it’s missing the focus on what was important.

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.

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.

gnuplot surprisingly also has a strange license, containing “Permission to modify the software is granted, but not the right to distribute the complete modified source code.”

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?