codys

8 ms·

31.
by codys 9mo ago
Ya, UUID v7 has been standard for a few years now. Perhaps the author is not familiar with the terminology of RFCs and so is misinterpreting the terminology used by IETF: "Request for Comments" and "Proposed Standard" ca
32.
by codys 10mo ago
Allocators in rust are objects that implement the allocator trait. One (generally) passes the allocator object to functions that use the allocator. For example, `Vec` has `Vec::new_in(alloc: A) where A: Allocator`. And so if in your example
33.
by codys 10mo ago
One would still use `?` in rust regardless of adding context, so it would be strange for someone with rust experience to mention it. As for the example you gave: File::create("foo.txt")?; If one added context, it would be
34.
by codys 10mo ago
Rust has an RFC about some of the conventions for the Fd conversions. https://rust-lang.github.io/rfcs/3128-io-safety.html It's unfortunate they did not extend marking the OwnedFd conversions as unsafe due to the
35.
by codys 10mo ago
I can't speak to http/3 (I haven't tried to impl it), but I can say that a bare-bones http/2 is very easy to implement because it doesn't try to pretend to be prose.
36.
by codys 11mo ago
Ya, something like "table stakes" would be closer to what they mean.
37.
by codys 11mo ago
The article in CACM that presents Knuth's solution [1] also includes some criticism of Knuth's approach, and provides an alternate that uses a shell pipeline: tr -cs A-Za-z $'\n' | tr A-Z a-z | sort | u
38.
by codys 1y ago
There's also an article on another game by the same folks that's similar (but earlier) which describes some details on building it https://www.awwwards.com/summer-afternoon.html
39.
by codys 1y ago
It seems surprising to me that this kind of basic thing (does the update work on the hardware we've released) wasn't validated by Apple prior to releasing this software update. Perhaps a sign of issues in the QA process at Apple a
40.
by codys 1y ago
It is strange how folks are refusing to admit they can even _evaluate things_ in a bunch of cases. We're seeing that here, but I've also noticed it in other posts on HN: a disagreement with the position of the article is framed no
41.
by codys 1y ago
Nothing prevents using O_DIRECT as an open-flag for a fd used in other io_uring operations. But I'm not sure I'd necessarily think of O_DIRECT as a way of improving "confidence in a write". It's a way to get a speci
42.
by codys 1y ago
Unless the lack of real time (or consistent time to) results drives down interest in the cloud version, or instead of driving down interest makes it appear as if people want something different than what they would want if the time to resul
43.
by codys 1y ago
Btech markets devices that are GMRS type accepted, it's actually one of their main businesses these days to take Chinese developed radios and modify them slightly and get them GMRS approved in the US.
44.
by codys 1y ago
FFMpeg does have an API. It ships a few libraries (libavcodec, libavformat, and others) which expose a C api that is used in the ffmpeg command line tool. They publish doxygen generated documentation for the APIs, available here: https:&#x
45.
by codys 1y ago
When you say "modern GC", which particular implementation(s) of GC are you referring to?
46.
by codys 1y ago
That's a very good point on the timing. Thanks for adding that extra info.
47.
by codys 1y ago
In this thread I linked the fly.io security page because it helps us establish that one can talk about _languages_ as being memory safe specifically, which is something it seems you're rejecting as a concept in the parent and other com
48.
by codys 1y ago
That seems contrasted by Rob Pike's statement in 2012 in the linked presentation being one of the places where it's called "not purely memory safe". That would have been early, and Go is not called memory safe then. It s
49.
by codys 1y ago
The post is a demonstration that a class of problems: causing Go to treat a integer field as a pointer and access the memory behind that pointer without using any of Go's documented "unsafe.Pointer" (or other documented as un
50.
by codys 1y ago
Curiously, Go itself is unclear about its memory safety on go.dev. It has a few references to memory safety in the FAQ ( https://go.dev/doc/faq#Do_Go_programs_link_with_Cpp_programs , https://go.dev/doc&#
51.
by codys 1y ago
From the update added to the post: > This is tracked through io_uring's completion queue - we only send a success response after receiving confirmation that the completion record has been persisted to stable storage. Which completio
52.
by codys 1y ago
Yes, but I suspect there might be some confusion by the author and others between "io_uring completion of a write" (ie: io_uring sends its completion queue event that corresponds to a previous submission queue event) and "fsy
53.
by codys 1y ago
> > you lose the durability guarantee that makes databases useful. ... the data might still be sitting in kernel buffers, not yet written to stable storage. > No! That's because you stopped using fsync. It's nothing to do
54.
by codys 1y ago
> But database engines are absolutely the target of io_uring's feature set and they're expected to be managing this complexity. io_uring includes an fsync opcode (with range support). When folks talk about fsync generally here,
55.
by codys 1y ago
> Yes, you do need to check if both records are written and then report it back to the client. But that is a non-fsync request and does not tax your system the same as fsync writes. What mechanism can be used to check that the writes are
56.
by codys 1y ago
They do not state that it is exclusively collected for those purposes, only that those purposes is included. As written, they'd be in line with their policy to collect that data for any purpose (including those listed).
57.
by codys 1y ago
this seems possible to avoid as an issue without needing IP certs by having the configuration supply both an IP and a hostname, with the hostname used for the TLS validation.
58.
by codys 1y ago
Were there any Microsoft XP security issues caused by "Easter eggs" prior to that policy change? Or was this just put in place as a policy because it was easy to put in place?
59.
by codys 1y ago
I agree that there are problems when laying multiple build systems on top of one another, and I see that often as a user of nix (it's also bad with rust projects that use cargo, and though there are a variety of options folks have writ
60.
by codys 1y ago
True. That isn't something the compiler can do. That said, that (determining the c flags and ld flags for dependencies) is something that might be able to be mixed into compilation a bit more than it is now. Could imagine that if we an

More ›