This is a common use for tape, which can via tools like HPSS have a couple petabytes of disk in front of it, and present the whole archive in a single POSIX filesystem namespace, handling data migration transparently and making sure hot data is kept on low-latency storage.
Even just spawning a thread is going to make somebody complain that they can't build the code on their platform due to C11/pthread/openmp.
This matches squarely with my experience, but it's not limited to threading, and Rust evades a large swath of these problems by relatively limited platform support. I look forward to the day I can run Rust wherever I run C!
While Rust doesn't have C coverage, it has (by my last check) better coverage than something like CPython currently does.
The big thing though is Rust is honest about their tiers of support, whereas for many projects "supported platform" for minor platforms often mean "it still compiles (at least we think it does, when the maintainer tries it and it fails they will fix it)"
Not to be too glib though, there are obviously tools out there that have as much or more rigor than Rust and cover more platforms. Just... "supported platforms" means different things in different contexts.
All too common (not just with compilers) for someone to port the subset they care about and declare it done. Rust's decision to create standards of compliance and be conscious about which platforms are viable targets and which ones don't meet their needs is a completely valid way to ensure that whole classes of trouble never come. I think it's a completely valid approach, despite complaints from some.
Because, unfortunately, a terminal degree is not always a guarantee of future productivity.
String theory came into the public consciousness about two decades ago, followed by a backlash from a relatively small but persistent set of professors. String theory has largely dropped out of the public focus, but those researchers continue to hammer at it.
Woit is one of those. He's known primarily for his objections to string theory. His own work is just fine, but nobody outside of his discipline knows it.
It's a community repository for Fedora. It works similar to RPMFusion: you can use it along the official repositories to grab software that's not available there. If you'd like to reduce the number of organizations you're directly depending on, you may choose to use their Fedora fork, with their own repositories (forked from Fedora's), called Ultramarine Linux [0].
Rawhide is the development branch of Fedora. Terra is a community rolling-release repository that provides additional software on top of Fedora, for both the Rawhide and stable versions of Fedora. They're not directly comparable.
Sure they are. Rawhide is the official community-driven rolling release for the latest of Fedora. If you want to get some package into Fedora (and thus RHEL), put it into Rawhide, not Terra.
The man spend a tremendous amount of time trying to discredit the entire medical industry. In the past he has claimed to avoid cancer through prayer. This is part of a pattern.
The common thread from all the frontier orgs is that the datasets are too big to vet, and they're spending lots of money on lobbying to ensure they don't get punished for that. In short, the current corporate stance seems to be that they have zero agency, so which is it?
Huh? Unless you are talking about DMCA, I haven't heard about that at all. Most AI companies go to great lengths to prevent exfiltration of copyrighted material.
I note that the vide coding tools managed to keep the license headers in individual files, but the COPYING file containing the GPL2 has not made the transition.
reply