Convert several old posts to markdown.

1 files changed, 32 insertions, 0 deletions

diff --git a/_posts/2008-05-01-overuse-of-ajax-is-not-good.markdown b/_posts/2008-05-01-overuse-of-ajax-is-not-good.markdown
new file mode 100644
index 0000000..11943e7
--- /dev/null
+++ b/_posts/2008-05-01-overuse-of-ajax-is-not-good.markdown
@@ -0,0 +1,32 @@
+---
+layout: post
+title: Overuse of AJAX is not good.
+tags: [ development ]
+published: true
+---
+
+I was having a nice chat with a [partner of mine](http://igorcarrasco.com)
+about this new project we're to create soon. I was spreading the word on web
+standards design and he actually agreed on the principles. He also asked my
+opinion on using <abbr title="Asynchronous Javascript And XML">AJAX</abbr>,
+stating that it would be a great tool on server performance, although it would
+affect Google indexation; all true.
+
+The thing is he wanted to use AJAX the wrong way. In other words, he wanted to
+use it all the way, including content. That really is harsh towards
+findability, according to what he said, thus it shouldn't be used on generating
+content, unless we don't actually want it to be found, of course.
+
+If you want your content to be findable, just don't use AJAX. My whole learning
+process is about optimizing content and its generation and what I know for sure
+is that AJAX is for optimizing content management and not its generation (if
+you still want to use <abbr title="Asynchronous HTML And
+HTTP">AHAH</abbr> that's your call, I respect).
+
+For example, you have a blog with regular posts. If want to insert a new post,
+you won't actually need a brand new page just to say the post has been created.
+This is the perfect example to use AJAX in which the only thing you have to
+print from the server is a single phrase, after doing the insertion in the
+database of course.
+
+And that is only one example, there is a ton more out there!