How is Go not memory safe? Having escape hatches does not count, all the safe languages have those.
unique_hemp
joined 2 years ago
Due to the way Flatpak deals with nvidia drivers, you need to run flatpak update after any time the nvidia drivers update and you reboot the system. Thankfully you do not need to reboot after updating only flatpaks. Could not find a good source for this now, unfortunately.
As for the "why?" - flatpak apps do not contain the userspace parts of the nvidia driver required to use the GPU properly, they come packaged as separate runtimes. These nvidia driver runtimes need to match the specific driver version you are currently running. If they don't match, flatpak downloads the right runtimes when updating.
Yep, reinvent it for educational purposes and then burn it with fire.
Is it? Honestly I don't care about it anymore, I've been opening everything from task bar icons and search for ages now.
You can just disable web search through the settings app now.
"great work" 🤭
Even worse - it looks like Google might be forced to sell Chrome to some AI company.
What does it matter? They all rely on Mozilla to do the hard work - maintenance and keeping up with web standards, and then just slap a couple of features and customizations on top of it. If Mozilla dies the current forks are dead in the water.
A lot? All of them.
It's neither with parts from both.
Mastodon can also replace the main FB feed. Matrix would be the closest alternative for Discord, but it has its share of problems.
view more: next ›
That is a consequence of having parallelism - all mainstream pre-Rust memory safe languages with parallelism suffer from this issue, they are still generally regarded as memory safe. I don't know where you got that Java does not have this issue, you need to know to use the parallelism-safe data types where necessary.