@@ -44,12 +44,29 @@ <h1>JavaScript</h1>
4444< h2 > Why is JavaScript necessary?</ h2 >
4545< p > JavaScript executes in the client and enables dynamic content and interaction
4646that is not possible with HTML and CSS alone. Every modern Python web
47- application uses JavaScript on the front end. The trend towards richer client
48- experiences will increase as projects such as
49- < a href ="https://angularjs.org/ "> Angular.js</ a > ,
50- < a href ="http://backbonejs.org/ "> Backbone.js</ a > , and
51- < a href ="http://emberjs.com/ "> Ember.js</ a > continue to mature.</ p >
52- < h2 > Where did JavaScript originate?</ h2 >
47+ application uses JavaScript on the front end. </ p >
48+ < h2 > Front end frameworks</ h2 >
49+ < p > Front end JavaScript frameworks move the rendering for most of a web
50+ application to the client side. Often these applications are informally
51+ referred to as "one page apps" because the webpage is not reloaded upon every
52+ click to a new URL. Instead, partial HTML pages are loaded into the
53+ document object model or data is retrieved through an API call then displayed
54+ on the existing page.</ p >
55+ < p > Examples of these front end frameworks include:</ p >
56+ < ul >
57+ < li >
58+ < p > < a href ="https://angularjs.org/ "> Angular.js</ a > </ p >
59+ </ li >
60+ < li >
61+ < p > < a href ="http://backbonejs.org/ "> Backbone.js</ a > </ p >
62+ </ li >
63+ < li >
64+ < p > < a href ="http://emberjs.com/ "> Ember.js</ a > </ p >
65+ </ li >
66+ </ ul >
67+ < p > Front end frameworks are rapidly evolving. Over the next several years
68+ consensus about good practices for using the frameworks will emerge.</ p >
69+ < h2 > How did JavaScript originate?</ h2 >
5370< p > JavaScript is an implementation of
5471< a href ="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/JavaScript_Overview "> the ECMAScript specification</ a >
5572which is defined by the
0 commit comments