bcantrill

7 ms·

61.
by bcantrill 10mo ago
Please DM me and I'll let you know if there's constructive feedback to be provided.
62.
by bcantrill 10mo ago
I understand your disappointment; we are very explicit about why we provide so little feedback.[0] I disagree that it's indecent; to the contrary, we allow anyone to shoot their shot, with the guarantee that they will be thoughtfully
63.
by bcantrill 10mo ago
Your materials were absolutely read (and indeed, RFD 576 makes clear that LLMs are not a substitute for reading materials). If you have writing samples that were external links, I can't guarantee that they were clicked through though:
64.
by bcantrill 10mo ago
I am really surprised that people are surprised by this, and honestly the reference was so casual in the RFD because it's probably the way that I use LLMs the most (so very much coming from my own personal experience). I will add a fo
65.
by bcantrill 10mo ago
The em-dash alone is not an LLM-reveal -- it's how the em-dash is used to pace a sentence. In my experience, with an LLM, em-dashes are used to even pacing; for humans (and certainly, for me!), the em-dash is used to deliberately chang
66.
by bcantrill 10mo ago
Note that I made that claim in 2011. I had tried to research this a bit for the brief period of time that I was at Oracle, and really couldn't find anything (other than the Ellison Medical Foundation). That said, I think my essential
67.
by bcantrill 11mo ago
Ha ha -- but maybe we can finally find the mysterious headwaters of ta?[0] [0] https://www.youtube.com/watch?v=8Gp-RXCLO2M&t=3500s
68.
by bcantrill 11mo ago
Has anyone done a piece a Second System Syndrome and IPv6? (Surely?)
69.
by bcantrill 11mo ago
Indeed. One of the interesting side effects of being a remote company that records everything[0] is that we have the instant where the "1000 piece puzzle just clicks together" recorded, and it's honestly pretty wild. In this
70.
Futurelock: A subtle risk in async Rust(rfd.shared.oxide.computer)
449 points by bcantrill 11mo ago|245 comments
71.
by bcantrill 11mo ago
I (obviously) don't agree with your characterization, but given that I don't work for you (and won't) and that you don't work for me (and won't) can we just let a decades-old disagreement live in the past? Not that
72.
by bcantrill 11mo ago
Oh brother, this again. To bystanders wondering what the hell this is about, it's actually about two things, the most recent of which was over a decade ago. The first thing is a regrettable quip of mine on Usenet (RIP) from October 29,
73.
by bcantrill 1y ago
Bingo: forcing UEFI and D-Bus to breed in captivity is antithetical to our approach of holistic boot.[0][1] [0] https://rfd.shared.oxide.computer/rfd/0241 [1] https://www.osfc.io/2022/talks/i-
74.
by bcantrill 1y ago
I don't disagree that Sun was a company run aground by engineers -- though I certainly like to think of myself as one of the engineers trying to navigate us around the rocky shoals! For whatever it's worth, I broadly stand by my
75.
by bcantrill 1y ago
Noted!
76.
by bcantrill 1y ago
I am unspeakably biased, but I think that this talk is extraordinary -- one of the best talks (or maybe the best talk?) on the challenges of large systems software that I have ever seen. I should really update the blog entry, but note that
77.
by bcantrill 1y ago
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 certa
78.
Systems Software in the Large(oxide.computer)
7 points by bcantrill 1y ago|0 comments
79.
by bcantrill 1y ago
It took all of my self-control to not put "plan" in quotes in the submission: this is a sloppy, sorry excuse for a plan that involves somehow magically extracting a $40B bailout from Intel's customers, which Barrett confusing
80.
Former Intel CEO Craig Barrett's Plan to Save Intel(finance.yahoo.com)
8 points by bcantrill 1y ago|2 comments
81.
by bcantrill 1y ago
So (foolishly?) I had never bothered to check Glassdoor, because we have been so upfront about our compensation.[0] But apparently that was a mistake! If it needs to be said, the Glassdoor numbers are comically wrong -- and in fact the hi
82.
by bcantrill 1y ago
Well, good news: we have one of those too![0] [0] https://oxide.computer/blog/hubris-and-humility
83.
by bcantrill 1y ago
This "job" that you speak of, that you are so good at. Are you... at it now?
84.
by bcantrill 1y ago
Check out Oxide and Friends[0]! We've been doing it for several years now, and it's a much more flexible format that allows the team to be heard in its own voice -- and allows us to weigh in on whatever's on our collective mi
85.
by bcantrill 1y ago
Because VCs need to have a way to sell their shares within the (limited) lifetime of their fund.
86.
by bcantrill 1y ago
We didn't use anything from OCP. When we first started the company, we thought we might use the enclosure (and considered ourselves "OCP inspired"), but there ended up being little value in doing so (and there was a clear cos
87.
by bcantrill 1y ago
Just because it's hopelessly on-brand for us to offer up a podcast episode for everything, you may also be interested in our Oxide and Friends episode on RFDs with our colleagues Robert Mustacchi, David Crespo, Ben Leonard, and Augustu
88.
Attabotics CEO on devastating week that brought bankruptcy(retailtechinnovationhub.com)
16 points by bcantrill 1y ago|7 comments
89.
by bcantrill 1y ago
Long before Oracle killed it, Sun fumbled it, sadly. The failure of SunRay to live up to its potential -- and it clearly had tremendous potential -- was Sun at its most frustrating: the company tended to became disinterested in things at
90.
by bcantrill 1y ago
This is hot! I -- like maybe everyone at Sun in the late 1990s and early 2000s? -- had a soft spot for SunRay. The original SunRay demo from Duane Northcutt to the Solaris Kernel Group in February 1999 (when it was a Sun Labs project code-

More ›