It’s satire, pointing the cognitive dissonance that allows people to recognize that fumes are deadly but never question the fact that our entire “modern” concept of city planning is built around constantly being in and around the machines that produce these fumes 24/7.
For anyone interested in learning more about bloom filters, this is a technical but extremely accessible and easy to follow introduction to them, including some excellent interactive visualizations: https://samwho.dev/bloom-filters/
The major car manufacturers have literally been collaborating for the better part of a century, along with oil companies, to keep Americans dependent on cars. It’s a well-documented fact. Even long before Citizebs United made corporate bribery legal, they’ve been using the state’s power to quell protests, destroy non-car infrastructure, and outlaw use of our streets for anything except cars.
There are several things I disagree with in this article, although I see where the author is coming from. I will never be onboard with "I’ll take my segfaults and buffer overflows.", and I fundamentally disagree about concurrency. I also think that cargo is fantastic, and a lack of standard build tools is one thing that holds rust's predecessors back.
However, a majority of the authors points can be boiled down to "C is more mature", which doesn't tell us much about the long-term viability and value of these languages. For example, in the author's metric of stability and complexity, they use C99 as the baseline, but C99 is the state of a language that had already had almost 3 decades of development, whereas Rust has been stable for less than a decade. Talking about superior portability, stability, and even spec, implementations, and ABI is in some real sense just saying "C is older".
That's not to say those things aren't valuable, but rather they aren't immutable characteristics of either language. And given that safety is playing an ever more important role in software, especially systems software, I think Rust will catch up in all the ways that are meaningful for real projects more quickly than most of us realize. I certainly don't think it's going anywhere anytime soon.
One alternative that seems promising is Nebula. It only fills a small part of the role YouTube currently occupies, since it focuses on being a platform for high quality professional content creators to make unfiltered content for their audience, but it's funding model seems to be much more honest, stable, and so far viable than an ad-supported platform or the other alternatives. I don't think anything could realistically replace all facets of YouTube (and I think the internet might be healthier if it were a little bit less centrally-located). A self-sustaining, straight-forwardly funded platform like Nebule seems like the best path forward to me.
I think they’re referring to the fact that Edge runs on the Chromium engine which, as the name implies, is a Google product.
I don't think we should abide hate speech in any format for any reason.
That said, it's concerning that the Australian courts were able to get recompense for Barilaro, yet Barilaro's very real corruption and straight up evil that Friendlyjordies was trying to call attention to has gone completely unaddressed.
I can't claim full understanding, but what I took away from it was that NVIDIA somehow ended up using GPL-licensed code in their proprietary drivers, possibly in a way that could incriminate the Linux kernel if not handled properly. My best guess (as someone with no kernel programming experience) is that NVIDIA sometimes contributes code directly to the Linux kernel that exists solely to support their proprietary drivers (the shims mentioned in the article). Apparently, these shims were exporting GPL-licensed code for use inside the proprietary drivers, which would be a violation of the GPL (unless NVIDIA made the source code for their proprietary drivers freely available in compliance with the GPL).
TLDR: (I think?) NVIDIA essentially infected the linux kernel with license violations to support their proprietary drivers, and the linux kernel devs are working to excise the violations and prevent anything like that going forward.
This is, in part, a correlation. To some extent, compiled Rust is fast because compiling Rust is slow. That is, Rust does a lot of work (static analysis) at compile time so that the runtime binary is as fast as possible.
I think you’re confused on a couple of points.
So their track record so far with delivering on their promise of upgrades and repairs is short, but so far it has been stellar.
I agree with this, Elon is a disingenuous selfish prick, but this source doesn’t provide any indication that Musk admitted anything, it’s just speculation from detractors.