Veserv

14 ms·

211.
by Veserv 10mo ago
Because that is a poor characterization of the problem. It just has a in-flight message/queue limit like basically every other communication protocol. You can only buffer so many messages and space for responses until you run out of sp
212.
by Veserv 10mo ago
No, you should run every program with only the privileges it needs. The very concept of running your programs with all your privileges as a user by default is wrong-headed to begin with. To strain the "user" model you should have
213.
by Veserv 10mo ago
Introspection windows from a interrupting context are a neat technique. You can use it to implement “atomic transaction” guarantees for the interruptee as long as you control all potential interrupters. You can also implement “non-interrupt
214.
by Veserv 10mo ago
BDHS seems strictly less powerful than a time travel debugger. You can just set a hardware breakpoint and run backwards until the value is set. Why not just do proper time travel? Is that absent for Javascript?
215.
by Veserv 10mo ago
perf is a sampling profiler, not a function tracing profiler, so that fails the criteria I presented. I used FunctionTrace as a example and evidence for my position that tracing Python is low overhead with proper design to bypass claims lik
216.
by Veserv 10mo ago
It does not, those are just very inefficient tracing profilers. You can literally trace C programs in 10-30% overhead. For Python you should only accept low single-digit overhead on average with 10% overhead only in degenerate cases with la
217.
by Veserv 10mo ago
Why even bother with sampling profilers in Python? You can do full function traces for literally all of your code in production at ~1-10% overhead with efficient instrumentation.
218.
by Veserv 10mo ago
Except that the medical system already does that for various types of common cancer screening such as breast cancer. It is frequently detected extremely early when it is medically insignificant and patients may be recommended to just wait
219.
by Veserv 10mo ago
Your response is a non-sequitur. The original statement was about intentionally not detecting cancer. You are talking about whether the cancer is medically necessary to treat. You are just assuming that all cancer must be treated if detecte
220.
by Veserv 10mo ago
To use the example provided by the anti-Monsanto upthread poster as a example of Monsanto being underhanded: https://en.wikipedia.org/wiki/Bowman_v._Monsanto_Co 1. Bowman buys Monsanto soybeans as seeds agreeing to not
221.
by Veserv 10mo ago
I am actually not talking about the lack of fat pointers. That is almost entirely orthogonal to my point. I am talking about the fact that what would be the syntax for passing a array by value was repurposed for automatically decaying into
222.
by Veserv 10mo ago
Pointer to array is not only type-safe, it is also objectively correct and should have always been the syntax used when passing in the address of a known, fixed size array. This is all a artifact of C automatically decaying arrays to pointe
223.
by Veserv 11mo ago
Client intent is distinct from server interpretation . Distinguishing these is important when defining protocols/interfaces. A client can blindly PUT a endpoint that does not support PUT, only GET. In the cold connection case where
224.
by Veserv 11mo ago
You clearly do not understand protocol/interface design. The behavior and constraints of a generic interface is a lower bound on the behavior and upper bound on the assumable constraints by all direct participants when handled in gener
225.
by Veserv 11mo ago
> POST requests by design are neither safe not idempotent. Outright wrong. You are allowed to handle POST requests in a safe and idempotent way. In fact, the existing usage of POST to query, the literal impetus for this proposal, has exa
226.
by Veserv 11mo ago
No, I was referencing the example in the article in literally the very first section showing and explaining how POST endpoints are used for fetching data when GET endpoints are too limited. This is literally their motivating impetus for the
227.
by Veserv 11mo ago
That is exactly my point. There is no reason to syntactically distinguish what is semantically non-distinguishable. The interpretation of a request is up to the server. There is no reason for the client to syntactically distinguish that the
228.
by Veserv 11mo ago
The existing mechanism to get QUERY semantics is a POST that encodes the “fetch parameters” in the body and the response contains the fetched values. You then out-of-band document that this specific use of a fetching POST is idempotent. Thi
229.
by Veserv 11mo ago
The problem is that they are not enforced. You can already have GET requests that modify state even though they are not supposed to. What you are actually doing when making a specific kind of request is assuming the actual properties match
230.
by Veserv 11mo ago
Thank you for benchmarking. 2.5x slower than what they were replacing. Demanding evidence for claims strikes again.
231.
by Veserv 11mo ago
Says it is fast, but presents zero benchmarks to demonstrate it is actually fast or even “faster”. It is shameful to make up adjectives just to sound cool.
232.
by Veserv 11mo ago
It is fairly straightforward to implement QUIC transport at ~100 Gb/s per core without encryption which is comparable or better than TCP. With encryption, every protocol will bottleneck on the encryption and only get a mere 40-50 Gb&#x
233.
by Veserv 11mo ago
That is because providing a reliable stream over a stateful connection is actually about a half-dozen layers of abstraction. TCP couples them all in a large monolithic, tangled mess. QUIC, despite being a little more complex, has the layers
234.
by Veserv 11mo ago
Your argument is lacking nuance, declaring that the criticism being levied here must be a simple binary. The specific error they are criticizing is extremely egregious, akin to builder declaring a house without a roof complete. “failing and
235.
by Veserv 11mo ago
The original loop is: while (time() != timeout) {;} The fixed loop is: while (time() < timeout) {;}
236.
by Veserv 11mo ago
Electricity is cheap compared to GPU capital costs and depreciation. Intermittent usage is only cost efficient with capital that cheaply buffers energy either generically like batteries or specifically like heating up your smelters. It is n
237.
by Veserv 11mo ago
The cameras actually do not even meet minimum vision requirements required to hold a license in California and most other states. Here is one of my posts with a detailed breakdown and analysis: https://news.ycombinator.com/i
238.
by Veserv 11mo ago
You do want to offload crypto to dedicated hardware otherwise your transport will get stuck at a paltry 40-50 Gb/s per core. However, you do not need more than block decryption; you can leave all of the crypto protocol management in us
239.
by Veserv 11mo ago
The problem with QUIC for these kinds of problems is that it is really multiple protocols stacked in a trenchcoat with no way to get at the individual layers. QUIC has a connection setup protocol, a stream reconstruction protocol, a stream
240.
by Veserv 11mo ago
Mine. I implemented it myself. Not fully standards compliant since I skipped some irrelevant details like bidirectional streams when I can just make a pair of unidirectional streams, but handles all of the core connection setup and transpor

More ›