Why I Don’t use Ajax on my Blog
There was a time when I was the first on my block to adopt new technologies. To show you how far I go back I actually bought the video game ‘Pong‘ (no I’m not old, I’m just getting better ;-).
When I was a kid I would spend hours at the local Radio Shack store perusing their catalogues and salivating over the products. I built myself an Apple 11 Plus clone for about $700 bucks without any instructions and off-the-shelf parts (except for the EPROM of course but please don’t tell Steve Jobs because at the time I didn’t realize what ‘proprietary’ meant :).
With my first PC I was one of the few who figured out how to crack the 64K barrier (if you don’t what that means then don’t worry about it because these days we’re all crackerjacks). And when I became a blogger I created my own RSS newsfeeds from scratch before Blogger had even offered it (oddly enough I’m still getting requests for my ebook).
Right now we are going through another evolution with something that is called Web 2.0 (which is in fact a misnomer but don’t tell that to Tim O’Reilly) and leading the charge is a new technology called Ajax.
But as for me I’m struck in neutral. I’m neither for or against it. I’m just noncommittal at this time.
So why is that? Well read the following excerpt from an article I just read and I’ll tell you why:
Web 2.0 dangers:
“With Web 2.0, the functionality and experience of the sites become the primary focus, and the technology empowering the dynamic content is hidden behind the scenes to the average user. Yet the web applications underneath the polished finish remain just as complex, and add a variety of new and often unproven or unsecured technologies to the back end.
In the rush to unveil more interactive sites developers are urged to release functional sites that often lack added security measures. Attackers have quickly learned to exploit the shortcomings in these codes. This has resulted in an urgent need to audit and assess these sites for security vulnerabilities. In order for Web 2.0 technologies to reach full potential, inherent security issues must be recognized and addressed and businesses must incorporate security best practices into application development.
In addition to structural security flaws, there are also user threats including the loading of malicious content. Sites that encourage end user postings typically have no way to stop the uploading of content that might distribute malicious code to other site visitors. In similar ways, other user-driven web sites, including blogs, podcasts and social networking sites, are prone to both security and privacy issues. While it seems as though democracy has come to the Internet, more freedom means increased potential for abuse and errors.
As in our car example, the new features create new avenues for exploit. The majority of Web 1.0 users interacted with single functions on single pages. Now AJAX programming allows any given page to have dozens of features and functions, running independently as well as interacting with each other. This means a fragmentation in communication and the possibility that web application vulnerabilities that have been around for years might increase exponentially. The most common vulnerabilities include SQL injection, cross site scripting (XSS), buffer and SOAP overflow and XML attacks.” Source.
So what can a user do to safeguard their computer?
So what does that mean? If a reader should decide to turn off scripts in their browser your ajaxified blog would be rendered useless, that’s what! I’m all for “cool” and “wow”, but not when it could possibly jeopardize the very core workings of my blog.
What about SEO?
There is also the SEO issue. It is a well known fact that GoogleBot can’t read scripts and so the aspect of how well your blog will be indexed and ranked is another unknown. Unless you are a clever enough programmer to get around that fact you face the distinct possibility of becoming extinct on the search engines and sabotaging your blog’s pagerank.
On the other hand I have heard reports from those who sing the praises of Ajax but they are few and far between and expert in getting around the limitations of scripts.
A programmer has to be knowledgeable enough to know where and when to use AJAX. In the hands of the ordinary person Ajax could cause more damage than benefit, or as CyberCoder said “A tool is only as good as the person using it.”
Post Pages are Rendered Moot:
I’m a firm believer in the importance of post pages in blog design, not only from an SEO point of view but for other uses as well. Ajax unfortunately keeps readers on the main page.
I realize that by writing this post I run the risk of becoming unpopular with some of my colleagues and readers who have adopted Ajax with open arms. But regardless if you agree with the Bloke or not, you can count on the fact that I will always be honest with you and not just say what is popular.
So for me there too many issues with Ajax that tell me to use caution and wait and see how the dust settles before I decide to ajaxify my blogs. I’m not saying that Ajax is bad. What I am saying is Ajax is a technology that you need to be careful with and make sure you know what you are doing. You really need to know the risks as well as its limitations before you decide to implement this new technology on your blog.
Has your blog been ajaxified yet or are you planning to sometime soon? Or are you like me and sitting on the sidelines? I would like to know.
Filed under: blog bloke, instabloke, blogging, blog tools, blogtech, web 2.0, computers and internet, technology, tech, web 2.0, ajax, seo, blog design
What Next? Here's more from BLOGBloke: Tweet
What Next? Here's more from BLOGBloke: