Anyone who has ever tried explaining technical jargon to someone who is not well-versed with the terminology is aware of how difficult the explanation process can be.
Simplified JavaScript Jargon, as the name suggests, is an attempt to cure the above mentioned problem. Basically, it is a community driven exercise that explains the buzzwords related to JavaScript in simple words.
In other words, Simplified JavaScript Jargon is a glossary that you can refer to, when you need to figure out the meaning of JavaScript terminology in simple language.
To help you get a better idea, here is how it describes some of the major terms:
- AJAX: a technology for asynchronous HTTP requests.
- AMD: a standard defining how to load JavaScript libraries or modules asynchronously.
- AngularJS: a structural framework for dynamic web apps.
- Babel: a JavaScript transformation toolkit which started as an ECMAScript 2015 / ES6 code translator (transpiler).
- Backbone: a structural framework for dynamic web apps.
- Bluebird: a fully featured Promise library with focus on innovative features and performance.
- Bower: a package manager for front-end dependencies.
- Broccoli: a fast and reliable asset pipeline.
- Browserify: a tool making possible to use the require function from Node.js within the browser.
- Brunch: a tool focusing on the production of deployment-ready files from development files.
- Canvas: an HTML element for graphic applications in 2D or 3D.
- Chai: an assertion library used with a JavaScript testing framework.
- CoffeeScript: a language that compiles into JavaScript.
- CORS: a way for a server to make things accessible to pages hosted on other domains.
- CouchDB: a NoSQL database with JavaScript as query language and HTTP as API.
Need more? Check it out over at GitHub, and if you wish to contribute, simply open a pull request to complete, update or fill in a given section.
Good idea, yet the simple words are still 80% high tech buzzwords. Asynchronous? Libraries? Framework? Average people do not even know what a http request is. For them libraries are for books.
I cannot possibly up-vote or support this comment enough. None of this is simple to anyone who isn’t a programmer, or who hasn’t at least worked with them.