In my experience, the ecosystems make up the developers mind most of the time. The Java ecosystem makes adding dependencies to a project cheap and very convenient. For example adding dependencies to a maven project is really simple but in most cases your maybe only using a small subset of that dependencies code and when you build a fat jar you end up wondering why it's 100mb plus. A rule I have found very useful recently is to favour libraries over frameworks. I know from experience I can back away from libraries much easier if that decision turns out to be a disaster.
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.
In my experience, the ecosystems make up the developers mind most of the time. The Java ecosystem makes adding dependencies to a project cheap and very convenient. For example adding dependencies to a maven project is really simple but in most cases your maybe only using a small subset of that dependencies code and when you build a fat jar you end up wondering why it's 100mb plus. A rule I have found very useful recently is to favour libraries over frameworks. I know from experience I can back away from libraries much easier if that decision turns out to be a disaster.