Viewing profile — psarna
psarna
HN member- Joined
- Wed, Sep 11, 2019, 3:04 PM UTC
- HN karma
- 148
- Public activity
- 30 items
- HN profile
- View on Hacker News ↗
About psarna
No profile information was provided.
Recent public activity
-
comment
Comment #48835972
single executable with its own frontend is the way; I followed the pattern with https://worb.cloud . Nice for users but also extremely easy to have a short debugging feedback loop
- story
- story
- story
- story
-
comment
Comment #46695820
related: https://printed.games/gates/
- story
- story
- story
- story
- story
- story
- story
- story
- story
-
comment
Comment #34520048
First of all, let me start by reiterating the first sentence from the bottomless repo - it's work in heavy progress (and we'll move it under the sqld/ repo soon, to keep everything…
- story
- story
- story
-
comment
Comment #30003882
In case somebody stumbles upon this old thread, here's the recording of the meetup: https://youtu.be/pgzjPeIQ3Us
-
comment
Comment #29947691
maybe_yield may or may not be the right solution here, but I think it may be useful in general - e.g. when you have long I/O-less computations. In such a case, I'd like to be able …
-
comment
Comment #29923178
Now that I think of it, it would probably be beneficial even outside of the unconstrained scope, especially for long computations. When iterating over millions of elements, it woul…
-
comment
Comment #29917196
wrt. preemption - in Seastar we have maybe_yield(), which gives up the cpu, but only if the task quota (more or less a semantic equivalent for Tokio's budget) has passed. Wouldn't …
-
comment
Comment #29916985
Indeed - 1ms was a nice round number, but it was also not that far from the real, sub-1ms number. But note that by "latency" here I mean not only the round trip, but the total meas…
-
comment
Comment #29916900
> In my experience so far, highly proficient Cpp programmers tend to find rust constraints overly restrictive For me it's the exact opposite - I find Rust righteously restrictive e…