Disadvantages of Ajax-Review

Disadvantages of AJAX

Author: Anonymous Source: Unknown Release Date: 15:15:11

Decrease font to increase font size

This link was found interesting when you visited a website. You can also check it out, whether you agree or not, looking at other people's views on AJAX is helpful for understanding one thing.

The following is my opinion on some defects:

Ajax for Ajax (using Ajax for the sake of Ajax .)
I agree with this. When the survival significance of a technology is erased due to its own highlights, I do not know whether it is a lucky or unfortunate technology.

Breaking the back button)
The back button is an important feature of the standard web site UI. Then, the backend button cannot cooperate well with JS ......
Does Gmail seem to be doing well? However, I did not carefully read how Gmail implements backend and JS compatibility. I was reminded by mistake that this may also be an ue cut.

A visual prompt (not giving immediate visual cues for clicking widgets) is not provided during clicking)
...... Maybe I didn't understand it. I thought the person who wrote this section was self-contradictory .. He says no visual prompts are provided, but the red prompt in the top right corner of Gmail is used as an example.

Leaving offline people behind)
I can see the title clearly, but with my reserved opinion, there seems to be a conflict between web application and offline browsing. To integrate it, you may need to move a lot of brains.

Don't let me wait (don't make me wait)
However, Ajax itself has the problem that if the client bandwidth is not enough, its presentation will be messy. This is its inherent defect, it is also an inherent factor in its rise-the frequent communication between the server and the client is possible due to the increasing speed and bandwidth.

Explicit transmission of sensitive information (sending sensitive information in the clear)
Using js to transmit data itself seems to have this risk. Before I find my objection, I tend to agree with it-except for the HTTPS protocol.

Assume that AJAX is the development of a single platform. (Assuming Ajax development is single platform development)
The author's point of view is that AJAX must be compatible with multiple browsers, but it cannot be coded to standard Javascript. It also takes into account the problems of various browsers ...... This is a JS issue. Isn't it relevant to Ajax?

Forget that many people may use the same application at the same time (forgetting that multiple people might be using the same application at the same time)
Well, this is actually a synchronization problem. This is a troublesome problem in the B/S system ...... Of course, it may not be troublesome. Do you have to fix it by making a tag?

Too much code slows down the browser (too much Code makes the browser slow)
Er ...... Agree with this. Although it will be greatly improved after code optimization, the defect of slow running speed of JS itself will still become a bottleneck.

Users who disable or do not have javascript (not having a plan for those who do not enable or have javascript) are not planned)
Er ...... When I used Ajax on the page, I was about to give up these users. I was not as idle as Google. I made two systems, one with Ajax and the other with pure pages. However, it is necessary to develop a good coding habit. For example, do not set href ="Javascript:... "The use of onmouseup or onclick to trigger events occasionally takes into consideration for others, and I cannot guarantee that my Js programs can be used in all browsers.

Unexpected page flashes and changes (blinking and changing parts of the page unexpectedly)
I have never experienced BLINK tag harassment on the Web page before, so I am a little confused about the resentment of the author. I feel that refreshing a page after a proper prompt is always more comfortable than refreshing the whole page.

Unable to send hyperlinks to friends or Favorites (not using links I can pass to friends or bookmark)
Hey, this is the point I mentioned above. If the encoding habits are good enough-and there is enough time, it is feasible to provide two sets of solutions for non-JS users and JS users in the hyperlink.

Asynchronously batch Ming batch operations)
The author means That Ajax does the operations that originally had to be performed several times at a time, which makes it unable to track every element change and trace back ...... Maybe this is the case .. But does that seem to be a solution?

Scrolling the page and making me lose my place)
The author believes that inserting text into a page will cause the page to scroll and make it lost. I have never seen such a disgusting effect and cannot evaluate it, however, I am not satisfied with some poor Ajax navigation work. I often get lost in some Ajax programs and do not know where I got in the previous step ......

Inventing new UI conventions)
The author described this shortcoming in one sentence: "click an unnoticeable item to produce an unnoticeable result ". This induction is full and accurate. In many Ajax programs, users are completely blind, shaking and touching the Ajax program elephant, you can use this program only when you get angry and angry. But from another perspective, isn't the same for the first web page? There is no such thing as hard contact at the beginning, and there will be no subsequent progress. As long as there is enough help, it should not be too difficult to get started with anything-unless it is not intended to be easy to use, that's another problem.

Blocking spidering)
I agree with this. When I hesitate to use Ajax, I am considering crawler's influence on JS and how crawlers can understand my pages loaded in strange ways, parsing the Ajax library seems impossible. crawlers are not human brains. If crawlers can compete with human brains, they are hacker empire 4.

Character set (character sets)
Ajax itself lacks support for character sets ...... Set it to UTF-8, but the author finally said so.

Use a hyperlink to change the status (changing state with links (GET requests ))
The author believes that mainstream Ajax applications work in get mode, which violates W3's suggestions for using get and post methods ...... I don't know how to look at the mainstream Ajax applications. I don't know if they all use get. Although Ajax encoding is simple, it doesn't mean Ajax cannot use post?

Other related parts of the page are not changed (not cascading local changes to other parts of the page)
Because Ajax makes it easy to control specific parts of the page, it may also lead to excessive attention to a specific point and loss of attention to the overall layout. Hmm ...... This is the encoding problem, and the table blame Ajax.

Problem report (Problem Reporting)
The author believes that program errors on the server can be easily reproduced and captured, while client errors may be difficult to reproduce. Well, this is supported, but it is not closely related to Ajax ......

Return on Investment)
The author believes that AJAX can improve the availability of applications, but rich client programs are not much better than pure HTML versions ...... Ignore this point of view, and drag the author out, accounting 50 responsibility

Simulate the browser page Jump behavior (mimicing browser page navigation behavior imperfectly)
...... Ignore. The information described by the author is not displayed.