If drama was going to drive Linux kernel developers away, it would have just been Torvalds working on it alone for 30 years. For better or worse, that community has selected for having very thorough antibodies to conflict.
I agree it doesn’t magically eliminate bugs, and I don’t think rearchitecting the existing Linux kernel would be a fruitful direction regardless. That said, OS services split out into apps with more limited access can still provide a meaningful security barrier in the event of a crash. As it stands, a full kernel-space RCE is game over for a Linux system.
If you’re trying to demonstrate something about Rust by pointing out that someone chose C over Perl, I have to wonder how much you know about the positive characteristics of C. Let alone Rust.
> Google has probably the largest C++ codebase in the world. Migrating to Rust would be so expensive that the board would squash it.
Google is transitioning large parts of Android to Rust and there is now first-party code in Chromium and V8 in Rust. I’m sure they’ll continue to write new C++ code for a good while, but they’ve made substantial investments to enable using Rust in these projects going forward.
Also, if you’re imagining the board of a multi-trillion dollar market cap company is making direct decisions about what languages get used, you may want to check what else in this list you are imagining.
You almost certainly have a bunch of devices containing a microcontroller that runs an architecture not targeted by LLVM. The embedded space is still incredibly fragmented.
That said, only a handful of those architectures are actually so weird that they would be hard to write a LLVM backend for. I understand why the project hasn’t established a stable backend plugin API, but it would help support these ancillary architectures that nobody wants to have to actively maintain as part of the LLVM project. Right now, you usually need to use a fork of the whole LLVM project when using experimental backends.
Look at OpenAI - where there’s a will (and an army of lawyers), there’s a way. That said, I don’t think any of the big tech orgs would be interested in acquiring them. Google and Amazon even already have their own public CAs that are in the major trust stores.
I don’t know why the Snowden revelations would prompt a business necessity, at least not a rational one for most businesses. What would the NSA slurping up all your data do to your business, that was both bad enough and likely enough to plan for? What it would do to your country or you as an individual is separate from that.
What does bothering to read some distributed systems literature have to do with demanding unnecessary perfection? Did NATS have in their docs that JetStream accepted split brain conditions as a reality, or that metadata corruption could silently delete a topic? You could maybe argue the fsync default was a tradeoff, though I think it’s a bad one (not the existence of the flag, just the default being “false”). The rest are not the kind of bugs you expect to see in a 5 year old persistence layer.
What fields? Cargo culting is annoying and definitely leads to suboptimal solutions and sometimes total misses, but I’ve rarely found that simply reading literature on a thorny topic prevents you from thinking outside the box. Most people I’ve seen work who were actually innovating (as in novel solutions and/or execution) understood the current SOTA of what they were working on inside and out.
I don’t think Nixon cared about indigenous people in South America. Not because he was a great guy, just because they didn’t matter to him even slightly. He definitely cared about communist militias though.
They’re higher relative to median latencies for each. A high end SSD’s P99/median is higher than a high end HDD. That’s the relevant metric for request hedging.
Pulsar can do most of what NATS can, but at a much higher cost in both compute and operations (though I haven’t seen a head-to-head of each with durability turned on), along with some simply different characteristics (like NATS being suitable for sidecar deployment). NATS is fantastic for ephemeral messaging, but some of this report is really concerning when JetStream has been shipping for years.
It is if they’re in the same physical datacenter. Usually the way this is done is to wait for at least M replicas to fsync, but only require the data to be in memory for the rest. It smooths out the tail latencies, which are quite high for SSDs.
Wow. I’ve used NATS for best-effort in-memory pub/sub, which it has been great for, including getting subtle scaling details right. I never touched their persistence and would have investigated more before I did, but I wouldn’t have expected it to be this bad. Vulnerability to simple single-bit file corruption is embarrassing.
It’s like using a non-cryptographically secure RNG: if you don’t know enough to look for the fsync flag off yourself, it’s unlikely you know enough to evaluate the impact of durability on your application.
The war on drugs is a scam, but pretty sure if the primary goal was to oppress indigenous people in another country the US government could’ve found a cheaper way (both fiscally and politically).
That’s not a technical problem - this kind of system can scale out just fine and has in other jurisdictions. SEPA is far from perfect, but is better than Bitcoin for everything but evading governments (justified or otherwise). We’ll see what Fednow looks like in a few years - the banks are definitely dragging their feet and it’s hard to tell what the
UX will look like in the end.
They couldn’t get their whole balance in cash I’m sure. But the Fed is the one that handles retiring old paper currency and giving banks fresh currency to give to ATMs and tellers, and I doubt the inflows and outflows are perfectly even for each bank.
There are schemes for this, but it requires much more than just a hash. You need not only asymmetric cryptography, but some sort of Zero Knowledge Proof if you don’t want to be able to identify the person who voted.
Sure, but approximately zero of the actual crypto space/hype was built around facilitating this kind of thing. In fact for that use case, it would’ve been better if Bitcoin never got nearly as big as it has (since that lead to much more government scrutiny, all over the world). Ideally it would’ve gotten large enough that there were enough reputable-ish exchanges that you could move fiat in and out, and then stopped there. Like some sort of digital Hawala.
The Fed has had a wire service (Fedwire) for banks, allowing them to transfer their balances on the Fed’s balance sheet to another bank during settlement, since before the dollar moved off the gold standard. It was initially done with literal telegraphs - not sure at what point it became digital.
It obviously has no pseudo anonymity, is literally the least democratized banking system in existence, and is subject to the government’s whims in a whole host of ways. But it is a digital ledger of massive sums of real dollars (the banks can ask for it in cash if need be), and you couldn’t really steal the money even if you managed to create an unauthorized transfer on some bank’s master account.
Actually, maybe 1 hour downtime for ~ the whole internet every month is a public good provided by Cloudflare. For everyone that doesn’t get paged, that is.
Look at it a user (or even operator) of one individual service that isn’t redundant or safety critical: if choice A has 1/2 the downtime of choice B, you can’t justify choosing choice B by virtue of choice A’s instability.
Even if Oracle evaporated and their contemporary ZFS source became unencumbered, I doubt OpenZFS would want to try and merge significantly parts. They already have their own encryption implementation for example.
It could make it worse. IP from companies that got chopped up and sold for parts can be a nightmare. You may have to do deals with multiple parties, and it can be unclear who owns what (even to the potential owners themselves).