@a1ba@suya.place struct Moe { struct Moe *next };

@a1ba@suya.place Coming from , I keep forgetting that you have to write "struct" when you use a struct as a type you've defined.

@alyxshang yeah, love polluting the only global namespace I got with typedef struct foo foo;

@a1ba@suya.place Sarcasm?

@alyxshang no. But many programmers tend to do that just to avoid writing struct/enum/union just everywhere

@a1ba@suya.place Do they? I usually dump all my custom types/structures into a separate file and separate these things. I might know what's going on in that moment but after some months I won't anymore, even though dragons have good memories.

@alyxshang polluted namespaces are noticeable if you have an auto complete.

@a1ba@suya.place Now you know why I don't use ClangD inside Neovim's default LSP plugin.

@alyxshang I try to not use clangd at all, it makes my qtcreator visibly lag when I edit headers

@a1ba@suya.place Why not use something simpler? I really don't like bloated IDEs because a) they take up a lot of storage, b) they're usually very slow, and c) I spent too much time acquiring the muscle memory for Neovim.

@alyxshang QtC (without dumbass clangd) is actually pretty lightweight and fast.

If I really want to code in something simple, I would rather do it in GNU Nano because apparently everything else is not for human beings.

@a1ba@suya.place QtC? Explanation needed, please. "Not for human beings"? Help, I'm being bullied.

@alyxshang short for qtcreator

not for human beings? Yeah, literally. I don't get why text editor can't just edit text.

@a1ba@suya.place But isn't that kinda the point of why NVim and Vim exist? They are recycling an older technology that was there from the very beginning and improving it.

@alyxshang I don't think adding new letters to broken concept helps it

@a1ba@suya.place Too eepy.

@alyxshang yeah same :tiredcat:

@a1ba@suya.place Would be down for a hug, tho plus your pfp is cute.​​

@alyxshang