> whereas nix will always produce the same output for a given input.
If they didn't take shortcuts. I don't know if it's been fixed, but at one point Vuze in nix pulled in an arbitrary jar file from a URL. I had to dig through it because the jar had been updated at some point but not the nix config and it was failing at an odd place.
This should result in a hash mismatch error rather than an output different from the previous one. If there is a way to locate the original jar file (hash matching), it will still produce the same output as before.
Apparently I made note of this in my laptop setup script (but not when this happened so I don't know how long ago this was) so in case anyone was curious, the jar file was compiled with java 16, but the nix config was running it with java 8. I assume they were both java 8 when it was set up and the jar file upgraded but don't really know what happened.
No it doesn't.
If the content of a url changes then the only way to have reproducibility is caching.
You tell nix the content hash is some value and it looks up the value in the nix store.
Note, it will match anything with that content hash so it is absolutely possible to tell it the wrong hash.
I recently switched from teflon to stainless steel, and after a few false starts figuring it out I like it more now. Also for something that leaves a lot of grease like sausage and bacon, the stainless steel surprised me by being easier to clean.
What did the false starts teach you? I have some stainless steel pans and sometimes they work great and sometimes they're just mysteriously sticky, with whatever I'm cooking bonding to the pan.
If it's happening only sometimes I'm not sure how useful this will be but these were where I had issues at the beginning - I'd looked up how to use them before buying them because I figured nonstick wouldn't exist if I could use them the same, but some information was misleading or incomplete. For example when cooking:
* You should preheat until you get a leidenfrost effect - get some water on your fingers and flick it onto the skillet, it should form droplets that bounce around without boiling off.
* Once this happens, immediately turn the heat to the lowest setting so the skillet doesn't get too hot (most instructions are missing this step and I didn't really expect the skillet would get too hot - stainless steel just keeps getting hotter at a temperature the teflon nonstick would maintain heat). Depending on your stove, the lowest might be a little too low and heat is slowly lost, this is something you'll eventually get a feel for.
* After getting the leidenfrost effect (maybe? not sure how important it is to wait until after), you have to add something (butter or vegetable oil, for example) to coat the surface and not only get a nonstick effect but also sort of buffer the heat. It's kind of like cast-iron seasoning, but extremely low-effort and you do it / clean it off every usage. Some of the things I'd read before buying said the leidenfrost effect was the important part for getting a nonstick surface without mentioning this stage, which led to a pancake that was black and stuck to the skillet on one side and still liquid batter on the other.
And when cleaning:
* I'd mentioned sausage and bacon above, these leave gunk that sounds kind of like what you described except a lot more of it. For some reason getting a wet paper towel and rubbing down the skillet (instead of putting water on the skillet directly) works really well getting almost all of it off, though it will take several of them.
* If there's still residue not coming off, something I got from reddit worked even where grease-removing dish soap didn't: Lightly boil baking soda in water in the skillet for about 20 minutes. Don't let the water boil off or you'll be left with baking soda gunk stuck to the skillet, you want it to dissolve and soak in the hot water for a while before emptying it and wiping it down.
* And lastly one of the side reasons I like it over nonstick while cleaning: The surface is actually smooth. When using a scrunge to wipe it down you can feel where there's still something stuck to the surface, while nonstick is rough even when clean.
I had one that person seemed to think their @twitter name was the same thing as my gmail address. Haven't seen it in a while, maybe they figured it out after I told their kid's teacher they had the wrong person...
Ice, slush, sleet, snow, graupel, hail... And within there is a subtype "black ice", a compound noun that isn't really just a description (it's not black, it's nearly invisible - a similar sense as another one, "black hole", which you'd never figure out from the components alone).
We have a lot of words for "frozen water" because it takes a lot of forms. As far as I know "boiling water" is only one thing so we've never needed additional words to distinguish it.
About halfway down the page (look for "revolutiooon") there's some example images that seem to be meant to show how Japan didn't change around 2010 while the rest of the world did. Except the "American" set of images also show that we didn't really change either. Were those supposed to be different images?
> In Russia and Ukraine pretty much every child can read by the time they enter the first grade.
In the US too, reading is generally handled in Kindergarten, the year before first grade. If your parents didn't teach you before that, like mine did.
> Meanwhile, when I was learning English there basically was one spelling rule: memorize.
There are rules though, that we're ad-hoc taught as kids, or just absorb through exposure. Just because there's a lot of exceptions doesn't mean they don't exist. Here's an attempt at listing them out: https://www.zompist.com/spell.html
I dunno, AI tools love adding not only useEffect but also unnecessary useMemo.
> I don't know why people think the virtual DOM is a performance boost.
It was advertised as one of the advantages when React was new, due to the diffing browsers would only need to render the parts that changed instead of shoving a whole subtree into the page and the having to do all of it (because remember this came out in the era of jquery and mustachejs generating strings of HTML from templates instead of targeted updates).
Patching the DOM existed long before React, that wasn't a new technique. IIRC, the idea was more that the VDOM helped by making batching easier and reducing layout thrashing, where you write to the DOM (scheduling an asynchronous layout update), read from the DOM (forcing that thenlayout update to be executed synchronously now).
That said, none of that is specific to the VDOM, and I think a lot of the impression that "VDOM = go fast" comes from very early marketing that was later removed. I think also people understand that the VDOM is a lightweight, quick-to-generate version of the DOM, and then assume that the VDOM therefore makes things fast, but forget about (or don't understand) the patching part of React, which is also necessary if you've got a VDOM and which is slow.
There was a website back when I was in college where you'd click through some presentation or tutorial or something about bitcoin and at the end they'd just give you 0.5 bitcoin for free.
If they didn't take shortcuts. I don't know if it's been fixed, but at one point Vuze in nix pulled in an arbitrary jar file from a URL. I had to dig through it because the jar had been updated at some point but not the nix config and it was failing at an odd place.
reply