Disqus: http://disqus.com/ is a managed comment application to essentially take all the work out of handling comments on your website, by having a universal standards approach to handling authentication, moderation, posting and reading. Its very feature rich and enticing to use since its very easy to setup and install.
Having seen Disqus used in the jQuery API for comments and other developers I hold in high regard, I felt reasonably sure it could become a standard engine every site would use for comments. After using it during my development phase of the new Tab Developer blog, I’m not so sure. There are stability and performance problems that exist which violate the strict cleanliness and efficiency standards I’ve set for the new site. Since I would like to roll out the new blog tonight, I’m going to be keeping Disqus, but will definitely be phasing out in the next release ( 2 weeks ).
The major issues are:
- Remote resources are loaded outside of my control. When something goes wrong on their end, the perception becomes something wrong with my site. This is not an isolated fault of Disqus, but one that affects all managed applications.
- To the first point, it appears things go wrong often with Disqus. In the time I’ve been developing, I’ve had issues with # of comments being displayed inaccurately, failure to receive comments, styles not being rendered ( as if the stylesheet was never downloaded ), and an unexpected and unannounced change in layout that affected the implementation ( note: you can revert back… still annoying ).
- Graceful degradation is non-existent. With a server side custom approach I can be assured that if someone does not have Javascript enabled or if for some reason a browser does not render the Javascript due to either a parsing error or network blip, that not only will the comments still be visible, but the comment count next to the entries will be accurate as well. With Disqus everything is loaded via Javascript, so I will have a generic “View comments” link and an annoying “Enable javascript to see comments”. This is fine for probably most cases, but I prefer to call the shots with my site and I want comments visible with or without Javascript.
- My last issue with Disqus lies with performance. On a basic blog entry page, my assests/content/rendering all that jazz ends at ~200ms. Then I start to see Disqus’s loader and all its assets getting pulled in. That accounts for 2.8 seconds. 3 seconds total to finish loading a basic page with hardly any content and cached resources, is unacceptable by my standards.
As I finish my cappuccino, I’ll finish with a few thoughts. Disqus will most likely work well with reasonable expectations and non-insistent perfectionism. It is still in early stages and has plenty of time to iron network issues, performance, bugs, etc. I could also potentially use a server side caching mechanism to handle almost all my complaints above – which I haven’t ruled out investigating – but that becomes one more thing to maintain and at that point I might as well just use Django’s built in comment engine.
Were my points valid or irrelevant? Let me know what your thoughts are on Disqus.

So glad this blog is being phased out…
Upgraded the theme just now and the right bar is gone. Can’t be arsed to figure out what went wrong since the new site is going up either tonight or tomorrow, so shrug your shoulders with me and pretend it’s still there.