Don't build the wheel repeatedly. The wheels are more than enough.
Docker itself is sufficient, additional packaging will only hide too much detail, which is not conducive to developers to understand the nature of the problem, and add additional problems.
In the short term it may improve development, CI/CD efficiency, but in the long term it is not conducive to developer knowledge growth.
Exception: unless it is a more advanced solution with better algorithms that greatly improve performance in terms of time and space.
Thanks for your insight, it's indeed a valid point...
But other point is this kind of solution also helps you learning all these, having sane defaults and learning curve, so it's easier for new comers to start using and feeling the benefits of it.
This is kind of the same tradeoff of using frameworks or not, etc.
IMHO you never should fully rely on the tool but also learn from it, how it solves the problems.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Don't build the wheel repeatedly. The wheels are more than enough.
Docker itself is sufficient, additional packaging will only hide too much detail, which is not conducive to developers to understand the nature of the problem, and add additional problems.
In the short term it may improve development, CI/CD efficiency, but in the long term it is not conducive to developer knowledge growth.
Exception: unless it is a more advanced solution with better algorithms that greatly improve performance in terms of time and space.
Thanks for your insight, it's indeed a valid point...
But other point is this kind of solution also helps you learning all these, having sane defaults and learning curve, so it's easier for new comers to start using and feeling the benefits of it.
This is kind of the same tradeoff of using frameworks or not, etc.
IMHO you never should fully rely on the tool but also learn from it, how it solves the problems.