Polaris431
Top achievements
Rank 1
Rank 1
Polaris431
asked on 22 Aug 2007, 05:55 AM
We've been using Microsoft's Ajax for about a month now. Because it is a beta product, bugs are to be expected. The most common bug and one that caused us to switch over to Telerik's Ajax is the infamous PageRequestManagerParserErrorException error. This happens on the client side and happens randomly for no explainable reasons. It happens only on some PCs and not all. It can vanish without a trace and appear again shortly after.
In addition to this major bug, the Microsoft Ajax is a resource hog. The download time and update times are horrendous compared to Telerik's own Ajax stack. Studies posted on the Internet confirm this.
It is unfortunate that Telerik has chosen to abandon their own Ajax stack. Their Prometheus controls rely on it and it has been stated that Telerik will not invest in their own Ajax beyond a final release date of their Prometheus controls. If Microsoft fails to make their Ajax stack comparable to Telerik's and other competitors, we will abandon Telerik and purchase controls that use a higher performance stack. As it stands, one of the major reasons for ajaxifying web pages is for performance purposes and if an Ajax stack negates that performance, then it isn't worth using.
Sincerely,
Johann Blake
In addition to this major bug, the Microsoft Ajax is a resource hog. The download time and update times are horrendous compared to Telerik's own Ajax stack. Studies posted on the Internet confirm this.
It is unfortunate that Telerik has chosen to abandon their own Ajax stack. Their Prometheus controls rely on it and it has been stated that Telerik will not invest in their own Ajax beyond a final release date of their Prometheus controls. If Microsoft fails to make their Ajax stack comparable to Telerik's and other competitors, we will abandon Telerik and purchase controls that use a higher performance stack. As it stands, one of the major reasons for ajaxifying web pages is for performance purposes and if an Ajax stack negates that performance, then it isn't worth using.
Sincerely,
Johann Blake
2 Answers, 1 is accepted
0
Hello Polaris431,
We are still going to support our own ajax framework, for one more year after we discontinue it (which is still under question btw), so you can freely use it during this period and we will fix any bugs you might encounter, although it is pretty mature framework already and such are not expected. For this period Microsoft will already release the official MS AJAX as part of the new framework and Visual Studio, and all major problems are expected to be fixed.
All the best,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We are still going to support our own ajax framework, for one more year after we discontinue it (which is still under question btw), so you can freely use it during this period and we will fix any bugs you might encounter, although it is pretty mature framework already and such are not expected. For this period Microsoft will already release the official MS AJAX as part of the new framework and Visual Studio, and all major problems are expected to be fixed.
All the best,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Polaris431
Top achievements
Rank 1
Rank 1
answered on 22 Aug 2007, 07:30 AM
I highly recommend that Telerik doesn't abandon their own Ajax. It is light-weight and has been tried and tested. Only once Microsoft's Ajax has proven itself stable and has good performance like your own Ajax, would I recommend abandoning it.
Johann
Johann