Contribute = Human ideas, testing, review etc.
The monkey part of writing code by hand = obsolete.
Do you still write code without and IDE? you remember all the programming language words? everything? you use stackoverflow? it's called evolution, btw:
AI full disclosure
This software is developed with strong assistance from Cursor, Grok 4.5, GPT 5.6, and Claude Fable 5, with humans leading the ideas, testing, and debugging. We say this openly because it shaped how the project was built. If you are not happy with AI-developed code, this software is not for you. The acknowledgement below is equally important: this would not exist without llama.cpp and GGML, largely written by hand.
Let’s distinguish a bit. There are political appointees (Trump’s government employees as you say) who are mostly upper management, and there are career civil servants (all the government scientists are under this category) who have a strong culture of apolitical dedication to the mission of their agency and to the American people and Constitution, regardless of who the current president is. And in the DOE labs in particular most (not all) of the scientists are actually employed as government contractors, but they have a similar non-partisan ethos.
That doesn’t necessarily mean there’s no need to be concerned with potential impact of policy and priority changes from the administration, but it does temper the threat model because the government employees you’re considering trusting have given oaths of office to protect and defend the Constitution.
> and there are career civil servants (all the government scientists are under this category)
US national lab scientists are not even civil servants. The labs themselves are run by a corporation under contract to the DOE and the scientists work for that corp. The managing corporation changes from time to time and the scientists transparently start working for whatever assumes the replacement. The land, the hardware, the buildings and any physical products are owned by the US gov't. To a very large extent, the intellectual output is set free to the world in the form of papers, presentations and to some small extent (eg compared to CERN) in the form of software.
Right, I did specifically say that most of the DOE scientists are contractors, but I concede the phrase “government scientist” is a bit ambiguous. I appreciate the extra detail you added. I think the distinction between political appointee and scientist/researcher stands.
As an added complication, some of the DOE labs do have civil servant scientists, for example National Energy Technology Lab and National Renewable Energy Lab are like 50/50 civil servants and contractors. And most of the funding arm of DOE are career civil servants. LANL, Sandia, Livermore, Argonne are all staffed by contractors
> I think the distinction between political appointee and scientist/researcher stands.
I agree with this.
I'm a civil servant and I know (personally; my work is nowhere near the labs) a number of people who work or have worked in that weird contracting DOE/DOD structure that includes the labs.
The difference I've seen is far more from the nature of work rather than the employment details.
Your naivete is refreshing, but not particularly useful.
Your senators and house reps are the beneficiary of various forms of largesse from political donors.
"Billionaire ** and her *** ** *** are among the most prolific megadonors in modern American political history,
funneling hundreds of millions of dollars overwhelmingly to ***, ****"
please enumerate the civil wars over the decades Nix has been around. It is insane to discourage someone from using a good piece of battle-tested software because you personally have opinions about their community.
I can't think of an outcome that would be more odious to Steve Tuck and Brian Cantrill. Brian in particular still talks about the soul-crushing experience of Oracle's hostile takeover of Sun Microsystems.
Which many keep forgetting is that there was no one else wanting to acquire Sun, IBM did an offer that was shortly thereafter withdrawn, and that was it.
Sun would have died, everything completely lost among creditors and that would be it, end of story.
Ironically, not only are you entirely wrong on the facts themselves, but the historical record in this case is incredibly (and unusually) crisp: the Merger Proxy Statement that Sun had to file with the SEC[0] has, in accordance with Delaware law, the full narrative of the acquisition.
In the "Background of the Merger" section of that document, there is an incredibly detailed (and interesting!) story of three companies: Party A, Party B, and Oracle. (As was well-known at the time, Party A is IBM and Party B is HP.) As that narrative makes clear (and contrary to your assertion), it was Sun that rejected IBM's definitive agreement, not the other way around. You can certainly argue that IBM's acquisition of Sun would have failed to complete for other reasons (regulatory and so on) -- but your assertion that "IBM did an offer that was shortly thereafter withdrawn" is simply (and demonstrably) wrong.
Actual shout out to Oracle inexplicably moving Java forward a ton while also not strangling it with fees and suing their own customers. Wonder if there's a story of some genius, unsung internal salesman who made that happen.
Joyent was likely a part of what convinced Brian Cantrill that a new cloud machine was needed. They had their own stack running on commodity OEM hardware in their own cloud - likely a painful experience, since Brian talks a lot about how much of a difference it makes to own the complete root of trust and everything in it.
To answer these questions (or accusations?): Yes, I was at Joyent for the acquisition by Samsung -- but I also was not a founder, did not have a board seat, etc., so the involvement that I had, while substantial at some level (working with the Samsung team when they were doing their significant due diligence, for example) was also ultimately limited. My job was to make the acquisition work, not to determine the fate of the company for which I was ultimately an employee.
It's also absurd to call the sale a "sellout" -- the company was not for sale when Samsung came calling. The deal that Samsung proposed was a good and fair one, and if I HAD been on the board, I would have absolutely voted for the acquisition. (It should be said that Samsung themselves had a very high threshold to close the deal -- 97% of shares IIRC?)
And all of THAT said: while I was supportive of the acquisition by Samsung of Joyent (and worked hard to make that acquisition work), when we started Oxide, Steve and I had (and have!) zero interest in building a company to be acquired. Oxide is our life's work (and I mean that "our" broadly, as many at Oxide feel that same calling), and our objective with Oxide is to build an independent, generational company. Indeed, this Series D is all about advancing that objective!
So, I know I am late to this discussion by a week (the coding rarely stops, and I often miss big developments), but, I was at Joyent when it was acquired by Samsung, and their interest was very similar to most Joyent customers: to find a way to shrink their tumorous, ever-growing AWS bill[0]. By acquiring Joyent, they did not have to build their own cloud-software from scratch, and they did not have to Ship-of-Theseus their internal legacy infrastructure. More importantly, they also got a team that knew how to maintain and improve that software stack.
While I practically never agree with the guy, Thiel did say that "every startup is a conspiracy". Which is just another way of saying that every business is a conspiracy. The Oxide "conspiracy"[1] is to divert a chunk of the enormous economic surplus that is being captured by Amazon (and Broadcom, and others), and in the process, put some meaningful amount of that surplus in the pocket of the customer (otherwise, there is no reason to switch).
This is an incredibly ambitious goal, that cannot be achieved without upfront capital. Part of it is certainly hardware (which is getting more expensive, rapidly, and so it might make sense to buy years-worth of it), but another part is the _switching cost_ (which the _challenger/conspirator_ usually has to cover for the customer). That cost can easily be measured in the millions of dollars (Dropbox, famously, migrated off of AWS, via a client-side reupload, because moving the data from AWS to their own DCs was prohibitively expensive[2]).
Also, WW3 is slowly unfolding. The only reason energy prices are not in "brownout territory" is because (IIUC) the world's largest oil consumer is importing half as much oil from the mid-east as it used to. A few of the things that I buy, have _not_ gotten more expensive in euros, but they have gotten more expensive in dollars (by around 5% last I checked). If you need to use dollars to stockpile input-goods, now is the best time to do that, if you anticipate that the dollar will lose value over the next year.
A similar logic applies to selling a company. Amazon, in 2016, was already on the path to _massively_ improving the performance of its VMs and cloud services (via using more SSDs, building custom hardware, etc), and bare-metal performance was one of the Joyent selling points. With the resources of a company like Samsung, Joyent could also (potentially) use faster hardware, etc.
However, even under the aegis of Samsung, some (let's call them) _political asymmetries_ could not be avoided. I cannot talk about _internal_ asymmetries, but _external_ ones are already public knowledge. In particular, in 2017 or 2018, spectre and meltdown CPU-exploits hit the industry. All the major cloud providers had advance knowledge of this (and were able to mitigate via KPTI), except for Joyent (who had to work with the OpenBSD community for a few months to fix this). In those few months, if customers wanted to be completely safe, they would have had to move their instances to a different cloud. It is unclear (to me, because I am an engineer and not an accountant or account manager) if Joyent could have survived that without being part of Samsung.
And by the way, this would not have been as urgent of a problem, if Joyent was selling physical machines (like Oxide is, right now), instead of renting them out to multiple tenants. Imagine if an adversary could just spin up a VM right next to yours on the same exact machine. Even without spectre and meltdown, they could probably impact the performance and latency of your VMs indirectly, if they were willing to spend enough money. I once did this by accident (because I, foolishly, overestimated Google) on GCP, via their lambda-equivalent, and found out when they told us that those workloads were moved to a different DC. So if this is a problem for _Google_, it's a problem for everyone.
For at least the last decade, HN has consistently (but, thankfully, not exclusively) been attacking Joyent (and now Oxide), for various perceived misbehaviors[3], while frequently letting much less ambitious projects off the hook. Engineering any meaningfully new or disruptive technology is a very challenging marathon, and doing so, in business circumstances (which can only be characterized as: circumstances where the other runners are armed and always out to get you, while sometimes, the universe itself decides to send a few lightning bolts and storms in your direction) is almost impossible, without either (1) a monopoly, like MSFT and GOOG and AMZN enjoy, or (2) massive amounts of investment-cash that can only come from a very smart and very keen sugar daddy[4].
[0]: I can't recall who said this, but someone at the time said, they were tired of buying Bezos a BMW every month (via their AWS bill). Sometimes, it wasn't even an issue with the size of the bill: Amazon competes with many, many companies out there.
[1]: Based on various public statements. So basically, the Joyent conspiracy, but this time on-prem (so maybe Joyent + Fishworks = Oxide), and with fewer faulty drives (IIRC, there was a batch of drives, worth a huge amount of money, that had bad firmware, which caused their throughput to drop sporadically -- the exact details escape me, but you can see why there is a distrust of firmware written by others (also worth noting, is that this HDD vendor did not even offer to replace the faulty drives, but instead offered a marginal discount on the next order)).
[2]: Not because of any real, physical cost, but because Amazon bills you for every byte that leaves their datacenter (but not for any byte that enters).
[3]: I think it started when Joyent did not honor the "lifetime storage" promise that it made to its customers from the 2000s.
[4]: If anyone knows any wealthy heiresses that are looking to get married (or for a concubine), in exchange for financing my ambition to build an invention that is simultaneously (1) the last invention humanity will ever need, and (2) the invention that humanity needs most urgently, please hit me up. I have a sense of humor and am hung AF.
Thank you for the response. I appreciate it. I ran SmartOS in production and enjoyed it thoroughly. I am sad to see it not doing as well as I had hoped. Thank for again for the long detail
I doubt that. Oxide was founded by a bunch of ex-Sun people who have already been burned by the Oracle acquisition. If you read through what they say, their company values, and how they act, it's pretty clear their intent is to grow a sustainable long-term business and they're not looking for an exit.
We are trying to build a sustainable long-term business! It's just that you need enormous amounts of money to get there when shipping this large a product.
The idea behind VC funding generally is that you need large infusions of capital to get to the point where the business becomes sustainable long-term. The first one is the most expensive, and so on. Hardware is capital-intensive compared to SaaS, and especially so in the current environment.
Read the blog post on their series C [0]. It's not long, but the most relevant excepts are:
> So if we didn’t need to raise, why seek the capital? Well, we weren’t seeking it, really. But our investors, seeing the business take off, were eager to support it. And we, in turn, were eager to have them: they were the ones, after all, who joined us in taking a real leap when it felt like there was a lot more risk on the table.
> ...
> Our intent in starting Oxide was not to be an acquisition target but rather build a generational company; this is our life’s work, not a means to an end. With our Series C, customers don’t have to merely take our word for it: we have the capital to assure our survival into the indefinite future.
Maybe you could read that and think its complete bullshit and they're lying their asses off. Considering the people behind Oxide and their history, that's vanishingly unlikely though.
The reasonable conclusion is that they would not have raised yet more money if it wasn't due to being offered very generous terms by investors who wouldn't threaten the long-term future of the business.
It says "they've entirely derisked capital" and now ~6 months later they raised twice as much. Lying is a strong word but that post clearly wasn't accurate at the time.
They've raised a lot of money and there will be pressure for an exit sooner rather than later.
You can be cashflow positive and still benefit from having a larger pool of cash to throw around, particularly in any situation involving hardware manufacturing.
If you tell your investors "our limiting factor is how fast we can spend to deliver on additional requirements for these new customers", then it can both be true that you're not going to miss payroll for 5 years no matter what happens tomorrow and more cash would be beneficial.
Look at how much the components cost 6 months ago and now. That may explain why some calculations shifted considerably. It may be an act of keeping up with the market and having some reserve.
Depends on the VC. Some VC's are happy to own great businesses, even long term. Most are definitely vultures after a quick turn around. Mostly it has to do with where the VC gets their funding. Most VC's get their funding from offering a fund with a 2-5 year time-frame. Some are 10 yr funds, and some are long-term funds or are funded by a family office or two, which can be happy with great businesses long term.
It makes sense for Broadcom to remove that avenue of escape, and it makes sense for Oxide's investors to charge a premium to Broadcom, and materialize their returns.
The customers will have to deal with it, of course. At least they bought physical systems instead of renting them, so they can use them until they're obsolete.
Is there anything they're doing that can't be replicated by hypervisor/management software on commodity x86 servers? Seems like their "secret sauce" is a software stack that "just works" more than any actual special feature of the hardware.
I feel like Broadcom with its VMWare acquisition could easily take these guys out if they wanted to (or for that matter, any OEM that has a line of servers + network & storage hardware). They don't, most likely because there isn't actually enough profit to be made there (Oxide having to raise money multiple times might be a hint).
Managing a single commodity device is pretty simple. Could even be a shell script with a few IPMI commands.
Managing 100s of devices from a mix of vendors is possible becomes itself a massive ball of crap to stick all the pieces together.
Then add firmware management because now there is a plethora of firmware updates to worry about.
And then dealing with networking discovery & orchestration for such setups is an added horror few even try to visualize.
Then abstract all these differences away so one can provision two different vendor’s servers connected to two different vendor’s managed switches in different racks to a new VLAN. And do it with SR-IOV while you’re at it…
Oh, I forgot shared storage… details, details…
Commodity computing is the modern day Tower of Babel.
Yes, it can be done much simpler if one treats all switches as unmanaged, all storage as local, and all networking as flat. That’s just not acceptable for a lot of use cases though…
Good question. Can’t eliminate the BIOS/UEFI on commodity systems. Can’t remove/cut down the BMC. Can’t plumb the hardware root of trust into the OS and VMs. Can’t do dynamic rack-level power capping (future roadmap). There’s a whole bunch of the software stack that only works because the hardware and software were designed together.
Oxide exists in part because commodity systems don’t work for building a cloud at scale (Joyent). Similarly, AWS, GCP, and Azure don’t use commodity systems, they use hardware that was designed to work together with their software, Nitro being a prime example.
> Is there anything they're doing that can't be replicated by hypervisor/management software on commodity x86 servers? Seems like their "secret sauce" is a software stack that "just works" more than any actual special feature of the hardware.
There's a reason Apple is consistently one of the top 5 most valuable companies. It isn't because their hardware does anything that can't be done on "commodity" hardware, its that they built a software stack that "just works" and part of that was tight coupling to the hardware.
Their machines are x86 but they've rearchitected basically everything else in the pursuit of a cohesive and integrated machine, they don't even have a BIOS. The secret sauce is having full control of the software stack, and as close to full control of the firmware as is possible on x86.
Yes, custom hardware is a significant part of Oxide. You have to build your own to do that stuff, and that’s why they did. I alluded to some of the things upthread.
I found out about this round from this thread, just like everybody else, but
> Oxide having to raise money multiple times might be a hint
That’s not the only reason to raise a round, by far, especially when you, you know, are building custom hardware. It isn’t a SaaS business.
> Is there anything they're doing that can't be replicated by hypervisor/management software on commodity x86 servers?
It was technically possible with (e.g.) OpenStack for years (decades?) before Oxide ever existing, and yet even with such a solution being around, some folks still went with Oxide. (Or, depending on the scale you want to talk about: Proxmox, XCP-ng.)
Posting a link to AI slop about a mess of AI vibecode is not contributing.