Skip to main content
added 106 characters in body
Source Link

Is all of this k3wl AJAX really needed? What really gets me is comments. Surely, surely, surely, the comment text is small and the show comments could just unhide the HTML, or insert the text from an embedded string. At the moment, there is a pointless, irritating wait whilst a server round-trip is performed. It takes more than 50-100 ms and is therefore evil.

(Just don't get me on the subject of Slashdot, Twitter, etc., retardedwith AJAX turning the UI to treacle and being unreliable AJAX.)

**Edit: I must have had a bad day. It's been reasonably fast for years. **

Is all of this k3wl AJAX really needed? What really gets me is comments. Surely, surely, surely, the comment text is small and the show comments could just unhide the HTML, or insert the text from an embedded string. At the moment, there is a pointless, irritating wait whilst a server round-trip is performed. It takes more than 50-100 ms and is therefore evil.

(Just don't get me on the subject of Slashdot, Twitter, etc., retarded and unreliable AJAX.)

Is all of this k3wl AJAX really needed? What really gets me is comments. Surely, surely, surely, the comment text is small and the show comments could just unhide the HTML, or insert the text from an embedded string. At the moment, there is a pointless, irritating wait whilst a server round-trip is performed. It takes more than 50-100 ms and is therefore evil.

(Just don't get me on the subject of Slashdot, Twitter, etc., with AJAX turning the UI to treacle and being unreliable.)

**Edit: I must have had a bad day. It's been reasonably fast for years. **

edited tags
Link
Jeff Atwood
  • 311.4k
  • 107
  • 889
  • 1.3k
edited tags
Link
Jeff Atwood
  • 311.4k
  • 107
  • 889
  • 1.3k
made a feature request
Link
Kyle Cronin Mod
  • 37.9k
  • 10
  • 89
  • 152
Loading
Source Link
Loading