dwattttt

35 ms·

721.
by dwattttt 2y ago
I believe V6 is a reordering of V1, not V4. V4 is random aside from the bits specifying version & variant, ~6/7 bits.
722.
by dwattttt 2y ago
It's not a cloudflare thing: https://developer.mozilla.org/en-US/docs/Web/API/Worker/post...
723.
by dwattttt 2y ago
Firewall lets it through: cups-browsed explicitly listens for printers advertising themselves. If it's firewalled off, how can it receive the printer advertisements? I don't know what default firewall rules are configured, but on
724.
by dwattttt 2y ago
The article doesn't go into detail about the unstable features, that's not just a list of features that haven't been released yet. Some are experiments whose result will be "can't or shouldn't be done". So
725.
by dwattttt 2y ago
A phrase I heard early in my career from a superior while reviewing code was "just reminding myself that while this isn't how I'd do it, that doesn't make it wrong"
726.
by dwattttt 2y ago
The failure modes are much clearer: when you write the API in a default-deny context & forget to add that allowed pattern, it never works, so you notice & figure out the bug. The same story with default-allow means the system looks
727.
by dwattttt 2y ago
The optimisation the parent is referring to is development time/effort; if the alternative to dumping a structure to a file is to hand roll your serialiser/deserialiser, that's a slower & probably more error prone approac
728.
by dwattttt 2y ago
I guess if mice are generating too many messages, asking Windows to coalesce them has less impact.
729.
by dwattttt 2y ago
There's a lot to be said for a consistent process that always fixes a problem, vs one that fixes the problem relatively permanently, inconsistently, and requires more memory.
730.
by dwattttt 2y ago
Because the phrase has always bothered me: this means something other than what it's commonly understood to nowadays. An older use of the word "prove", as in to test, means it says "that's an exception that tests th
731.
by dwattttt 2y ago
An x86_64 toolchain is allowed to assume SSE2 is present, it's mandated by the AMD64 spec.
732.
by dwattttt 2y ago
I would imagine the normal lifetime arrangements in Rust would prevent this, the same way it prevents nesting a shorter lived pointer inside a longer lived struct when they're all from the same allocator.
733.
by dwattttt 2y ago
Honestly, with the kind of changes and restrictions that you would end up needing, you'll end up with enough of a different language that you can't cleanly migrate a big existing codebase. If a codebase wasn't designed with t
734.
by dwattttt 2y ago
I dunno how sustainable that scenario is, because it brings to mind the maybe apocryphal Chinese curse "may you be granted everything you wish for".
735.
by dwattttt 2y ago
> Your best option was basically a `Maybe SomeResponseType` which in the `None` case gave a 200 response with a "{'status': 'error'}" content. This seems to be an area where my tastes diverge from the mainst
736.
by dwattttt 2y ago
The scenario is that after the original file handle is closed, a new open occurs and the file is assigned the same handle value. Then code acting on the stale handle of the first file closes it, and accidentally closes the new file instead.
737.
by dwattttt 2y ago
But that's where non-blocking leads; it can't block until it reads all the bytes you asked for, that has to be handled somehow. A fancy C library could buffer the partial read for you rather than you needing to do it, and it could
738.
by dwattttt 2y ago
How automatic it is depends on the language, but error "objects" (rather than codes) can do this too. It is pretty great.
739.
by dwattttt 2y ago
There were quite a few times when patterns I expected to work were forbidden, but each time I learned why I learned something important (can't iterate a list of callbacks and pass a mutable reference of the list in? Iterator invalidati
740.
by dwattttt 2y ago
I very much do not want to go back to the days of "read up to 4 bytes off the wire to see how big the next chunk is. Oh I only read 3 bytes? Guess I'd better save those 3 + the fact I need to read 1 more, then drop back out to the
741.
by dwattttt 2y ago
Speaking as someone who has written C skirting both sides of the UB line & referenced the spec to see when something tipped too far over said line... The fear that I'd be less productive for a "long" time was quite overbl
742.
by dwattttt 2y ago
I propose the search tool decide how to split up the region I want searched, rather than me trying to compose simpler tools to try to achieve the same result.
743.
by dwattttt 2y ago
NODEFAULTLIB is quite a rite of passage
744.
by dwattttt 2y ago
That just pushes the task of optimising the workload up to you, complete with opportunities to forget about it & do it badly. I don't relish the idea of splitting sections of a file up into N chunks and running N grep's in par
745.
by dwattttt 2y ago
Safety may be a spectrum, but `unsafe` in Rust is very explicit about what it allows/enables. They never say "if you only write safe Rust you won't encounter logic bugs".
746.
by dwattttt 2y ago
Rust is not a new language for Firefox, some of Firefox is already written in Rust.
747.
by dwattttt 2y ago
>OpenAI said it complies with all copyright laws when training its models and that “we believe that legally copyright law does not forbid training”. I mean, it sounds like they aren't even offering excuses? They're just saying
748.
by dwattttt 2y ago
How bad those limitations are depends on the purpose of the simulation, they satisfy a few uses cases even with those limits. Also the skill sets involved in those two tasks are quite different.
749.
by dwattttt 2y ago
In context, there's still a right answer; the absolute path used to run the process should always be right, because the Windows locks the file (I'm sure with enough effort this can be made wrong, but I'm also sure that's
750.
by dwattttt 2y ago
Imagine not making an API more flexible because new users of it would fail when interacting with old versions of the API.

More ›