Ajax
In a site wandering, found this link, went to stroll around, feel very interesting, we can also go to see, regardless of whether you agree with the views of the inside, to see others look at the angle of Ajax, which is helpful to understand a thing.
Here's what I think about some of the flaws:
Ajax for Ajax (Using Ajax for the sake of Ajax.)
Quite agree with this, when the survival of a technology itself because of its own bright spots are obliterated, do not know whether this technology is lucky or unfortunate.
Took out the back button (breaking the "")
The Back button is an important feature of a standard Web site UI. Then, the Back button can't work well with JS ...
Gmail seems to be doing well? But did not go carefully to see how Gmail to achieve back and JS compatible, by this mistake a reminder, perhaps this is a UE of the incision Oh.
No visual hints were provided when clicked (not giving immediate visual cues for clicking Widgets)
...... Perhaps I did not understand, think the writing this paragraph contradictory. He said he didn't provide visual cues, but took the red tip in Gmail's upper right corner as an example.
Blocking offline users outside the door (leaving offline people behind)
See the title is clear, but I have reservations, the Web application and offline browsing itself seems to exist contradictions, to integrate, may have to move a lot of brain
Don't keep me Waiting (Don t make me wait)
However, Ajax itself exists if the client's bandwidth is not enough, its display will be a mess of the problem, which is its congenital defects, but also its rise of the congenital factors-due to the speed and bandwidth of the growing, so that the server and the client frequent communication possible.
Explicit delivery of sensitive information (sending sensitive information in the clear)
Using JS to pass data, it seems that there is the risk itself, before I find the objection, I tend to agree with this--https agreement except.
Suppose that Ajax development is a single platform for development. (assuming AJAX development is single platform development)
The author of the view is that Ajax because it must be compatible with multiple browsers, and can not do only need to encode the standard JS on the line, but also to consider the problem of various browsers ... This is a JS problem, and Ajax relationship is not it?
Forget the possibility that many people are using the same application at the same time (forgetting that multiple people might being using the same application at the same)
Well, this is actually a synchronization problem, in the B/s system this is a troublesome problem ... Of course, maybe it's not troublesome to do a bit of marking to solve it?
Too much code to slow down the browser (Too a bit code makes the browser slow)
Uh...... Agree with this, although the code optimization will have a great improvement, but JS itself slow to run this flaw will still become a bottleneck.
Don't plan to have users who are disabled or without JS (not have a program for those who does not enable or have JavaScript)
Uh...... I am on the page with Ajax when ready to give up these users, I do not have Google so idle, as two sets of systems, a set of Ajax, a set of pure pages. However, it is necessary to develop a good coding habit, for example, do not directly set href= "javascript: ..." in hyperlinks and use onmouseup or onclick to trigger events, and occasionally think about others. And I can not guarantee that my JS program in all the browser.
Changing page flicker and change (blinking and parts of the the page unexpectedly)
I have not experienced the harassment of blink tags in previous web pages, so I'm a bit confused about the author's aversion, and I think refreshing a page after a proper hint is always more comfortable than refreshing the entire page.
Can't send a hyperlink to a friend and a collection (not using link I can pass to friends or bookmark)
Hey, this is the point I mentioned above, if the coding habit is good enough-and time enough, in the hyperlinks for non-JS users and JS users to provide two sets of programs is feasible.
Bulk operations caused by synchronization (asynchronously performing batch operations)
The author's meaning is to say that Ajax once had to do a few times to do the operation of the first time, and cause he can not track each element changes, can not backtrack, uh ... Maybe there is such a demand. But it seems to be a solution, right?
Cause the page to scroll and let me get lost (scrolling the page and making me lose me place)
The author thinks that inserting text into a page causes the page to scroll, and let it lose direction, I have not seen such a disgusting effect, can not evaluate, but I for some Ajax navigation is not satisfactory, I often lost in some Ajax programs and do not know where I just last step to where ...
Invented new UI habits (the inventing new UI conventions)
Oh, the author used a sentence to describe this shortcoming: "Click on an inconspicuous dongdong to produce an inconspicuous result." This induction is full of accurate, in many AJAX programs, the user is completely as a blind person, in the shaking Soso Touch This Ajax program elephants, in a blind spot in the wild and dragged in a hurry after the use of this program. But in other words, the first web page is not the same? Without the difficulty of getting started, there will be no progress, and with enough help, it shouldn't be too hard to start anything--unless it's not intended to be useful, that's the other problem.
Stop the Reptile (Blocking spidering)
To agree with this, when I hesitate to use Ajax, in considering the reptile to JS of the cold, and how the crawler to understand my strange way to load the page, to parse the AJAX library seems to be an impossible thing, the reptile is not the human brain, if the crawler can match the human brain, that is, "the Matrix 4."
Character Set (Character Sets)
Ajax itself is less support for character sets, this ... Set it up as a utf-8, but the author finally said so.
Use hyperlinks to change status (changing state with link (get requests))
The authors believe that the mainstream AJAX applications are working in Get mode, which violates the W3 recommendations for Get and post methods ... I Shaojianduoguai, mainstream Ajax apps I don't see how, I don't know if I really use GET, although Ajax code is simple with get, but does not mean Ajax can not use post it?
There are no associated changes in the other related sections of the page (not cascading local changes to other parts's the page)
Because Ajax makes it easy to control a particular part of a page, it can easily lead to too much focus on a point and lose focus on the overall layout. Well, um ... This is the problem of coding, the table is strange to the Ajax head.
Problem report (Problem reporting)
The author believes that the server-side program error, it is easy to reproduce and capture, and the client's error to reproduce the more cumbersome, um, support this, but still not with Ajax relationship ...
ROI (return on investment)
The author thinks Ajax can improve the usability of the application, but the rich client program is not much better than the pure HTML version ... Ignore this point, somebody, drag the author out, account for 50
Parody browser page jump behavior (mimicing browser page navigation behavior imperfectly)
...... Ignored, did not see the situation described by the author.