1,125 karma · joined April 29, 2016
Enlisted, which uses the same engine, is fine though.
Going through the stuff chronologically seems to help understand how the ideas got put together. The 2017 MS paper is the oldest of the four and mentions a weaker MSPrecise method using summary statistics. I mean… if we really are sure some two things are somehow related, you might as well throw ML at it and see what it comes up. It's just linear, no super fancy models.
Cooking in plastic (or any "original package") has a food safety point in restaurants. Keeping it sealed until the outside is sterilized reduces possible contamination. Immersion also makes for easier and faster heating.
2) XQuartz took a while, but is doing well.
3) was a big one in making upstream wine not work. with wine32on64 you can sure still pull the pinball party trick, but building that thing takes too much.
4) was specifically SIP for me, especially when they started making updates break with system changes. The ntfs-3g automount thing has always relied on replacing mount_ntfs [which is, by the way, not the proper way to make an fs on a Mac -- there's some filesystem bundle business], and now it's too much of a pain to still access the Windows drive.
More realistically though, we would throw away at least half that length like how we are handing out /64 blocks to everyone on IPv6.
Lifestyle modification can only go so far when the stress of living remains high. Swap the burnt stuff with something that puts less tar in your lungs, maybe, but any further is… sigh.
Now CA3153196A1 is the interesting one as it names Xanthobacter sp. VTT-E-193585 as the strain of interest. You even get a 16S rRNA sequence with it for doing some taxonomy! This is not to be confused with FI129574B involving a similar but genetically modified bacterium.
(Patent says it’s a strain of Xanthobacter.)
These drives generally come from budget laptops where the optane is originally used as the system disk. Not a good idea anyways and computer shops usually swap them out. You pay about 28 CNY for 16 GB, which is 2x the average SSD price-per-gig.
Or you could just send any super strong signal on the frequency to cover the satellite signal up. That can also work.
Iron is probably the only nutrient I can immediately think of where there’s a significant (~2x) bioavailability difference between plants and animals. Not big enough to make the animal source "more efficient" from a resource use perspective considering the feed conversion still.
Even Intel’s Clear Linux does not bother to patch individual libraries. They just use the glibc library multi-versioning feature to load from different directories depending on the cpuid.
In my opinion, GCC and Clang could make the whole thing more ergonomic. Ideally you declare a function as "interesting for multi-versioning" in the source using an attribute, then in the command line define what -march's to actually clone for. Kinda like ICC’s /Qax. (On second thought preprocessor defs are sufficient, duh.)
We can and have designed cities that properly handle rainfall. The issue is not density, but the lack of water-permeable surfaces. Suburban parking lots and wide freeways cause the same issues and on a larger scale due to the low density.
The lack of nature is, again, solved not just once. In Amsterdam they have dense urban areas right next to actual farms with cows, free-range ones. Again, you save space for nature by going high density. Compared to sprawling out with cul-de-sacs a you have more people getting closer to nature more often. Same argument for farmers traveling to town.
(I do sense a bit of mismatch between conceptions of non-dense-city living spaces. You seem to be talking about something that combines the environment of rural areas with the convenience of suburbia, but these two seldom co-exist without wasting a lot of tax money on maintenance…)
* The range reduction is, well, probably worse than acos. Look for Payne–Hanek–Corbett. Not an issue for games, I assume.
* The LERP is nice and all, but Qt actually has an even better one: instead of doing a LERP, you use the local derivative also available from the lookup table. https://stackoverflow.com/a/52841086
Others have already mentioned the Remez and the Horner stuff. Won’t repeat here.
I guess that’s to be expected with “pure ruby” — all the cross-insn backends you can use (Cranelift, LLVM) are written in not-Ruby.
I cannot access the tanzil XML file right now due to MobileSafari layout issues (boo). https://github.com/ceefour/qurandatabase has its own consistent DTD, but I doubt this is the only format I will find.
https://github.com/v2ray/discussion/issues/704 is the actual issue; my memory could be wrong.
On these slightly squished and stretched ones… I think converting back to OKlab is the better idea. You can just turn the polar stuff into Cartesian directly too, but it will be distorted.