FR: Document comparison with buildpacks

[imjasonh]

First of all, very cool project! I love anything that'll improve the image building experience and make efficient images easier to get right.

But, I'm curious how this compares to buildpacks, which also detect source language, but further skip Dockerfile generation and are capable of building images in environments where Docker isn't installed.

Could you help me understand where this tool fits in, in your opinion? Thanks!

[beornf]

My thoughts regarding buildpacks is I like how they take care of setting up simple environments. Cloud native buildpacks do sound promising being able to generate OCI images compatible with Docker.

However I am not a fan of reading lengthy bash scripts. My opinion is that Dockerfile and other build specifications are easier to read and make required changes. Plus Docker builds are deterministic so you can test thoroughly in development.

If you add an obscure system dependency to your app in the next release none of the buildpacks will "just work". So you'll need to write a Dockerfile at this point which this tool helps with.

[beornf]

Should also write a comparison with a project I got inspiration from https://github.com/openshift/source-to-image. I still wanted a tool that can output a human readable Dockerfile instead of running adhoc build scripts with a Docker container as the byproduct.