[filburt1]

Originally Posted by vbcore

I <3 Ajax

I prefer old-school, simple, reliable, accessible, functional methods. More bandwidth == bad, but stability == makes up.

Having said that, I do plan on upgrading eventually for these reasons:[list=1][*]Inevidably, security and bug fixes of all degrees will only be for 3.5[*]I am working on a site redesign and there's no sense in retrofitting it again from 3.0.x to 3.5[*]I forsee uses for the plugin system[*][high]CODE DOCUMENTATION[/high][*]Apparently more reliable thread read state marking[*][noparse] is groovy[*]Undisclosed reasons[/list]My dream vBulletin would publish its views through XML styled through XSLT without a single trace of Javascript, DHTML, layout tables, or WYSIWYG. However, most browsers don't support styled XML, nor are most web users using a browser that properly implements CSS (damn you IE), and everybody likes dynamic content (at view time) in a web page but me.

Memory leak fixes for a web page? I mean, when was the last time you could make HTML leak? Best of all, vB's .js files are among the highest bandwidth consumers on my site, surpassing all images and most of the PHP files.

Yes, the Javascript, DHTML, AJAX, WYSIWYG (all using Javascript) is cool and for an [i]application[/i], I like it. However, I do not feel such content belongs in a web [i]page[/i] which, by my definition, displays static content and should appear nearly the same as when printed as it is displayed on the screen.

In the case of web pages and AJAX, my major gripe is accessibility. [b]Users, after clicking a link on a web page, expect the browser to load subsequent content. This takes a few seconds.[/b] By switching the view instantly from a viewer to an editor, it disorients users (no, not all...) and they think that they did something wrong. It may take time to load the page for editing a message, but it's strangely reassuring to the user because they know that their action had their assumed and desired effect.

I'm apparently Amish when it comes to web design. I'm also opinionated, so :disclaimer:.

As is my policy:
[size=+1][b]EACH TO HIS OWN[/b][/size]
I respect your opinion, but not an argument based on the fact that you find AJAX and similar processes intuitive so therefore all users do. I do accept an argument where this type of technology is potentially becoming commonplace (obligitory reference to Google Maps and Gmail) and that those who are used to the common methods of web page interfaces will need to adjust.