And the converse of that is that when someone spends a lot of time deliberately not learning a thing (as the author of the article seems to have done), it's understandable for them to be defensive about the utility of those things.
The author makes one fundamental error, which is the assumption that any of those things are necessary. You don't need to "create a hello world service to create the hello world factory to create the hello world sercice so you can print hello world on the screen". You can just print hello world to the screen. You can do it in the template, in the console, wherever.
You don't need layers of abstraction for simple tasks like "printing hello world", but when you have things that do need those layers of abstraction, they're there, and they're appropriate. The alternative is to write uglier code, which it seems the author prefers.
That said, I don't mean to discount preference in this debate, which many seems to have done. If it isn't to the author's taste, then cool. If he'd rather write small, pluggable modules, that's cool too. Those small, pluggable modules have their limitations though, and the author either hasn't run into them, or refuses to acknowledge that, at least for some use cases, small, pluggable modules aren't actually the best choice.
The author makes one fundamental error, which is the assumption that any of those things are necessary. You don't need to "create a hello world service to create the hello world factory to create the hello world sercice so you can print hello world on the screen". You can just print hello world to the screen. You can do it in the template, in the console, wherever.
You don't need layers of abstraction for simple tasks like "printing hello world", but when you have things that do need those layers of abstraction, they're there, and they're appropriate. The alternative is to write uglier code, which it seems the author prefers.
That said, I don't mean to discount preference in this debate, which many seems to have done. If it isn't to the author's taste, then cool. If he'd rather write small, pluggable modules, that's cool too. Those small, pluggable modules have their limitations though, and the author either hasn't run into them, or refuses to acknowledge that, at least for some use cases, small, pluggable modules aren't actually the best choice.