Using (cargo) bikes to get shit done. Had to pick up the car after getting new tires installed, so on the way home from work swapped cargo bike for car at the gas station, drove home, rode the 3-speed back to the garage, and towed it home behind the cargo bike.
The cost of the car repair was equal to the cost of the Big Dummy's frame (though not in inflation-adjusted dollars, the Big Dummy is 16 years old).
Russ & Daughters which has been on New York's Lower East Side for 114 years is about the size of a subway car.
"Russ & Daughters for me was a literal mom and pop. Because it was my mom and pop," says Niki Russ Federman,
who is a fourth generation co-owner of the family business.
"As a kid, I would wait at the doors for the produce delivery guys to come, and they would wheel in with their handcarts. They had sacks, 50 pound sacks of onions, carrots…
A simple layered-wheel-like construction
Maria Chudnovsky, David Fischer, Sepehr Hajebi, Sophie Spirkl, Bartosz Walczak
https://arxiv.org/abs/2507.06169 ht…
Physics-Informed Detection of Friction Anomalies in Satellite Reaction Wheels
Alejandro Penacho Riveiros, Nicola Bastianello, Karl H. Johansson, Matthieu Barreau
https://arxiv.org/abs/2509.04060
A while ago, I've followed the example given by #Fedora and unbundled ensurepip wheels from #Python in #Gentoo (just checked — "a while ago" was 3 years ago). This had the important advantage that it enabled us to update these wheels along with the actual pip and setuptools packages, meaning new virtual environments would get fresh versions rather than whatever CPython happened to bundle at the time of release.
I had considered using our system packages to prepare these wheels, but since we were already unbundling dependencies back then, that couldn't work. So I just went with fetching upstream wheels from PyPI. Why not build them from source instead? Well, besides feeling unnecessary (it's not like the PyPI wheels are actually binary packages), we probably didn't have the right kind of eclass support for that at the time.
Inspired by @…, today I've tried preparing new revisions of ensurepip packages that actually do build everything from source. So what changed, and why should building from source matter now? Firstly, as part of the wheel reuse patches, we do have a reasonably clean architecture to grab the wheels created as part of the PEP517 build. Secondly, since we're unbundling dependencies from pip and setuptools, we're effectively testing different packages than these installed as ensurepip wheels — and so it would be meaningful to test both variants. Thirdly, building from source is going to make patching easier, and at the very least enable user patching.
While at it, I've refreshed the test suite runs in all three regular packages (pip, setuptools and wheel — we need an "ensurepip" wheel for the last because of test suites). And of course, I hit some test failures in testing the versions with bundled dependencies, and I've discovered a random bug in #PyPy.
https://github.com/gentoo/gentoo/pull/42882 (yes, we haven't moved yet)
https://github.com/pypy/pypy/issues/5306