I'm thinking about using Buck2 for a project, and the fact that binary releases are compressed with zstd is making the developer experience and initial onboarding this much more complicated. Unlike tar or zip, most people don't have zstd CLI installed on their machine, and some even might not know what it is.
My idea is to provide a superb DX, where you'd only need buck2 installed to successfully run the build.
Is there any specific reason for using zstd for Buck2 releases over something more conventional, except the fact that zstd was also created at Meta 🙂?
I'm thinking about using Buck2 for a project, and the fact that binary releases are compressed with zstd is making the developer experience and initial onboarding this much more complicated. Unlike tar or zip, most people don't have zstd CLI installed on their machine, and some even might not know what it is.
My idea is to provide a superb DX, where you'd only need buck2 installed to successfully run the build.
Is there any specific reason for using zstd for Buck2 releases over something more conventional, except the fact that zstd was also created at Meta 🙂?