Ember.js vs jsf: What are the differences?

### Introduction
This markdown provides the key differences between Ember.js and JSF.

1. **Architecture**: Ember.js follows the MVVM (Model-View-ViewModel) architecture pattern, while JSF (JavaServer Faces) follows the MVC (Model-View-Controller) architecture pattern. This impacts how data is handled and processed within the applications built using these frameworks.
2. **Language**: Ember.js is primarily based on JavaScript, whereas JSF is a Java-based web application framework. Developers familiar with JavaScript might find Ember.js more intuitive, while those with a background in Java may prefer JSF.
3. **Tooling**: Ember.js includes a command-line tool called Ember CLI, which offers features like project scaffolding, testing, and deployment tools. JSF, on the other hand, relies on IDEs like Eclipse or NetBeans for development, lacking a dedicated command-line interface.
4. **Community and Ecosystem**: Ember.js has a more robust and active open-source community compared to JSF, resulting in a larger ecosystem of plugins, libraries, and resources available for developers. This could impact the ease of finding support and solutions to problems encountered during development.
5. **Client-side vs. Server-side Rendering**: Ember.js primarily focuses on client-side rendering, enabling fast and responsive user experiences. In contrast, JSF is more server-side oriented, which could affect performance depending on the application requirements and expectations.
6. **Testing Capabilities**: Ember.js has built-in support for testing through tools like QUnit and Ember CLI, allowing developers to easily write and execute tests. JSF, on the other hand, may require additional setup and configuration for comprehensive testing, impacting the development process.

In Summary, Ember.js and JSF differ in architecture, language, tooling, community support, rendering approach, and testing capabilities.