Frameworks have been in focus lately because of the integration of jQuery to Microsoft. Because of jQuery’s feat (and also of Microsoft), frameworks were largely talked about again and compared.
Unfortunately there are times wherein a developer would stand up and say the framework is better than the other and that would cause a rift between developers.
Conflict might lead to better things but conflict because of competition without knowing the capability of the other is a bad thing. Frameworks are not there to stare down at each other.
These frameworks were created to provide a solution to a specific problem. Since each developer has a different problem, the solution (framework) is also different. There are powerful frameworks, but none of them could provide the answer they need.
Getting Out from the Framework
Developing a highly efficient Ajax based application is all about harnessing JavaScript. Without any prior knowledge of JavaScript, development of an Ajax based application will not be successful. Frameworks will still require developers to learn the basics of JavaScript syntax.
That is why budding developers scour the internet most of the time to find the answer of the specific question. Their research is usually focused on what they need to figure out JavaScript. Fortunately, Ajax has great following from different developers and the answer to almost any question regarding JavaScript is found online.
But that does not mean that mining what you know from different sources while harnessing Ajax should only be implemented for developers personal gain. As developers gain experience and knowledge in building Ajax based applications, they should slowly get out from framework and learn JavaScript.
Although this could be unimaginable given the magnitude of the programming language, developers do not want to be constricted by the framework. Slowly, they will look for ways on how to reconfigure the application and/or website.
Eventually, they can just look back to the days where they use frameworks extensively in developing an Ajax based application.
Leaving a Mark
Aside from “graduating” from frameworks for Ajax based applications, developers should also move forward from mere manual coding to sharing their knowledge. Everyone has to start somewhere and everyone only improved when they were able to gain knowledge from other developers who are more than willing to share what they know.
If everyone ends up keeping what they know, powerful frameworks such as MooTools, jQuery, Prototype and others will never be possible. The current state of Ajax is never the same if developers never share what they know without any strings attached.
Ultimately, developers have to build Ajax based applications with codes that could be reused. They are not just building an application but creating patterns that will be reusable in the future.
These codes should not only be reused for personal gain but also for the development of the entire Ajax community and their users. Who knows? You might be working in something groundbreaking.
Your use of Ajax can start with frameworks but you should move forward in looking for ways to harness JavaScript and share what you know with the world.
Ajax Projects
