I mostly agree, but we shouldn't forget the importance of 'coding for the present'. If an external service fulfils the current requirement and is cost effective then not adopting it due to speculative fears for the future maintainability of your application may increase your time-to-market and risk the success of your application.
Of course it's never black-and-white, but a balanced view of a service and it's immediate and potential future impact of your application is important in these decisions.
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.
I mostly agree, but we shouldn't forget the importance of 'coding for the present'. If an external service fulfils the current requirement and is cost effective then not adopting it due to speculative fears for the future maintainability of your application may increase your time-to-market and risk the success of your application.
Of course it's never black-and-white, but a balanced view of a service and it's immediate and potential future impact of your application is important in these decisions.