Most development these days seems to turn to libraries and/or frameworks straight away - along with all the associated tooling. People don't stop and think if something could be done way quicker and more efficiently just using the basics. This leads to bloat, performance issues, and a whole raft of complications that really do not need to be there.
To be honest, this has always occurred and is not really a recent phenomenon. It does seem to be getting worse though. I believe it stems either from laziness, a lack of knowledge, or a "don't care" attitude towards performance and resource use. I think it's exacerbated by the rate of improvement in the capabilities of hardware outstripping our ability to be able to fully utilise them, and a convenience culture of just using "off the shelf" solutions/components without really understanding how they work - just to get something 'out the door' with the minimum of effort
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.
Most development these days seems to turn to libraries and/or frameworks straight away - along with all the associated tooling. People don't stop and think if something could be done way quicker and more efficiently just using the basics. This leads to bloat, performance issues, and a whole raft of complications that really do not need to be there.
To be honest, this has always occurred and is not really a recent phenomenon. It does seem to be getting worse though. I believe it stems either from laziness, a lack of knowledge, or a "don't care" attitude towards performance and resource use. I think it's exacerbated by the rate of improvement in the capabilities of hardware outstripping our ability to be able to fully utilise them, and a convenience culture of just using "off the shelf" solutions/components without really understanding how they work - just to get something 'out the door' with the minimum of effort