masklinn

16 ms·

331.
by masklinn 9mo ago
> There is a "pre-heat" feature which would be nice, but then it would keep it warm 24 hours a day which is ridiculous. Maybe some better boilers can time the pre-heat. Yeah one of my colleagues has a preheat which can be trigg
332.
by masklinn 9mo ago
> Does heating water in a boiler work well with a heat pump? Sure, heat pump hot water tanks are a thing. Air-to-water heat pumps are less efficient than air-to-air as they need to reach higher target temperatures, but it will be more ef
333.
by masklinn 9mo ago
> you’re permanently creating the string, so if it isn’t reused later, that means your memory usage needlessly goes up. Nowadays lots of runtime will GC interned strings to avoid this, this can mean churn in the interning table but avoid
334.
by masklinn 9mo ago
String interning only stores whole strings, dictionary compression stores sub strings. Essentially string interning is a trivial subset of dictionary compression (because you don’t need a substringing scheme, which is the hard part).
335.
by masklinn 9mo ago
I’ve also been guilty of plugging at something, and squashing it all before publishing for the first time because I look at the log and I go “no way I can release this, or untangle it into any sort of usefulness”.
336.
by masklinn 9mo ago
A component here is the highly unfortunate timing of two trains crossing one another as one of the trains derailed. Both trains look like rigid HSRs, and usually when these derails they stay very stable and rarely have fatalities.
337.
by masklinn 9mo ago
> Plus, some major XML libraries, like lxml in Python, are extremely unintuitive in their implementation of DOM structures and manipulation. Lxml, or more specifically its inspiration ElementTree is specifically not a (W3C) DOM or dom-st
338.
by masklinn 9mo ago
XSLT I see as a tragedy. The match / patch processing model is so elegant, but the programming langage built around it is such a disaster (the XML, various langage semantics e.g. the implicit context, the gimped semantics, and the deve
339.
by masklinn 9mo ago
Namespaces were fun! But mostly used for over engineering formats and interacted with by idiots who do not give a toss. Shout out to every service that would break as soon as elementtree got involved. And my idiot colleagues who work on EDI
340.
by masklinn 9mo ago
IIRC it’s not just laziness, there are things glibc explicitly doesn’t want to expose for various reasons, and since the two projects are essentially unrelated you get the intersection of what both sides are happy with. Traditional unices d
341.
by masklinn 9mo ago
Checking whether `deleted_at is null` should be extremely cheap, and it avoids the duplication and desynchronisation of having both “deleted” and “deleted_at”.
342.
by masklinn 9mo ago
That's the first solution (a function based index), however it has the drawback of fragility: a seemingly innocent change to the query can lead to not matching the index's expression anymore). Which is why the article moves on to
343.
by masklinn 9mo ago
Wouldn’t RL be 11? 2+(3 (4-1)) = 2+(3 3) = 2+9
344.
by masklinn 9mo ago
They will require breathing but much less than an open fireplace and a lot more of the heat will be kept inside and not sent through the chimney. So overall they’re way on the positive side. If you can get a cold air inlet it’s better, but
345.
by masklinn 9mo ago
> Then what was the intent of your comment? Pointing out to the other guy that their reply made no sense? > There's no point to making a 400dpi 32" display Thank you captain obvious. You do know that there are densities betw
346.
by masklinn 9mo ago
Is it an oled display? It’s likely that the subpixel rendering does not match the physical display, so the subcolors are in the wrong location making the text worse instead of better (in the case of macs Apple entirely removed subpixel rend
347.
by masklinn 9mo ago
> Which is the right choice because our eyes cannot resolve that kind of DPI at that distance. If you can’t resolve that kind of DPI at that distance you need to get an appointment because you require glasses. The low end of normal vis
348.
by masklinn 9mo ago
That’s not a point it’s nonsense thought termination. There’s a gulf between 130 dpi and 460 dpi, and in that gulf there are densities which stop being poor at monitor viewing distances. That smartphone densities are excessive for that purp
349.
by masklinn 9mo ago
I fail to see how that is relevant as I neither introduced nor advocated for smartphone pixel density?
350.
by masklinn 9mo ago
Sadly they're not super common which makes them expensive, and I don't think I've seen any that wasn't 16:9. The world has decided to go with refresh rates rather than resolution.
351.
by masklinn 9mo ago
Compared to a smartphone it's not just poor it's complete dreck. Smarphones are in the 400s.
352.
by masklinn 9mo ago
Which is a poor pixel density.
353.
by masklinn 9mo ago
> Now in the service of minimalism we have scrollbars that consist of a thin, semi-transparent line that fades out after half a second and is nearly impossible to click and drag due to how small it is. You can make them always on still.
354.
by masklinn 9mo ago
It should be noted the drag handle was removed back in Lion. And the square cutout was removed in Panther, both of which were iterations of Aqua. (and yes Lion was garbage, first upgrade I skipped since Tiger, and definitely the first &quot
355.
by masklinn 9mo ago
> That is the whole argument No, it is not. > Let me quote the other person: "My claim is that, if I call `foo(std::move(myObj))`, it is statically knowable if `foo` receives a copy of `myObj` or whether it is moved to it."
356.
by masklinn 10mo ago
Yes, it's a media query ( https://developer.mozilla.org/en-US/docs/Glossary/Media_quer... ) on the <link>. Only if the media query passes will the link "activate".
357.
by masklinn 10mo ago
> you can call functions on it Only functions with no preconditions, unless the type makes more guarantees as to the moved-from state.
358.
by masklinn 10mo ago
Usually yes, however because that's not for some resource types it can lead to less than ideal behaviour e.g. if your RAII resource is something which will get corrupted if there are two handles to it (some sort of odd hardware resourc
359.
by masklinn 10mo ago
That is static though, that `foo` takes its parameter by `const&` and will thus not move it is available to the compiler (or other tooling) at compile time. The point of contention is whether that is always the case, or whether there ar
360.
by masklinn 10mo ago
"Validity" is an extremely low bar in C++, it just means operations with no preconditions are legal, which in the most general case may be limited to destruction (because non-destructive moves means destruction must always be poss

More ›