Hi. Le sam. 2 nov. 2024 à 10:32, Glavo <zjx001...@gmail.com> a écrit : > > > > > Reusing a library allows the host component to focus more on its business > > than having to draw attention from it. The benefits far outweigh any > > drawbacks in my view. > > > > At least for commons-compress, I don't agree with this view. I don't see > enough benefit, > and I just feel that commons-compress is too big and bloated right now. > > We use commons-compress in a small program[1] of about 5MiB. I have decided > to stay on commons-compress 1.25.0 due to size. > Then I will pick up the fork[2] I developed earlier to split and modularize > commons-compress, which will keep our program compact. > > Since I have decided to maintain my fork, I don't want to express my > opposition too much. > I just wanted to present our decision here as an example of how this could > indeed discourage some people from choosing commons-compress.
A fork is "copypasta" on steroids... Why not contribute your enhancement (modularization) to the code here instead? Gilles > > Glavo > > [1]: https://github.com/HMCL-dev/HMCL > [2]: https://github.com/Glavo/kala-compress >>> [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
