![]() ![]() ![]() These frameworks let us design our applications in a structured manner. So the need was to create SPAs in a structured manner and this created a need for JavaScript frameworks and libraries that provided some structure to single page applications.Ĭurrently, there are quite a few Open Source JavaScript frameworks available that help us solve the problem of spaghetti code. So why should we write single page apps when they lead to bad code? The main reason for wanting to create a single page application is that they allow us to create a more native-like/desktop-like/device-like application experience to the user. This led to spaghetti code and these client side HTML/JavaScript applications (Single Page Applications or SPAs) became a maintenance nightmare. But since HTML and JavaScript were never meant to be used for writing full fledged web applications, these applications had all the HTML and JavaScript code intermingled. No need for plugins like Flash and Silverlight. This led developers to write client side code using HTML and JavaScript to create rich internet applications. Creating a rich internet application became possible only using browser based client side technologies. Then came the time when browsers became more capable and HTML became more mature. The only downside of this was that the user needed to install the browser plug-in to get these applications to work. They provided the possibility of creating rich internet applications that ran in the browser. These technologies filled in the gap for all the functionality not possible with HTML. This is where browser plugin based applications like Flash applications and Silverlight applications came into picture. Web applications had no such problems because once the application is updated on the server, all users got the updated applications.īoth these approaches had pros and cons and something needed to be done to get the best of both worlds. The downside of distributed applications was that it was very difficult to roll-out and ensure the application updated across all users. The major differentiating factor for these two applications was that the distributed applications provided an interactive user experience whereas web applications provided very limited features (due to technology limitations). Web applications, on the contrary, were sandboxed in a web browser and HTML and HTTP were used to let the user perform operations on the data which is stored on the remote server. Distributed applications ran as standalone applications on the user’s machine giving him a rich user interface (desktop like experience) to work with, and behind the scenes, these applications sent data to a server. This need gave birth to distributed applications and web applications. Then came the need to share data across multiple users and a need to store data at a central location. These applications were targeted at a single user and ran on their operating systems. It was a long time ago (almost a decade back) when most software applications were getting built as standalone applications. BackBone Tutorial – Part 8: Understanding Backbone.js Events.BackBone Tutorial – Part 7: Understanding Backbone.js Routes and History.BackBone Tutorial – Part 6: Understanding Backbone.js Views. ![]() BackBone Tutorial – Part 5: Understanding Backbone.js Collections.BackBone Tutorial – Part 4: CRUD Operations on BackboneJs Models using HTTP REST Service.BackBone Tutorial – Part 3: More about Backbone Models.BackBone Tutorial – Part 2: Understanding the basics of Backbone Models.BackBone Tutorial – Part 1: Introduction to Backbone.Js.In this article, we will try to look at the basics of JavaScript frameworks and try to introduce backbone.js. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |