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?

From an ATM maybe, the actual bank offices don’t have cash. But the question is, what would I do with the cash, only a few stores like big chain grocery stores accept cash nowadays in Sweden. Small stores and cafés etc almost never accept cash as payment. Even beggars outside on the street often have a QR-code for their mobile app transfer because so few people carry actual money.

I literally don’t know what our money look like. I have a vague memory that the 20 krona bill was blue, but beyond that I don’t know.

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.

One reason is that different distributions of linux do things slightly different. Would it be better if there was only one linux os? For some devs of third party software, probably, but diversity and freedom to fork software has been good to linux, and no one could decide what everyone else should use anyway.
So, each distribution takes the available software and package it to fit their distro specifics, and those packages go into their repositories. The benefit of using official repositories is that someone has gone through the trouble of making sure it will work on your system safely. There’s accountability and hopefully a bug tracker etc. When you download from a random website you have to trust them instead. Then… you have companies working outside of this model, usually they provide a flatpak or their own third-party repositories. Then you get all these extra steps, but it’s not how most distros prefer to handle software.

curl is a good tool to have in general, you can install it with sudo apt install curl

Sweden classified PKK as a terrorist organization in 1984. Sweden does not finance PKK.

Similarly, the viking rune “alphabet” is called the Futhark, because the first letters are pronounced F, U, Þ, A, R, K.

ntfs is a windows filesystem, so you’d have the same problem in windows if you used a linux filesystem that isn’t supported out of the box by the windows os.

Of the points, not allowing others to make money from a fork could be difficult. You can ensure that a fork stays free, but iirc it’s hard to stop anyone making money. Although I’m hesitant to suggest this, you might want to look at the license for Gnuplot (it’s not gnu as in GNU), which is imho the least free license commonly called “free software”, it effectively prevents forked projects. In which case another question might be, do you want it to be free software? Is the gratis aspect more important?

There’s also PonyOS (https://www.ponyos.org/) They wrote their own kernel, so it’s not Linux, but it is Unix-like.

Me too, I’ll stick with good old HannahMontanaBSD.

and GNU?

If people will be people, the interesting difference will be how the platform works. I guess this is the true test of the federated approach. What does it hinder or facilitate in practice and what are the actual effects?