dwattttt

34 ms·

781.
by dwattttt 2y ago
The existing pattern leads to very useful usecases though: there are resources a server only needs to open once (e.g. during startup), and being able to then remove access while holding onto the one handle you're going to use is a secu
782.
by dwattttt 2y ago
> How does your rationale explain Internet Explore/Edge and Safari which both have abundance of money and still can’t outcompete Chrome? How do I explain groups that attempt to compete and don't overthrow an incumbent? How much
783.
by dwattttt 2y ago
> Opera and Firefox and others are all free browsers as well And yet browser development costs money. If browsers cost money, you could make a better product and compete by selling it, but when an incumbent is giving theirs away for free
784.
by dwattttt 2y ago
I thought so too, and I thought "this is just robust control with different words", but after reading the abstract I don't think robust control actually describes deriving an improvement from perturbing an input. On the other
785.
by dwattttt 2y ago
So to be very clear: def foo(x): x['a'] = 1 y = {'b': 2} foo(y) print(y) foo can modify the object y points to, but it can't make y point to a different object? Is that what "This is impossi
786.
by dwattttt 2y ago
Really, the mismatch is at the JSON side; arbitrary JSON is the opposite of strongly typed. How a language lets you handle the (easily fallible) process of "JSON -> arbitrarily typed -> the actual type you wanted" is what ma
787.
by dwattttt 2y ago
This is what confuses me; it sounds like what you're saying is Python isn't pass-by-reference, it's pass-by-value, and that value is sometimes a reference? Honestly, "x's value, like the value of all Python variable
788.
by dwattttt 2y ago
Sure, but in the traditional sense of pass-by-reference you could say it's just always pass-by-value, and that value is always a reference. It's just not a helpful thing to say. (In those traditional pass by reference languages, w
789.
by dwattttt 2y ago
Is it not pass-by-reference by some technicality? In the mutation example you suggest, if a reference to x isn't being passed into foo, how could foo modify x? I would sooner believe the example is showing you shadowing the z argument
790.
by dwattttt 2y ago
True. You could write it in C or asm too, and it would be about as simple. But there's still a difference that if they weren't all primitive (and you can't always rely that they will be), you'll know it won't work s
791.
by dwattttt 2y ago
The stronger guarantees/performance fall out of the stronger lifetime/ownership model, combined with errors around ambiguous/invalid lifetimes being a compiler error. In other languages those violations are things you have to
792.
by dwattttt 2y ago
Generic dispatching all the type combinations (or warning or erroring) wouldn't be a problem in a project the scale of the Linux kernel. I'm unfamiliar with the incantations needed to try preserve constant expressions though, that
793.
by dwattttt 2y ago
With a 1.0 release in a month!
794.
by dwattttt 2y ago
I took a brief look into Windows public API, even with a tight coupling between compiler/toolchain & OS they don't offer a way to increase the region for a stack after a thread has been created.
795.
by dwattttt 2y ago
It's funny the parallel of "detect when the mapped stack region is exhausted, and map the next page" and "detect when the stack region is/will exhaust, and reserve/allocate another region"
796.
by dwattttt 2y ago
Oh, is stacker requesting stack growth that otherwise wouldn't happen? I always just assume address space reservations are cheap/free, and you can just mark a heap (hah) of space for your stacks. I guess it also has the behaviour
797.
by dwattttt 2y ago
To rustc not calling stacker enough/at the right times, the behaviour on MSVC/Windows is for the compiler to rely on hitting the OS's guard page to extend the stack (rather than growing it yourself), but also for the compiler
798.
by dwattttt 2y ago
I regularly find quite smart people assume Rust's references must be fat pointers to handle lifetimes, and check them all at runtime.
799.
by dwattttt 2y ago
> If I can dream, all of this would be solved by 72-bit CPUs, which would be the same as 64-bit CPUs, but the upper 8 bits can be used for garbage collection tags, sentinel values, option types etc. https://www.cl.cam.ac.uk&#x
800.
by dwattttt 2y ago
I think config _is_ the clear boundary between those gathering, ordering etc steps. The less expressive config is, the more regular and structured it is, and it becomes very easy to be descriptive and composable.
801.
by dwattttt 2y ago
Calling all TIS-100 fans
802.
by dwattttt 2y ago
Reason number 37 to hate "code as config"
803.
by dwattttt 2y ago
It also prevents backwards edges in the control flow graph; no loops (unless entirely unrolled), no recursion
804.
by dwattttt 2y ago
And since they haven't been removed, just not implemented, you get the joy of finding out it doesn't work anymore when you try to use it, instead of when you build it!
805.
by dwattttt 2y ago
The P cores being presented as two logical cores and E cores presented as a single logical core results in this kind of split already.
806.
by dwattttt 2y ago
They also admit a microcode algorithm produces incorrect requests for voltages, it doesn't sound like they're trying to shift the blame; ASUS doesn't write that microcode
807.
by dwattttt 2y ago
FWIW their configuration files can't be holding addresses; those have been randomised in the kernel for at least a decade
808.
by dwattttt 2y ago
Not rigorous enough to have detected this flaw in the kernel sensor, although effectively any bug in this situation (an AV driver) can brick a machine. I imagine WHQL isn't able to find every possible bug in a driver you submit to them
809.
by dwattttt 2y ago
In representation yes. But if you have UncheckedEmail, you can't accidentally validate a Username, or use an UncheckedEmail as a Password
810.
by dwattttt 2y ago
It would be a good but difficult analysis; at a quick check, rr 1.0 took 3 years and signficant contributions from around 3 or 4 people (I saw at least 5 people contributing), and the rr we have today is 10 years further work on that.

More ›