All geek questions in one place

Best AJAX Web Development Technologies

I have some experience developing AJAX, mainly on .NET and MooTools. However, I want to find out more and see what others have thought about other available options. I am looking more for tips about the front. In the end, I will most likely be encoded in .NET using C # and WCF services.

Please feel free to provide me as much information as you can. I would also appreciate any links to resources.

Parameter List (Feel free to add)

  • Write my own javascript

  • Use a frame like MooTools, jQuery, etc. Which one is better?

  • Use the Google Web Toolkit. Am I binding myself to the limitations of GWT? Or no limits?

  • ASP.NET AJAX

  • WPF (will this work not in IE browsers?)

  • Flash (it will be a pain to learn the script action)

Thanks Jaspreet

+4
source share
13 answers

Writing your own Javascript often means reinventing the wheel when it comes to trying to achieve cross-browser compatibility. Angles such as jQuery and MooTools take care of a lot of this work.

Personally, I would suggest choosing a Javascript structure or using GWT, but actually it’s just a matter of personal preference at this point, like choosing a programming language. Choose the one that best suits your goals or what you are most familiar with.

+9
source

I would go with jQuery.

jQuery will be bundled with the next version of Visual Studio. Google uses jQuery. jQuery has the largest user base of any of the frameworks out there. And speaking of not reinventing the wheel, jQuery also has the largest plugin repository of any of the frameworks out there. Including its own official user interface library, which is in constant development.

.. And if you are a fan of books; there are 3-4 books about the structure at present.

Oh yeah! Check out the Douglas Crockford site for great vanilla JavaScript tips and tricks.

Only my two cents :)

+7
source

Everyone will work with very strong code, which is usually the best way to improve your own skills. And don't forget all their extensions / plugins.

+6
source

I would recommend jQuery. It is more extensible and lightweight than most other JavaScript libraries I've seen (and you can use it on Google using the AJAX API).

For Flash-oriented web applications, AJAX Flex is the best solution.

+5
source

Since this is a rather subjective question, I will put my 2 cents.

I developed using the Dojo toolkit and found it very well rounded. However, if you do not do custom assembly in your library, it slows things down. It has a steeper learning curve than other frameworks, but it seems to sit very close to the heart of Javascript.

But this is not an advertisement for dojo. I am currently working on an Ajax web application, and my goal is to try to avoid using a framework. What for? A few reasons.

The biggest reason is complete control over the code. It's not that I don't trust toolkits, I just like my own code. I don't have code that I don't use, and all my abstractions are customizable for my purposes. From time to time, I actually reinvent the wheel *, but it is always a little different because it is created.

Another big reason is the amount of knowledge that I get. I am sure that I could take any structure much faster, because I did not use it for the project. I understand much more than before. Before it was more like a mystery bonus, and now even the framework makes more sense to me.

The thing is, if you are doing some kind of non-trivial javascript, you will have a framework (or a mess). This is actually not the fastest way to write web applications, but it is not so difficult with a little practice. You may be amazed at what creative things you can come up with, which you did not have before.

* Rethinking the wheel is a terrible analogy that we all use. We constantly invent wheels. First made of stone, then lighter wood, tires, etc. My truck does not have the same wheel as my sedan.

+5
source

Like other respondents, I prefer to use frameworks, but my favorite dojo is a clean and well-designed architecture, good books (my favorite Matthew Russel's ), and a particularly impressive approach to using browser extensions (such as Google Gears or Microsoft Silverlight) if they are installed, and gracefully rolled back (for example, to server storage on the Ajax side), if there are no suitable browser extensions (or sufficiently advanced browsers with HTML5 support).

Dojo is currently a little less popular than jquery (for example, [jquery ajax] has 8.4 million hits on Google Search, versus 4.3 million for [dojo ajax] ), but it's still popular enough that it doesn't leave soon; -).

+3
source

You should check out ExtJS .

Most of the libraries I've seen have a useful kernel, but I don't have a widget / control library that will fit into each other. Of course, you can get a huge number of controls for jQuery, but do you have time to figure out which ones are designed to work and customize the look to suit the rest of the controls? ExtJS gives you exactly that. The core is the core. It works and it works great. But a huge selection of compatible and functional controls is the main driver that will make your life easier.

I used ExtJS with Asp.Net and WCF services, and it was a really good experience overall. You will need some time to become familiar with the ExtJS component model to expand it even more (since you will need to do the same with other libraries), but when you do this, you will begin to love it even more.

One more thing: since MS sends jQuery with MVC, this does not mean that it is the best. This means that it is one of the best (and much better than Microsoft AJAX), but with the most relaxed open source license.

Edit : Now that Silverlight 3 has been shipped, it has become apparent that it will shake a bit with its offline support and graphical support. Like a standalone desktop, for example, web applications. Definitely something to consider ...

+3
source

Please note that WPF has nothing to do with ajax.

AJAX = asynchronous javascript and xml

WPF = window-only user interface display technology. The only option for use in a browser is to create Xbap. Silverlight (say, like flash, but from microsoft) is more suitable for a web colleague, so maybe you should study this too ... this is similar to using flash, but with familiar MS technologies.

As for your question about which frameworks to use with ajax: I prefer jQuery. This short syntax and chain allows you to achieve your goals in a very fast, intuitive way.

In addition, GWT is a Java framework that also provides client information as far as I know. This way you will have a limitation of Java as the base language ...

+2
source

Over the past 7 months, the GWT has made significant leaps. The multiple libraries of the GWT widget have received a lot of attention, and Google’s work in the library is impressive. Switching to GWT limits you:

  • Using GWT widgets
  • May become a developer of the GWT widget

Benefits:

  • Java coding
  • Debugging in Java
  • Skipping parts of JavaScript that make you pull your hair.

GWT is a step beyond AJAX. It embeds HTML / JavaScript, so you don't need to deal with it, but it also provides access if you want to deal with it.

In general, you will spend less time getting the little things to work, and more time adding an amazing application.

+2
source

there is also prototype.js

+1
source

Select a library to find out, and then pick up the rest, but I don’t think I invented the wheel.

I chose MooTools and have since taken jQuery / Prototype. (Picked Mootools, because their site, at that time, was the only one that passed the test, realized that pure html means pure javascript).

MooTools Side Note: An often overlooked feature of MooTools is the bootloader. You can download enough source code to make AJAX work, and nothing more.

0
source

There's an open source BBC javascript library called Glow

0
source

Source: https://habr.com/ru/post/1285722/

More articles:


All Articles