puetzk

That's a rotating spindle, which indeed can catch a loose thread and reel it in. An oscillating cuter moves back and forth, so it unrolls just as much as it rolls, with no net pull.

And if the oscillation strokes are short enough it can saw rigid material while just vibrating jiggly flesh (this is how the saws used for cutting off casts work). Though cardboard is also pretty floppy, so the mechanism here is probably different (mostly the puck guard keeping fingers out)

https://ocasio-cortez.house.gov/about > After high school, Alexandria attended Boston University, and graduated with degrees in Economics and International Relations (and tens of thousands of dollars in student loans). During this period she also had the opportunity to intern in the office of the late Senator Ted Kennedy.

She was indeed a congressional intern, but then her father died and family finances got rough, and a year later Ted Kennedy died (August 25, 2009) so she lost the job in his office.

Following the financial crisis of 2008, tragedy struck when her father passed away suddenly from cancer. The medical bills and other growing expenses placed their home at risk of foreclosure. Alexandria pulled extra shifts to work as a waitress and bartender to support her family,

Her father seems to have been in the business of home remodeling and renovations. I haven't found any source for "owned multiple brownstones", but a little bit of house-flipping or some rental properties wouldn't be weird to see in that kind of business. Being a landlord with a mortgage doesn't necessarily mean huge wealth, and it it's easy to believe a combination of cancer treatment bills/being unable to work/2008 housing crisis could take a situation like that from comfortable to house-poor to foreclosure on upside-down loans in an awful hurry.

Evolution doesn't plan ahead. Various plants got various random mutations that produce various random chemicals. The ones that were tasty to birds but disgusting to mammals for their seeds spread all over and ended up pretty widespread, so they survived and became common.

The ones that were repulsive to birds but tasty to mammals got eaten by something that grinds up their seed, and so they are extinct. Or, (after humans invented agriculture), possibly got domesticated and became extremely numerous since we'd intentionally save some seeds to plant despite eating the rest.

But there was no awareness and no plan, just chance and history and whatever happened to work.

Unihertz phones still do (even the tiny Jelly Star)

and laptop

Maybe start with a screen module for a Framework laptop: https://github.com/FrameworkComputer/Framework-Laptop-13/tre..., before/instead of trying to engineer a laptop from scratch...

