Yes. Pedantically (as if this is a real language to begin with) it would be “Trick AND NOT Treat”.

Huh. I did as well. Like /use/bin was for user installed applications and such. You learn something everyday.

And then you realise your dumb endless ls-ing has pushed the command off the history list

Fixed :)

Depends on where you live. With my tariff I get paid to use energy during negative price periods.

Edit: typo.

You will still have private/public sections, interfaces (unless you class them as inheritance), classes and instances, the SOLID principles, composition over inheritance. OOP is a lot more than just large family trees of inheritance, a way of thinking that’s been moved away from for a long time.

I’ve only used DaVinci for small projects, so I don’t know their eco system too well, but what made you buy a product when you were having problems getting it to work? :O Does the studio version offer better hardware acceleration or something like that?

It was a lot of fun for me. I did it without a virtual machine (would not generally recommend) on a older laptop I wasn’t using anyway. I wasn’t very successful in the end however. My own built kernel couldn’t produce any vga output. I tried to fix it for a handful of nights, but in the end gave up and called it good enough :P So I might comeback to it later to fully complete an installation.

But it was good learning oppertunity. It showed that just compiling a version of the Linux kernel isn’t very complicated. It even comes with a very nice TUI to select your build options!

And then plug those values into a image generation service to give users a visually intuitive way to see if there’s cooffe or not!