Do built in garbage collectors produce lazy developers?
Or does it help programmers to focus on more important ideas?
Sonic I quite often jokingly say, "I created some program or library or reusable code because I'm lazy." What I'm really saying is I favor efficiency, maintainability, extendability, productivity, readability, agility, deliverability speed, etc over performance, troubleshooting memory leaks and other hard to reproduce, nuanced issues, and verbosity in code. This is the case 99% of the time. C++ would still be utilized the rest of the time when performance and being closer to the hardware are the primary concern. Ultimately, garbage collectors don't make developers lazy. It simply frees them up to be more productive with developing features rather than explicitly managing memory 100% of the time.
It depends on how you define "lazy"
It's a great question, don't know if I have the answer. However, I can tell you with languages like Python, people like me can produce scripts to help solve business related issues and automate tasks within the public and private cloud. In my work, leaders are constantly changing scope, so Python is great to produce working code or demonstrate the possibility of automation. Also, it allows me to remain agile when leadership decides to change task or trash projects because it does allow me to focus on the objective in order to produce results. I hope that makes sense 😁
Does the possibility to define functions produce lazy programmers?