I am not sure if this post can pass the algorithm of HN this time. Nonetheless, we are eager to learn feedback about the way we build Instill VDP for its no-code and low-code functionalities. Any comment is very appreciated.
One can absolutely lock versions in their Dockerfile. I can see that the design principle of DevBox is to pin the versions. At the end of the day we all need to consider versioning (i.e., the image version) the versions (i.e., package versions) anyway.
Reproducible Docker is fighting an uphill battle, Nix and it's ecosystem tries to be reproducible by default.
Dockers ecosystem aims more for repeatable, not reproducible.
> At the end of the day we all need to consider versioning (i.e., the image version) the versions (i.e., package versions) anyway.
The granularity of pinned versions and feasibility of having a culture of everything being pinned versus needing to know a crazy amount of things that need pinned a big difference.
6 months after we posted the manifesto (http://go.instill.tech/4bcxuf), we're releasing an Alpha version of VDP under the open-source Apache license 2.0.
VDP is the future for unstructured data ETL, where developers won't need to build their own data connectors, high-maintenance model serving platform or ELT pipeline automation tool.