In my first year I had multiple issues with Linux. Mainly because I tried to install stuff that wasn’t meant for my version of the OS but for an older one and I blindly followed the “black market” tutorials how to uninstall and reinstall packages to meet requirements. That corrupted my system and I had to repair it multiple times. Also, I played around with many distros and multibooted them all, destroying my grub once or twice.

Now that I use Ubuntu for a “longer” time, I rarely have issues except hardware specific ones. For example the webcam doesn’t work on my dell laptop because apparently it is not supported right out of the box. But apart from that I have no issues compared to windows (where imho windows 11 is an issue in itself).

I bet lock picking lawyer opens more brands.

If by chance you understand German this is an excellent beginner course: https://www.math.uni-bielefeld.de/~frettloe/teach/unix20.html otherwise I would grab a book; but I have no specific book to recommend. However, to name some I found interesting after a quick search:

• How Linux Works: What Every Super-User Should Know
• The Linux Command Line

While I think this is a great comment as Nebula is an interesting platform, I fundamentally disagree with how Nebula decides who can create content on their platform.

If I understand it correctly, you can only become a Nebula content creator if a content creator in Nebula knows you and vouches for you. This makes Nebula inaccessible for new creators.

That being said: With Nebula you do get a high quality selection of content creators.

I have set up a good hand full of dual booted Windows/ Linux machines. Never had any major issues. However, I also noticed that I only use Linux except for games and that’s slowly changing, too, so I would suggest trying the dual boot if it makes you more comfortable to realize yourself that you don’t need it.

Yes, it is absolutely valid that you decided to commercialise your project and keeping parts or all of the code closed. As I work in the public sector and we are encouraged to use open source and write open source software, my knowledge regarding closed software solutions is thin. Is there a “standard way” how closed software is able to guarantee private key safety? I could imagine solutions where there is a separate handler that is open source so that one can verify that only specific information is passed into the closed software area, but this doesn’t sound feasible when talking about full terminal support within the closed software.

Again, there is nothing wrong with going commercial! I am sure I will release closed software (side projects), too, at some point.

Giving it a quick scan, it does look interesting. I am not sure whether I will try it as I don’t see the need to visualise beyond what I can do with a shell and the openstack dashboard, but there can definitely be use cases for it.

Not being FOSS is the deal-breaker though. Not sure if I am too much of a sceptic but I prefer open source when having software that accesses my private key/servers.