Personally I’m more in the “oh yes please take my job as a programmer” mindset, yet none of the currently available tools seem to be anywhere near capable of it.

When they do, I guess I’ll just translate the b.s. customers spit into something that’s even humanly readable, just merely distilling the intent often isn’t enough. Also A.I. needs to ‘learn’ to say no, because even though the customer asks for something, doesn’t mean they actually want to have the result of their question.

please killall

I see…

Simplest solution would be to setup the nfs/smb as storage for backups and making a backup schedule. Datacenter -> Storage -> Add -> SMB/CIFS

Datacenter > Backup > Add

On Error Resume Next

Visual Basic is a beautiful language

“A bit loud” is understating it, those drives rip and tear (we use exos X18 drives). I pity the person trying to sleep next to those.

They are good though, while we had one (of 5) fail within the first week but that was quickly resolved.

A smart powerplug and/or a fingerbot would solve that problem I guess? But at that point it’s probably cheaper to buy a network connected picture frame.

You could use something like the Toshiba flash air?

Missing the joke here? We run a 3090 and a 3900x just fine on ArchLinux.

The biggest feature of Wayland for me is mixed refreshrate monitors works OOB. On X this is a pain to get even remotely working and it’s impossible if your monitors aren’t dividable (120/60 works, 144/60 stutters).

This is from my experience something that is starting to be a way more common issue (high refreshrate laptops with 60 external monitors at businesses or high refreshrate monitor for gaming and a smaller secondary monitor for info lookup/discord).

other than that, Xorg does win the “more stable” prize for me, but if I wanted stability, I should’ve become a carpenter.

It’s quite a bad UX, but generally error 2 from make means the called program resulted into an error.

Usually this is accompanied with another error somewhere up the log. Multiple cores can make this a challenge to scan the log for however, so maybe try compiling without the -j argument, that should get the actual error closer to the end.

From my experience, it’s usually an outdated config for the kernel (like using a config for 5.1 while compiling 6.7) or a missing dependency. However the real error will be somewhere among the logs, who knows, maybe it’s a missing processor instruction (it’s really bad UX).

oof

I prefer for it to be just a warning so I can debug without trouble, the build system will just prevent me from completing the pull request with it (and any other warning).

While I wholeheartedly support and use linux for gaming, I rather blame this on the attempts of apple to block gaming on a mac as much as possible (removing 32bit support, the switch to ARM and not using established standards like opengl and vulkan but building their own ‘metal’)

I use Trilium, it just scratched the need I had which obsidian and logseq couldn’t somehow.