JavaScript for Line of Business Applications
596.1K views | +0 today
Follow
JavaScript for Line of Business Applications
Keeping track of current JavaScript Frameworks that help design your clientside Business Logic Layers.
Curated by Jan Hesse
Beam to my Inbox:
Your new post is loading...
Your new post is loading...

Popular Tags - Filter using the Funnel

Current selected tags: 'Backbone.js', 'Meteor'. Clear
Scoop.it!

Two-Way Data Binding

Two-Way Data Binding | JavaScript for Line of Business Applications | Scoop.it

Let’s build a temperature converter app in Backbone, React, Angular, Meteor and vanilla JavaScript.

Vanilla JS is our baseline. Input values are synchronised using two event handlers, one on each input field.

Jan Hesse's insight:

https://news.ycombinator.com/item?id=7887852

No comment yet.
Scoop.it!

Choosing a JavaScript MVC Framework

Choosing a JavaScript MVC Framework | JavaScript for Line of Business Applications | Scoop.it

So you love the way single-page apps like Gmail and Trello feel, but aren’t sure where to start.  Maybe your JavaScript code has become disorganized enough that you are convinced to try one of the numerous  JavaScript MVC libraries/frameworks on your next project but aren’t sure which one to choose.  I’m writing  a book on single-page apps so I’ve pretty much “read the internet” on the topic.  I’ll attempt to provide some not so obvious insights to help you make your decision.

The frameworks discussed are the ones with the most traction at present AngularJS, Backbone, Ember, and Knockout.  Batman, CANjs, Meteor, and Spine are also mentioned but not covered in-depth.

Each project is examined from several different perspectives including community, leadership, maturity, size, dependencies, interoperability, inspiration, philosophy, and features.

No comment yet.
Scoop.it!

Rich JavaScript Applications – the Seven Frameworks (Throne of JS, 2012)

Rich JavaScript Applications – the Seven Frameworks (Throne of JS, 2012) | JavaScript for Line of Business Applications | Scoop.it

* For many web developers, it’s now taken for granted that such client-side frameworks are the way to build rich web apps. If you’re not using one, you’re either not building an application, or you’re just missing out.
* There’s lots of consensus among the main frameworks about how to do it (Model-View-* architecture, declarative bindings, etc. — details below), so to some extent you get similar benefits whichever you choose.
* Some major philosophical differences remain, especially the big split between frameworks and libraries. Your choice will deeply influence your architecture.

* Progressive enhancement isn’t for building real apps.
* Model-View-Whatever.
* Data binding is good.
* IE 6 is dead already.
* Licensing and source control.
* Libraries vs frameworks.

The technologies — quick overview:
* Backbone
* Meteor
* Ember
* AngularJS
* Knockout
* Spine
* Batman
* CanJS

No comment yet.