pipelines

It's one killer feature is pipelines, but the hierarchy is fixed depth and hard to learn.

You can think about processing your (semi) structure data (records) in terms of high level pipelines and processing steps.

Furthermore, the cost of producing the gas is not just the cost of the vessel - you need to drill wells and connect them to the vessel via pipelines/manifolds/risers.

You can only sell what you can deliver, and natural gas has to be delivered through pipelines.

Turns out it tends to be necessary when you're developing (key word) build pipelines and tooling.

The same reasoning applies to road freight, pipelines, and probably fresh fruit and cut flowers too.

Compiler optimizations matter even more on ARM than on x86 due to shorter pipelines, smaller caches, super-expensive synchronization primitives, and so forth.

All other dangerous networks like highways, runways and gas pipelines are tightly regulated.

No, you pay $1/month/pipeline for the pipelines which you've used during the month.

Yeah, I remember wanting to do a fan-out pattern in Go and reading the Go Pipelines and Cancellation article[0].

There are people who do nothing but develop looks and write shaders all day everyday, and others who create and manage distributed rendering pipelines.

These customer pipelines are the real magic - no matter what junk gets shoved down them, nine times out of ten, junk gets paid for.