Viewing profile — cross
cross
HN member- Joined
- Thu, Feb 07, 2019, 10:04 PM UTC
- HN karma
- 69
- Public activity
- 18 items
- HN profile
- View on Hacker News ↗
About cross
Recent public activity
-
comment
Comment #48213428
Xoogler here. This hits hard; right on the kidney. That is a huge problem at Google: "we're google; we know what you want and need better than you do." That and an unshakable confi…
-
comment
Comment #43867859
We don't. When I'm there, I see it addressed as a communal responsibility. Not to be facetious, but the way it's done is a bit of a microcosm of Oxide itself: everyone just chips i…
- comment
-
comment
Comment #42984002
Linux won in large part because it was in the right place, at the right time: freely available, and rapidly improving in functionality and utility, and it ran on hardware people ha…
- comment
-
comment
Comment #42080064
The first attempt appears to try and transfer ownership of the allocated memory from the Vec to C, so my first question is, why not allocate the returned memory using libc::malloc?…
-
comment
Comment #42079837
> If you've been doing C for five decades, it's a shame not to have noticed that it's totally fine to pass a NULL pointer to free(). Or that calling one's FFI function inside of an…
-
comment
Comment #39456328
I'm not Bryan, obviously, but part of the answer here is that 100 servers running at 100% capacity is an absolute upper bound, but most of the time you're nowhere near that. Most o…
-
comment
Comment #39181415
This is less of an issue for us at Oxide, since we control the hardware (and it is all modern hardware; just a relatively small subset of what exists out there). Part of Sun's issu…
-
comment
Comment #37456167
Sorry, I thought my last message did give suggestions for things to compare?
-
comment
Comment #37447606
Well, you're free to study both in detail and draw your own conclusions. But the UART driver in both is pretty uninteresting, and I suspect whatever conclusions one may draw from c…
-
comment
Comment #37442278
> rxv6, at least its userland, still seems to be written in C, which (correct me if i’m wrong) must be creating a lot of pressure on the rust kernel along the lines of ‘unsafe’ and…
-
comment
Comment #37441409
xv6 was originally written for 32-bit x86; the RISC-V port is a relatively recent development. See e.g. https://github.com/mit-pdos/xv6-public for some of the earlier history. rxv6…
-
comment
Comment #36880794
Probably true. Porting rxv64 to RISC-V probably wouldn't be that big of a lift, honestly.
-
comment
Comment #36024957
In a sense yes, but also no. Plan 9 was built with the observation that high-resolution, bitmapped graphics displays were ubiquitous, and there was little motivation to keep the da…
-
comment
Comment #36024923
Yeah, it's really more just a shell at the moment.
-
comment
Comment #29542813
So is sed.
-
comment
Comment #28168400
PL/1 definitely predates C.