Viewing profile — quotemstr
quotemstr
HN member- Joined
- Fri, Mar 18, 2011, 11:31 AM UTC
- HN karma
- 8,588
- Public activity
- 4,495 items
- HN profile
- View on Hacker News ↗
About quotemstr
Recent public activity
-
comment
Comment #49215607
Just add async_uuid to your IDL locally and rerun MIDL. The server doesn't know or care that it's being called asynchronously. It's a pure client thing. If you're calling an IFoo i…
-
comment
Comment #49212135
And COM enforces lifecycle rules, transparent remoting, uniform activation (constructors basically), security primitives, marshalling, transparent async calls (yes, you can call an…
-
comment
Comment #49201364
> less knowledge, more intelligence People produce such models by over-RL-ing smaller models on math and coding tasks. I've found the results capable of neither innovative work nor…
-
comment
Comment #49184675
I wish that when people posted a performance win, they would include a theory explaining it. Unexpected speedups are usually noise, bugs, or harness issues. No program is faster du…
- comment
-
comment
Comment #49170992
To be fair, this description omits a huge part of the modern terminal interface surface.
-
comment
Comment #49150204
One advantage to using pthread is the ability to call pthread_setname_np to name threads and thereby make debugging easier. Granted, you can call it with std::thread by using std::…
-
comment
Comment #49150195
https://scholar.google.com/scholar?hl=en&as_sdt=0%2C10&q=%22...
-
comment
Comment #49150171
Excellent use of Ragel to generate fast state machines. Everyone should check it out: https://www.colm.net/open-source/ragel/ The author of shitty encoded the whole terminal state …
-
comment
Comment #49136403
It's confusing how they want a custom protocol that seems to be converging from JSON-RPC, just spelled differently. They should just use JSON-RPC. In any case, it'd essential to re…
-
comment
Comment #49136328
Not everything has to be a "daemon". It's a bad trend in current programming zeitgeist to want to make everything into one. (sccache, no, you do NOT need a daemon to behave like cc…
-
comment
Comment #49130446
Implementation language is incidental. Rust is... fine, I guess? But I wouldn't mandate modules use it. What's important is to move PAM out of process and sandbox the process host …
-
comment
Comment #49127086
Everyone doing parallel biometric and password authentication on Linux today is either running two PAM stacks in parallel (which is meta-policy that kind of defeats the purpose of …
-
comment
Comment #49125514
PAM really needs to be ravamped and support for (among other things) running multiple stacks in par@llel added. This way you could ask for a password OR a fingerprint
- comment
-
comment
Comment #49089080
It'd look like Graal, which is a real thing you can use today.
-
comment
Comment #49088876
Classic ciphers are damn fast and small compared to PQC. If you're doing PQC anyway , doing classical cryptography at the same time has negligible cost. That makes attempts to push…
-
comment
Comment #49087825
One attack weakens HAWK, a post-quantum cryptography cipher candidate. I don't trust these PQC things one bit. I'll use them in combination with a strong clasically-resistant ciphe…
- comment
-
comment
Comment #49079784
How do their servers know I'm running a proxy, exactly?
-
comment
Comment #49079707
If I own a computer, I should be able to run whatever damn software I want on it, including software that provides a network proxy to others. (N.B. a smart TV is a computer I own.)…
-
comment
Comment #49054291
> And I also think it is totally fine to use Rust even if you could use a GC language like Go or Fil-C. The problem with choosing Rust over a GC language like the above (or a good …
-
comment
Comment #49050675
Your argument is literally that there is too much unsafe code.
-
comment
Comment #49048138
That's a lot of words to say that the problem with Rust is that people you don't like are allowed to write unsafe code.
-
comment
Comment #49044631
> It is not in scope of memory safety to make sure that logic not related to memory accesses works as you expected This logic is related to memory accesses. This is not an issue th…