Relatedly, GCC/binutils still has a `.ident` assembly directive (https://sourceware.org/binutils/docs/as/Ident.html) and `#ident` preprocessor command (https://gcc.gnu.org/onlinedocs/cpp/Other-Directives.html) that emit data into an ELF .comment for `what` to read...

My daily driver is a Unihertz Jelly Star: full android 13, but on a 3" screen and it fits in a watch pocket. Probably not for everyone, but I love it and maybe you would too...

Well, is also quite possible that adding such a bug was the previous stage. Or even just having found one that you didn't report/fix...

this obviously fails if the content is missing.

It doesn't, actually - all the fetchers are [fixed-output derivations](https://nixos.org/manual/nix/stable/language/advanced-attrib...) where you specify not only the source, but the hash it is expected to produce. And so the fetched files will be hashed and placed in the nix store under that hash. And therefore subsequent builds using that artifact will use the already-stored artifact and not care if the source is reachable or not. You know that all "external" inputs will be captured by fixed-output derivations, because any derivation that isn't fixed-output is blocked from network access.

For anything built by the hydra CI, this will be retained on central cache.nixos.org. Or you can copy from a store of some machine that has it.

Now, if it's something not on the official cache.nixos.org, and the source is gone, and you've lost (or pruned) your store, you will need to get the file from somewhere and put it back in your store: https://nixos.org/manual/nix/stable/command-ref/nix-store/ad.... Or you just change the source URL (this won't change the derivations depending on it, because the input being transferred is identified by the hash that is to be delivered, not by the URL it comes from).

The (beat) "drop" is genre term for a buildup of tension, sharp pause, and then suddenly resuming at greater intensity/tempo. Usually associated with EDM/dubstep.

E.g. https://www.youtube.com/watch?v=db5f-A-vSyw (drop at 0:45 seconds in the video, thought the countdown to New years that takes up most of the stage should make that obvious anyway)....

Thought it's certainly not a new thing - plenty of classical music has similar moments, e.g. the 3rd movement to Beethoven's 5th symphony: https://youtu.be/xAQFJ1YpFaI?t=279 ("drop" at 5:05 when the horns blast their way in...)

Now it just need to be combined with something like https://github.com/haimgel/display-switch to do a DDC/CI monitor input switch as the USB activity moves around.

With a device like this you'd be missing the on_usb_connect event, but presumably you could do something (a special HID device button, an extra device id appearing, who knows) to make it work.

CO2 is opaque to many wavelengths ("colors") of infrared light. So when the surface would be cooling at night by radiating infrared light back to the darkness of space, CO2 blocks(and reabsorbs) this energy, warming the atmosphere. This effect is strongest in a band around 15μm wavelength.

https://www.acs.org/climatescience/atmosphericwarming.html has a pretty good (though above ELI5) set of graphs and explanations of the chemistry involved.

You can dynamically link one service from another container. Choose wisely.

The texas blackout was a major factor - it hit an NXP plant that didn't manage to complete an orderly shutdown in time, and caused enough equipment damage that they couldn't get operating again at all for a month, and at reduced capacity for a long time after.

https://www.statesman.com/story/business/2021/03/12/nxp-coul...

There was also a Samsung plant similarly affected, which I think didn't really get back operational until the end of March.

Just FYI, it lives on, and there's an android keyboard app that implements it! mostly useful if you have a device with stylus, of course: https://play.google.com/store/apps/details?id=com.access_com...

Also, this function is just regex::escape https://docs.rs/regex/1.4.5/regex/fn.escape.html

I use it in Firefox regularly, and just checked and it runs in chrome too. Weird...

Unihertz still makes lots of the out-of-fashion form factors: https://www.unihertz.com/titan.html is a blackberry-esque android 9.0 device.

If you want to look at the limits of what physics seems to allow (cost practicality be damned), look at things like americansolarchallenge.org winners. They even have a multi-occupant-vehicle class nowadays.

The 2018 MOV winner (https://www.americansolarchallenge.org/the-competition/ameri... ) logged 1762 miles over 58.4 hours, or about 30mph average pace (with a 16.8kWh battery, but no external charging, just the ability to time-shift some energy).

That's with a vehicle that looks like this: https://www.youtube.com/watch?v=aE9gkYsR4TU

But heaters on thermostats will just run more if they are putting out less wattage. So across your whole population of houses, you won't move that part of demand much (maybe a few were already running at 100% duty cycle).

Right. But you can buy a stock (without knowing it was a borrowed share in a short sale), and then lend it to someone else (who intends to sell, it, thus creating another short sale).

So to unwind this, the one existing share has to get bought (by someone who short-sold it), and returned (to the owner who lent it out), twice.

There's actually a 3rd x86 license, that has changed hands quite a few times (Cyrix -> National Semiconductor -> Centaur(IDT) -> VIA -> Zhaoxin, I think, unless I missed a few transitions?)

There's also the https://opencores.org/projects/ao486 - the relevant patents on a 486-era design would have expired

I don't know if there's something either higher up that you'd qualify as "can readily buy", but a [Raptor blackbird](https://www.raptorcs.com/content/BK1B01/intro.html) would handily outclass the legacy PPC macs, and a [Talos 4U server](https://secure.raptorcs.com/content/TL2SV2/purchase.html) (with two CPUs up to 22 cores each) would pretty much crush it.

Admittedly the latter is a $15k machine, which is perhaps may be pushing what you had in mind for "can readily buy", but it's for sale...

It depends, [CAM succulents](https://en.wikipedia.org/wiki/Crassulacean_acid_metabolism) do their gas exchange at night, and then close their stomata and do the photosynthesis during the day. It's a dry-climate adaptation, to lose less water in the process of exchanging the previous day's O2 for fresh CO2.

And they don't even ship the CRT with the compiler any more

Just in case you/any other reader didn't know: That's just because they don't consider the ucrt compiler-version-specific anymore, it's distribution (binaries and source) moved into the windows SDK, E.g. Windows Kits\10\Source\10.0.17763.0\ucrt. The vcruntime is still with MSVC.

But this source never included the STL.

Because the 3.8 beta (and hence 3.8 feature freeze) is next week, and there's basically no chance of completing the PEP in time to make that cutoff.

It's because it's trivial to improve. The reason the MSVC STL is so slow in debug mode, is because it's really debug; they pull out all the stops to bounds-check every dereference, keep a generational count to detect iterators that could potentially have been invalidated by an operation that moved elements or reallocates the container (and do so whether or not the potential resize actually happened), etc. This adds a ton of code to the iterator paths, and (due to that code size) loses most inlining opportunities.

If you want it to be as fast as other implementations, ask it to do less of this. They provide [_ITERATOR_DEBUG_LEVEL](https://docs.microsoft.com/en-us/cpp/standard-library/iterat...) for exactly that purpose. I think their choice of default (Debug means you want it to catch as many bugs as it can, and Release means it should be fast) is appropriate.

If they hadn't provided the knob to adjust this I'd agree they had a problem for some use-cases, but if you want the faster-but-less-thorough mode you just have to ask for it.

It's also possible to move the listener to a permission-protected unix socket https://docs.syncthing.net/users/config.html?highlight=unix%...

Pity that I don't know of any browser that readily supports HTTP over a unix socket (nginx can proxy_pass it, but then you're back to a TCP listener).

But a multi-user install could reasonably lock things down in that way, though the defaults definitely favor "works out of the box on a single-user machine".

It defeats user-privilege separate on localhost - I (or an unprivileged daemon) can't get at parts of the filesystem belonging to their user instead of mine, but I can get at TCP ports on localhost that belong to other user's syncthing daemons, and reconfigure their syncthing to send all their data to me.

If your nodes have direct network access to each other, no.

But if two nodes that have added each other's keys cannot reach each other directly (e.g. are in separate private networks/behind firewalls/etc) but both can reach an external relay server, it may act as a dumb pipe bouncing encrypted traffic between them.

https://docs.syncthing.net/users/relaying.html

There is a public pool of such relay servers (https://relays.syncthing.net/), and by default syncthing will reach out and connect/announce its itself there so other nodes looking for it could contact it via a relay.

You can host your own relay server and configure your clients to use it exclusively: https://docs.syncthing.net/users/strelaysrv.html#client-conf... or if you only want syncing when your nodes are on the same local network you should be able to just not configure any relays at all.