Always_Anon

It's basically Sun Microsystems but RIR (rewrite in Rust). The incumbents will eventually release similar products and will eat their lunch.

Too little to late unfortunately. Many have written btrfs off as a loss and are looking at alternatives. bcachefs is hopefully going to be the next step for file systems on Linux.

Your webpage is an ocean of marketing fluff and buzzwords. It's not clear that you have a product that competes with Oxide. It's not even clear how you're different than Dell or HP.

No they're not unless I'm mistaken. They're not writing the firmware that runs on the NVMe drives, nor the NICs (they're not even writing the drivers for some of the NICs), etc.

There's a line in the sand that you must cross when it comes to understanding the true nature of the componentry that you're using. At the end of the day, your AMD CPUs may be lying to you, to all of us, but we just don't know it yet.

Interesting enough I also ran into something somewhat related with Dell that they were not able to resolve so they ended up working in a replacement from another vendor.

Nonetheless, it is quite interesting what you've built, but as the end user I'm not quote convinced that it matters. Sure you can claim it reduces attack vectors and such but we'll still see Dells and IBMs in the most restricted and highest security postured sites in the world. Think DoD and such. Core/libreboot with RoT will get me through compliance the same.

The software management plane y'all built is the headlining feature IMHO, not so much what happens behind the scenes that the vast majority of the time will not have a fatal catastrophic upstream effect.

>There are plenty of valid criticisms of Oxide -- but that we don't understand our system simply isn't one of them.

That's not what I said. There's a line in the sand that you must cross when it comes to understanding the true nature of the componentry that you're using. At the end of the day, your AMD CPUs may be lying to you, to all of us, but we just don't know it yet.

And it'll be tough to provide this because Oxide does not have a bare metal instance type (VMs only) and the hypervisor is running on illumos.

Oxides biggest selling point is the API, which can be manipulated with Terraform. I see no SoftIron Terraform plugin.

I used to run over 150,000 nodes and I agree with me.

Seems risky considering how small of a developer pool actively works on illumos/Solaris. The code is most definitely well engineered and correct, but there are huge teams all around the world deploying on huge pools of Linux compute that have contributed back to Linux.

Exactly right, Apple is actually a poor example. Watch enough Louis Rossmann and you'll grasp just how bad some of their shit can be.

It's ironic coming from a company who's CTO has harped about containers on bare metal for years. Maybe a large swath only need to deploy VMs, but the future will most definitely involve bare metal for many use cases, and oddly Oxide doesn't support that currently.

I've been a Dell customer for decades at this rate and I know for a fact it's true.

I've had support tickets open for all kinda of weird firmware, hardware, etc. bugs and they've been well resolved, even if it meant Dell just replaced the part with something comparable (NIC swap).

>Dell doesn't know how to fix things like that because they don't design and engineer the systems they sell.

Of course they do. That's like saying Oxide doesn't know how to fix stuff because they don't design the CPU, NVMe, DIMMs, etc. Oxide is still going to vendors for these things.

Oxide also has various hardware components from AMD, Intel, Samsung, etc. They are not manufacturing every component.

>I'm not speaking hypothetically.

Neither am I.

>If you hit a "zero-day" bug that Dell has never seen it's going to take time.

If you hit a "zero-day" bug that Oxide has never seen it's going to take time.

>And somehow every large customer finds bugs that Dell certification didn't.

Yes, happens. And I'm sure the exact same will happen with Oxide, so it's not a differentiator.

>And you'll be down for weeks or months while they do it.

Off by a few orders of magnitude. Dell on-site SLA with pre-purchased spares was about 6 hours.

With Oxide, you'd be lucky to get same day service.

>Sure you can, but then who will diagnose and fix your hardware/OS interaction problems when you have parts from five vendors in the mix?

Dell is a single vendor that will diagnose and fix all of your hardware issues.

With Oxide you're locked into what looks like a Solaris derivative OS running on the metal and you're only allowed to provision VMs which is a huge disadvantage.

I run a fleet of over 30,000 nodes in three continents and the majority is Flatcar Linux running on bare metal. Also have a decent amount of RHEL running for specific apps. We can pick and choose our bare metal OS which is something you cannot do with Oxide. That's a tough pill to swallow.

Dell now ships with OpenBMC iDRACs and such. How does what you mention differ from the RoT in Dells?

https://www.dell.com/en-us/blog/hardware-root-trust/

>Right, who wants or benefits from open source firmware anyway.

Their competition has open source firmware as well:

https://www.dell.com/en-us/blog/enabling-open-embedded-syste...

Because they can't. Their product currently has zero GPU compute.

A lot of your competition has verifiable open source software as well: https://www.dell.com/en-us/blog/enabling-open-embedded-syste...

>They lost billions in Iraq

You're absolutely correct, but I just want to emphasize the scale: trillion. That's over a thousand billions. It's an amount that's so huge it's truly hard to comprehend and visualize.

https://en.m.wikipedia.org/wiki/Financial_cost_of_the_Iraq_W...

According to practically any and every translation dictionary made in the last century, no, it is not.

>Allowlist/blocklist is more clear and accurate tho?

No it's not, not at all. Is "blocklist" a list of file system blocks? Bitcoin or other crypro blocks?

As someone who speaks English as a second language, the first time I read "whitelist/blacklist", I simply looked them up in a translation dictionary and immediately understood what they mean. Those are actual words with definitions spanning centuries.

>The software community loves to complain about this stuff like the change from master to main branch but I always get the sense that people just liked to complain rather than any meaningful objection.

Yes we love to complain, but there were many meaningful objections that were ignored. There was a reddit outage that occurred due to the madness around "inclusive language" and removing the word "master": https://www.reddit.com/r/RedditEng/comments/11xx5o0/you_brok...

How are gas prices subsidized? I'm asking in good faith because I truly don't know.

I don't understand your shock at the question? The military most definitely does not just let anyone in.

No children of felons for one. No children of illegal substance (drugs) users is another example. Parents must be literate to join the military is another, etc.

>It seems like they aren’t doing fine, actually.

Not to unlimited growth capitalist, no. Culturally and as a people they're doing fine.

>Meanwhile those nations that embrace newcomers of all kinds are doing significantly better.

No they are not. Japan is perfectly fine without trucks of peace, grenade attacks, and gang assaults on women.

Of course! A large portion of it went into the market, with great returns. Maxed out 401k, IRA, paid off my school loans, etc. Pandemic time was sweet financially, honestly.

I took the opposite approach and used the pandemic as a great way to save. No eating out, no going out for drinks, zero travel... I saved a lot, and paid a lot of debt down. I'm continuing some of these trends still. I do not eat out as much as I did pre-pandemic, I haven't traveled much, etc.

As far as JPMC goes, insider threats are the biggest threats they face. It makes sense from a security/compliance standpoint to "spy" on your employees, to a degree. Imagine if you could spy on your biggest enemy. You'd be dumb not to.

There are limits to everything, but for finservs, there's a reason why they do these things.

Source: I am/was infosec at JPMC and other large finservs.