Pipes are parallelized when you have unidirectional data flow between stages. They really kind of suck for fan-out and joining though. I do love a good long pipeline of do-one-thing-well utilities, but that design still has major limits. To me, the main advantage of pipelines is not so much the parallelism, but being streams that process "lazily".
On the other hand, unix sockets combined with socat can perform some real wizardry, but I never quite got the hang of that style.
Pipelines are indeed one flow, and that works most of the time, but shell scripts make parallel tasks easy too. The shell provides tools to spawn subshells in the background and wait for their completion. Then there are utilities like xargs -P and make -j.
UNIX provides the Makefile as go-to tool if a simple pipeline is not enough. GNUmake makes this even more powerful by being able to generate rules on-the-fly.
If the tool of interest works with files (like the UNIX tools do) it fits very well.
If the tool doesn't work with single files I have had some success in using Makefiles for generic processing tasks by creating a marker file that a given task was complete as part of the target.
Having played enough video games that use joysticks for steering I don't want to drive a real car with a joystick. Crashing in Mario kart or Grand theft Auto because I sneezed is fine but not in real life.
Exactly. The control needs to have both an intentional and major motor movement from the driver. Modern steering wheels have the same benefit as the original iPod wheel. Easy for small movements, even accidental ones; possible for big movements.
Also funny that they had the ability to swap to the passenger to drive it. So acceleration/break for one person, steering for another? Really not a good idea.
You are oversimplifying the writer's position. They mention zoning as one reason but also other regulations, health codes (minimum sink counts!) and other things like parking minimums (which houston has had, though they've been removed recently in a lot of cases), reliable and ubiquitous public transit, etc.
I'm guessing you stayed in a major city and didn't drive anywhere outside of it? If you flew in and didn't have a rental car, odds are your itinerary was biased towards places that didn't need a car?
Communities were not doing fine. CoC didn't come out of nowhere because someone was bored. Having a CoC doesn't absolve moderators any more than having laws absolves judges from having to make good rulings.
I've been part of a lot of communities and never have I felt that a CoC was missing or needed. CoCs didn't come because they were needed but because of a social justice fad. Have a look at the Tim Peters incident with the Python community. The decision to suspend him, a core maintainer (he wrote the Zen of Python), was justified by made-up absurd alleged CoC violations. Without a CoC they couldn't have suspended him as easily without totally losing their face.
From the little we know the "material" in question would be photoshops made to harass Limor, made by someone at sparkfun. So it would be weird for sparkfun to complain , given the content originated with one of their employees. (Allegedly)
The bottleneck in the example was maxing out disk IO, which I don't think duckdb can help with.
reply