Maybe for your use cases that's OK, but there are many situations where the size and ease of upgrading provided by shared libraries is worthwhile. For example it would suck to need to push a 40+ GB binary to a fleet of systems with a poor or unreliable internet connection. You could try to mitigate this sort of thing by splitting the application up into microservices, but that adds complexity, and isn't always a viable tradeoff if maximizing compute efficiency is also a concern.
ScreaminOctopus
In my understanding, you can't interface with the C abi without using an unsafe block.
The main issue I have with rust is the lack of a rust abi for shared libraries, which makes big dependencies shitty to work with. Another is a lot of the big, nearly ubiquitous libraries don't have great documentation, what's getting put up on crates.io is insufficient to quickly get an understanding of the library. It'd also be nice if the error messages coming out of rust analyzer were as verbose as what the compiler will give you. Other than that it's a really interesting language with a lot of great ideas. The iterator paradigm is really convenient, and the way enums work leads to really expressive code.
Anyone buying into this vaporware a decade after the original announcement while it's still nowhere near complete gets what's coming.
This is basically just a way nicer, more flexible cron syntax being dressed up as something ridiculous. There are legitimate reasons for wanting something like this, like running some sort of resource heavy disk optimization the first Friday evening of every month or something.
Yeah this tracks, I don't understand why people recommend Debian so much, especially to new users. Distros that update more regularly like Mint or Fedora (for non nvidia users) are much better options.
This would be solved if coin op washers locked. You could take the key like in a gym locker room. They'd probably have to charge per cycle + time to keep people from leaving them all day.
Kagi is the same as ddg 99% of the time.
I've been happy with Qwant lately, they have their own index so using them doesn't support the Google + Bing hegemony. They're also EU based and regulated by the gdpr.
Is that the case for the AMD boards as well?
Removing 3rd party kernel access will probably also make cheating harder. Kernel anticheat is necessary largely in part due to cheat software using exploits in the 3rd party extension system to get kernel privileges itself and evade user mode anticheat.
One specific example I encountered was ndarray. I couldn't figure out how to make a function take an array and an arrayslice without rewriting the function for both types. This could be because I'm novice with the language, but it didn't seem obvious. I ended up giving up after trying to dig through the docs for a few hours and went back to C++.