Here are some of his claims and my feelings on them:
They’re a hack.
Sure they are, but so is most of the Internet. I’d consider
Given that an overwhelming number of overwhelming number of sites that are likely running PHP or some other “dynamic” hosting setup, these least common denominator solutions just feel wrong.
At the end of the day, this is about cost saving, and using your infrastructure wisely. Generating a page for each pageview, or once per 1,000,000 pageviews is something that at the end of the day has to be analyzed from a business standpoint.
I’m personally a fan of dynamic sites, but understand the need for static content. I personally feel it’s a delicate balance, often dictated by the business at hand, and the requirements of the project.
<noscript> solution. But it’s well known, so people implementing it accept this. I’d say the damage here is minimal as most of the content in JS Widgets are syndicated content littering the web and don’t have much benefit for searching. Does anyone here feel upset that those annoying, yet popular snap.com popups aren’t google searchable?
Remember, in Firefox 2.0:
Hard to skin.
This is mostly intentional on behalf of the provider. It has two purposes:
- The goal of these widgets and badges is drop in functionality. They don’t want things to break. Less the implementor controls, the less that can break. Nobody wants to hold someones hands while they get used to the code. This is a good way around it.
- They don’t want things like branding to become hidden when it’s skinned.
Implementors accept the above, because they want to quickly gain a feature without the overhead of development.
Again completely agree, but this may again be the intent in many cases (AdSense, Analytics, etc.). In most other cases, it would often fall under two possible situations:
- The site is small and the owner doesn’t really care (most blogs, and MySpace users).
Don’t work everywhere.
Again, business rules tech. Copy/Paste is the best API thus far for implementing a third party product into your own code base. Non-programmers are just as good as programmers when it comes to this API.
Do I think they are harmful? I won’t be that harsh, I think they have their place. Do I think they are often overused and abused? No question in my mind. Will that change? Not likely.