The main point of our disagreement is NOT about skill sets but about
how you go about designing a web site to be the most effective and safe to use. I strongly believe it should be done in a way that is efficient in download, presentation, and safe to use as well, while it delivers the information or actions required of it. This means, in what I was taught and have found is best practice, is that everything for the site should be on the same server and all under the control and management of the web master. This means there is NO NEED for third party cookies or script calls, this means the site is a lot safer for the user.
However, with so many quick and easy ways of doing things by just using the work someone else has done you can create a site with lots of third party cookies, scripts, and other stuff. So instead of creating a real local website you end up with a mash-up of some sort. If you like that, well do so, but don't expect me to use it or recommend it to people as every time you leave your server to get something from another place you open the site and the user to a possible security breach.
The other main reason many people use third party services is to make money by serving up ads from Google Ads and the like. Like 99.999999% of the people in the world I go to a website to see what they have on their web site, not to see who they let put ads on the web page. I do NOT like having to pay for download of crappy ads so you, as the website owner, can make money off my visit to your site. If you want to make my use of your site harder or more costly, then you can't blame me for not returning to the site of buying from you. In the USA people may get free downloads, but the majority of the world the ISPs charge people for each megabyte of downloaded material, so any effort to reduce the rubbish like ads is very good work. Most ads come from third party services, so there's another reason for stopping all third party activity.
As I said, this disagreement is NOT about skill sets, but about how you use those skills in the real world. There is NOTHING that you can put on a website that requires a third party cookie or script call that can NOT be done by either putting it on your own server or by showing it as a hot-link with the information the user needs to make a decision to go to it or not.
BTW In regards to the Google APIs I mention I block that you seem to think so highly of, they are damn easy to download from Google and to place on your own website server instead of calling them from Google, thus eliminating the third party call and aspect of them.
