AJaX two steps back … really?

4 03 2005

John Reynolds
John Reynolds's Blog: AJaX: Two steps forward… Two steps back?: “So far so good, but when you look at the mechanisms that are currently available to take advantage of AJaX, a boatload of JavaScript embedded in an HTML file, you will probably experience a sickening feeling of deja vu all over again.

AJaX totally blows the idea of seperating presentation markup and code snippets. The result brings back memories of pre-custom tag JSP pages… a little puddle of HTML markup embedded in an ocean of Java code (only this time it's JavaScript).”

I don't think this is the case, actually. You can — and really should — put all your Javascript code (and CSS too) in separate files. Sometimes, most of the HTML in an AJaX application will be generated by the Javascript code, even.

And if you do it properly, you'll use HTML merely to describe the structure of your content. All the presentation issues (including layout) must be handled by CSS.

So, I don't see such a big risk of having a mishmash type of code. But I do think John has a point when he says that we need tools and frameworks. As with any new programming paradigm (there, I've said the dreaded p-word 😉 ), you start with manual tools (anyone remember editing C files with vi? ) and IDEs and frameworks start appearing later.

Advertisements

Actions

Information

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




%d bloggers like this: