|Hacker News, Reddit, Stack Overflow Stats|
|Why people like using this service||
|Companies using this service|
used angular on 3 projects extensively. slow compared to react but the bindings can be bliss. makes single page interactive websites a breeze.
Finally out of the RC phase with final release, Angular 2 provides us a modern web framework optimized for both developer productivity and performance. With ahead-of-time compilation, built-in lazy-loading, server-side rendering etc, it helps us in deploying fast and performant app across platforms.
Used Angular2(TypeScript) + Semantic UI for web application development
Runs the core application, ties together components with the Redux states to do lots of cool things.
The front end was built on an Angular template supplied by the client. We leveraged Angular's flexibility and speed to delivered complex matrices of data quickly and with great finesse.
We have a core angular skeleton that we use to rapid prototype custom tailored web applications.
Client Framework, integrates niceley with d3 and websockets, if you know how...
When ever I need heavy user client side apps this is my tool of choice. There are a ton of JS frameworks out there, picked this one because of philosophy they are trying to put out there and great community. Two way data binding FTW!
All of our frontend code is on AngularJS. Directives, controllers, and services really help in organizing code in order to keep things maintainable, and two-way binding makes data input easy. The large ecosystem of modules for directives is fantastic, too.
Front-end story feed. Used this in conjunction with our REST API, which is built with Django/Django REST Framework.
Among the best Front-End JS Framework Update: React & Angular2 are now leading but we are now stuck with AngularJS :-)
To build modern and powerful HTML5 web applications, cutting down both costs and time to market.
Dipping our toes in… currently using it to add enhanced functionality to specific UI components.
The whole frontend and the most analytics functions are hosted directly in the browser based on a RESTful API.
Being a large web app, we used Angular with Require JS to manage+lazy load assets and dependencies
Major part of our UI application uses Backbone models and views extensively. Though there's a plan to migrate to React and Redux.
The main web store is a Backbone.js single page web application, and so it hits API endpoints to do all the calls, and we use those same API endpoints for the consumer iPhone app, the consumer Android app, and the consumer mobile web app. It worked out really nicely, us just building one API and just all these clients, including the web client, using that.
All of our web apps are built using BackboneJS. Keeps our code clean and organized, and keeps the page refreshing to a minimum!
When the data request returns, Backbone.js gets busy. The idea with Backbone is that we render each Model that comes down from the server with a View, and then Backbone provides an easy way to:
1) Watch for DOM events within the HTML generated by the View and tie those to methods on the corresponding Model, which re-syncs with the server
2) Watch the model for changes, and re-render the model’s HTML block to reflect them
Neat! Using that general approach, we get a fairly regular, comprehensible, and maintainable client. We custom-built a client-side Model cache to handle updates and simplify client-side Model reuse.
Ember.js is still a great choice for our "ideal world" stack, but it's not as clear of a winner as it was when we picked it up. React.js has been pushing the front-end framework world forward for a while, and Ember.js has adopted some of its best ideas. However, React has begun to take over developer mind-share, which means it may be easier to hire React developers in 3 years than it is to hire Ember developers. That said, Ember allows us to expand our feature platform faster than React, and since we're still looking at "going wide" in our product offerings, it's the best choice.
Framework front-end utilizado para atingir alta produtividade e permitir organização por todo o projeto client web.