Yes

All over the place…

Jokes on you, my system is (mostly) -O3

Usually KDE, but I’m messing around with qtile atm.

I think it’s literally called “SQLite”. I haven’t used it though, so idk how good it is…

TrueNAS Scale if you want something simple that just works and Proxmox if you wanna configure/customize stuff with a lot more power under the hood…

Imo, either choice is better than unraid.

doesn’t vscode have an extension that does that?

My question is… why proton drive and not github or codeberg or… literally any VCS?

I’d still recommend dual booting, just in case…

I’d say dual boot. Jumping ship from windows to linux without it is very hard, especially if you enjoy playing a windows-only game or rely on windows-only software. A virtual machine can work for some basic software, but you need to do GPU passt trough to the VM to be able to game at all, which is a… let’s just say not insignificant amount of messing around and configuring stuff.

Android studio?

Chimera Linux is also a pretty cool independent distro…

I mostly use Spotify, but have the flacs of a few albums I really like on navidrome. As for how I got them… Yeah. I do have the for CDs a few of them but I don’t have a CD reader and most of them are completely destroyed, so I feel like piracy is justified for those.

Calling a language useless just because you don’t understand it has to be the most retarded take I’ve ever heard.

! Защо си направи труда да преведеш това, нали беше безполезен? !<

You sell it and buy a normal one /s

“Did stuff”

//TODO: Make this better

And you never look at it or touch it again.

There, code fixed!

Sums up my experience with C++. It’s fun until you actually start using it and then you get hit with: Idiotic syntax, no package management, C compilers, different operating systems, compiling in general, having to code everything from scratch, memory management and a lot more…

Shit hit me so hard, I began learning web dev instead and never looked back…

Changing stuff and seeing what happens. Yeah, about sums up my “debugging”.

What I usually do is I explain what the function does and, if not self explanatory, explain why it does such thing. Like, with the clock example, I’d explain that it tells the time and then, if not immediately obvious, explain why the time needs to be known… Smth like that.

There is no “correct” way of commenting code. I personally think the more verbose, the better, but that’s an unpopular opinion afaik. As long as the code can be understood, the comment is doing it’s job.

PS, I’m also kinda new to programming, mostly doing JS and React stuff