Skip to main content

Overweight Ajax

I came across an interesting article this morning on Ajaxian:  Ajax, Browsers, Running Out of Time.  The crux of the article is that the author's PC consistently gets bogged down if he leaves Ajax-heavy applications - such as Google Mail, Zimbra & Yahoo Mail - up for most of the day.   I can understand his pain, as i have noticed similar behavior with the new Yahoo Mail.  Sure, it's much "cooler" and easier to use than the "classic" version, but it comes with a cost.

This is why I am still very cautious and conservative when using Ajax components in APEX applications.  It's still too easy to create code that just doesn't play nice with browsers.  It's also 100% impossible to discern what else a browser is running when your Ajax component is fired up, which makes it all the more difficult to ensure that your code doesn't step on someone else's.

For better or worse, perception is reality.  If large-scale Ajax applications that the masses use degrade overall confidence in the technology, it will be even harder in the future to convince clients that even the smallest Ajax component in an APEX application is scalable, secure, and a good investment.


Anonymous said…
AJAX's days are numbered. Sooner or later, something like Adobe's Flex or Microsoft's Silverlight are going to become the norm for creating web-based applications.

Although HTML was never intended to be used for data entry, the browser makers and organizations like W3C have sat idle for far too long by not introducing native HTML widgets that would have filled the large gap that AJAX components now fill.
Carl Backstrom said…
AJAX's days are numbered. Sooner or later, something like Adobe's Flex or Microsoft's Silverlight are going to become the norm for creating web-based applications.

bah what do you work for adobe or microsoft?

the problem is you have people throwing ajax at things that have no need for it.

I use ajax everyday and carefully decided where and when to put it, when and where it makes sense and it kicks a...

proprietary formats silverlight and flex /air and truthfully xul are bad.

Why buy into in micorsoft and adobes personal little war when you can just follow web standards. Javascript and html work everywhere even your brand spanking new iphone.
Carl Backstrom said…
Not you Scott ;) my comment was for the first "Anonymous" commenter.
Scott said…
I'm going to have to agree more with Carl here; there will be some people who go with Adobe and MSFT, but I think that keeping with a standard, portable format is more advantageous.

Ajax is relatively young, and like most young technologies, people do stupid things with it. How many spinning, flaming Java applet logos were there in the 90s?

I also think that people will be hesitant to adopt another MSFT web "standard", for fear of some obscure dependency on IE. Remember what MSFT did to Java?

HTML is simply too common to be quickly or completely replaced, at least in the next several years.

- Scott -
mathewbutler said…
I don't have a problem with AJAX per se.

However, I'm still using the old version fo yahoo mail, and given the choice will continue to do so.

Mathew Butler

Popular posts from this blog

Whose Deck is it Anyways?

This year at KScope, we're going to try something new.  And fun.  And funny to watch - we hope.  It's called "Whose Deck is it Anyways?", and will occur on Sunday at 8:30pm.  It's only 30 minutes, but it will likely be the best 30 minutes of the conference.  Or at least the most embarrassing.

Here's what we're going to do: the will be four 5-minute presentations - one on each of the following: BI, EPM, Database & APEX.

Sound interesting?  Probably not.  We get that, too.  So here's what we did.

Each 5-minute session will be presented by a non-expert.  For example, it's highly likely that I'll be presenting on BI or EPM.

To make it even better, each slide deck will be prepared by the corresponding expert.  So again, it's highly likely that my slide deck's creator will be either Stewart Bryson or Edward Roske.  If nothing else, this session will be a crash course in how not to make cohesive, easy to read slides.

Interested now?  Ya,…

Spaced Out

A while back, I wrote about how to give the Universal Theme a face lift.  If you follow the steps in that post, the base font for an APEX application with the Universal Theme can easily be changed.

While that's all well and good, sometimes you only want to change the font for a report, not the entire page.  One of the applications that I'm building contains a number of IRs based mostly on log data.  Thus, having that data in a monospaced font would make it a whole lot easier to read.

You can search Google Fonts for monospaced fonts by selecting only that option on the right-side menubar.  You can also opt for the standard yet kinda boring Courier and achieve the same thing.

To implement this in your application, follow the steps in my other post, but stop shy of the final step.  Instead of pasting in the text that I specify, paste in the following to the Custom CSS field in Theme Roller, using the name of the font you selected for the font-family:

.a-IRR-table tr td { font-fam…


Unless you've managed to somehow filter out everything about US politics over the last few months (and if you have, please let me know your secret), then you've likely heard about "fake news".  From a high level, my basic understanding of "fake news" is that it refers to stories or websites that are fabricated to advance the political beliefs and/or ideologies of one site or the other.  Your definition may differ.

So what is fake code?  That, I can at least try to explain in a bit more detail.

The other day, I saw this image posted on Kris Rice's twitter feed:

I thought it was a joke, but it's actually a real book. That made me laugh.  Then cry.  Then I read the book, mainly since it's only 4 pages.  Believe it or not,  there's actually some really good content packed in there.  Let me summarize:

If you choose to copy code from Stack Overflow, the OTN forum, or anywhere, really, there's a few things to keep in mind:

Who owns the code.  It…