porcelain

It's more like build porcelain for cases where you already have your package's whole dependency tree locked down.

The only something about git that hampers comprehensive porcelain alternatives is the lack of orthogonality in git's plumbing.

Many people have used Git for years without knowing anything about the plumbing beneath its porcelain.

Since it's actually shelling out to the cabal executable for its solving needs it still pretty much fits the definition of porcelain.

I wonder if anyone in the git team has considered doing any updates on the porcelain for them.

My inexpensive solution has been to simply not own any porcelain figurines or music.

The Chinese had very high grade porcelain for many of their household needs.

Git does not need another tutorial, it needs an alternative porcelain.

Compare this with porcelain plates which can be re-used and last a long time, but have to be washed, which uses water and some energy.

It's also true that I cannot make porcelain figurines of my own and have to buy all of those as well.

We also looked into abstracting that away by building a porcelain UI, but there are a lot of challenges there that are very difficult to overcome.

In most use-cases, you're talking about one extra porcelain command in comparison to a server-connected client like SVN or TFS, assuming you push every single changeset.

Yeah it kinda reminds me of the "plumbing and porcelain" approach of some programs like git.

Where these resource managers actually do concern themselves with the problem space of resource management as well as orchestration, Fleet is taking the position of a "distributed systemd" in a way without much else in terms of provided porcelain.

Porcelain is arguably better for mugs and bowls and can be made much thinner than glass can.