My KDE Neon crashes intermittently for the past 2 years without a clear pattern or trigger. I suppose the only hint was that it often (not always) happens when I was using graphic intensive software, such as video player or remote desktop. But also happens during a cold boot up, or when the monitors wake up from sleep. It's mostly unpredictable.
What made the diagnosis confusing is the kernel log mostly shows error like this:
With my newly built dev machine, rocking an AMD Ryzen 9 5950X CPU and AMD 5700XT, the current LTS kernel (20.04 - Focal Fossa) from Ubuntu has very limited support, such as the occasional GPU freeze / tear / flickering, bios reporting EDAC memory issues etc. One major issue I don’t need worry this time is graphics drivers, because AMD GPU drivers are integrated into the kernel already. So the only hurdle is to upgrade the kernel (and the BIOS/UEFI).
Recently I discovered KDE Neon, a GNU/Linux distro based on Ubuntu LTS but with the bleeding-edge KDE plasma.
When you install VS Code with its remote-SSH plugin, and logs into a shell via SSH. VS Code will install its backend on the remote machine (at ~/.vscode-server) and turns the client into a front-end (after all, it’s just an Electron app).
The concept of `closure` may seem deceivingly easy to grasp – just a function that returns another function which could access the parent function’s environment.
I’ve just came across this article Into the personal-website-verse. It made a few points along with my comments:
I’ve been thinking of setting up a technical blog for quite some time now and I understand there are many options available online. None of them clicked for me however for various reasons:
There’s heated discussion on the impact of AI tools (or machine learning to be more accurate) on radiology. Here’s a points I summarised from various conferences and readings on the internet.