Like that Cloudflare outage from the other day? In any case, I'm sure there's good reason to believe that, as Rust gains popularity, there totally won't be proportionally more high profile issues in stuff made with it.
You could write a lot of bugs in Rust. Or in any memory-safe language. Just not some bugs. It's just that starting a non-toy project using a non-safe language today is really in the "you could, but didn't stop think if you should" category.
Fair enough, and I do appreciate Rust's contributions to the spectrum of programming language considerations. Personally I'd like to become a Zig guy, though.
There's also Fil-C BTW, and in normal C++ there are GCC or Clang (I forget which) extensions for detecting threading issues, even good old Valgrind is under-appreciated and under-used. In general one wants to adopt best practices and be proactive, rather than relying on the language to solve all problems (of course).
Someone engaging this mode by error or stupidity, and then causing an accident makes me think some things should remain lock behind some "I know what I am doing" barrier, which the subject of the original link seem to not have scaled above, as there is a simple way to brute force the electronic break, no expensive tools needed.
As far as I can tell it's one of their most significant features, and certainly one of its most capital intensive. And I don't know how many startups land institutions like INL as their launching customer, and enough other big enterprise leads to warrant their follow up investment.
If you remove that component from their value prop, they're not that much different from Dell.
Just a quick point of clarification that while our boot architecture is very important (e.g., a service processor in lieu of a BMC, the elimination of UEFI entirely, etc.), we are quite a bit different from Dell beyond that. There are certainly many hardware-level differentiators (e.g. DC busbar-based design, blindmated networking, built-in switch, etc.) but the big differentiator is really what these things allow: entirely integrated software. The Oxide rack comes with all of the software to run elastic infrastructure (that is, the distributed system that comprises the control plane), including switch software, storage software, etc. And then (critically!) the capacity to update all of this.[0]
All of it is a far cry from the offerings of Dell/HPE/Supermicro, which rely on others to provide the software that turns the hardware into real infrastructure.
Right, my apologies for downplaying it. That you control both the hardware and the software through the entire stack has tremendous benefit, especially for this type of customer. My point was if you as a customer don't value that aspect of Oxide's pitch, which you obviously are much better at fully conveying, then you'd be seriously considering Dell/HPE/Supermicro as well.
For what it's worth the last time I had to procure a small cluster the offer Dell made was ridiculously overpriced, didn't meet the specifications I asked for, and the whole experience didn't inspire confidence in the software they were pitching either. We were a small underfunded startup so we were never gonna drop 200k on that storage solution (0.5PB HDD + ~80TB SSD), but if we did have that kind of budget we probably would have gone with one of the smaller but more focused parties there instead like maybe TrueNAS, I bet there's a beautiful market for Oxide as well in that segment.
At the bottom of the page, it reads "By using this site, you agree to be bound by the CDP Terms of Service and Global Privacy Policy."
Shouldn't that be at the top? If you want me to agree to a EULA no one would read, at least make a show as if you expect people to read it, don't hide it in a disused lavatory with a sign on the door saying 'Beware of the Leopard'.
That said, I am not sure those numbers are true. I am in California (PG&E with East Bay community generation), and my TOU rates are much lower than those.
There are 3 different components of PG&E electricity bills, which makes the bill difficult to read. I am also in PG&E East Bay community generation, and when I look at all components, it’s:
Minimum Delivery Charge (what’s paid monthly, which is largely irrelevant, before annual true-up of NEM charges): $11.69/month
Actual charges, billed annually, per kWh:
Peak NEM charge: $.62277
Off-Peak NEM charges: $.31026
Plus 3-20% extra (depending on the month) in “non-bypassable charges” (I haven’t figured out where these numbers come from), then a 7.5% local utility tax.
Those rates do get a little lower in the winter (.30 to .48), and of course the very high rates benefit me when I generate more energy than I consume (which only happens when I’m on vacation). But the marginal all-in costs are just very high.
Are you actually able to compute that? With PG&E + MCE because of the way they back off the PG&E generation charges, the actual per-time period rates are not disclosed.
I can solve for them with three equations for three unknowns... but since they change the rates quarterly by the time I know what my exact rates were they have changed.
Employers already have to publish H1-B applications, including wages (but not personal information of the applicants, which would be a very bad idea to publish).
This is not just an accent, it’s extremely poor speaking and comprehension of English itself. Communication is painfully slow and you have to change the way you talk and your vocabulary as well.
After a week of that, interviewing someone who actually knows English feels like turbo charged discussion. I get through interview questions in half the time, with literally 10x more information communicated.
I'd argue this is true for every corporation that didn't need that regulationas a moat (some have found they could use those regulations to their advantage and block competitors, mostly due to implementation costs)
reply