Create React App VS Ember-cli

• Ease of Setup
  Create React App provides a simple command to quickly set up a new React project. This reduces the time required for initial configuration.
• Zero Configuration
  The tool comes with a large set of defaults out of the box. You don't need to configure Webpack, Babel, or other build tools manually.
• Best Practices
  It encapsulates a lot of best practices for building React applications, ensuring you start off on the right foot.
• Development Server
  Includes a local development server with hot-module reloading powered by Webpack, which improves the development experience.
• Community Support
  As a Facebook-backed project with a wide user base, Create React App benefits from extensive documentation and community support.
• Testing Setup
  Initial Jest configuration is included, providing a straightforward way to start writing and running tests.
• Production Optimizations
  Built-in optimizations for production builds, such as code splitting and minification.

Possible disadvantages

• Limited Customization
  While the zero-configuration approach is convenient, it can be limiting if you need to modify the underlying configurations (Webpack, Babel, etc.).
• Monolithic
  Create React App is a single monolithic package, which can make it difficult to understand or change certain aspects without ejecting.
• Eject Complexity
  Ejecting from Create React App exposes all underlying configurations, which can be overwhelming and increase the complexity of your project.
• Dependency Management
  Because it abstracts away many details, you may not be aware of what dependencies are being used in your project.
• Less Control
  Advanced users may find Create React App restrictive as it abstracts many details and does not easily allow for deep customization.
• Performance Overhead
  For very small applications, the built-in tooling might be overkill and add unnecessary complexity and performance overhead.

• Convention over Configuration
  Ember-cli enforces strong conventions for file structure, naming, and project organization, which reduces decision fatigue and makes it easier for developers to jump between different Ember projects with minimal onboarding time.
• Built-in Tooling
  Comes with a robust set of built-in tools including a development server, testing framework integration (QUnit), asset compilation, and live reload, reducing the need to manually configure and integrate third-party build tools.
• Addon Ecosystem
  Ember-cli supports a rich ecosystem of addons that can be easily installed and integrated into projects, allowing developers to extend functionality without reinventing the wheel for common features.
• Blueprints and Generators
  Provides powerful generator commands (blueprints) that scaffold components, routes, models, and other application pieces quickly, speeding up development and ensuring consistency across the codebase.
• Stable Long-term Support
  Ember-cli follows Ember's release cycle with clear LTS (Long Term Support) versions, providing stability and predictability for teams maintaining large applications over time.

Possible disadvantages

• Steep Learning Curve
  The strict conventions and unique architecture of Ember-cli can be difficult for newcomers to learn, especially those coming from more flexible frameworks or with no prior Ember experience.
• Smaller Community Compared to Alternatives
  Compared to tools like Vite, Webpack, or CRA used with React/Vue, Ember-cli has a smaller community and ecosystem, which can mean fewer third-party resources, tutorials, and community-driven troubleshooting.
• Build Performance
  For large applications, Ember-cli's build process can become slow, and while improvements have been made with embroider, some developers still report slower build times compared to more modern bundlers.
• Rigid Structure
  The opinionated nature of Ember-cli, while helpful for consistency, can feel restrictive for developers who prefer more flexibility in structuring their applications or adopting non-standard patterns.
• Migration Complexity
  Upgrading between major Ember-cli versions or migrating to newer build systems like Embroider can be complex and time-consuming, particularly for older or heavily customized applications.

Why You Should Stop Using Create React App | React.js Todo List | Code Review #4 Part 2

More videos

No Ember-cli videos yet. You could help us improve this page by suggesting one.

• Understanding Docker multi-stage builds

  Let's start by preparing a sample application that we want to place in a Docker image. This will be a web application created using the React framework and its create-react-app tool. It will generate a code template and configuration,... - Source: dev.to / about 1 year ago

• Those Golden Era of React...👩‍💻☺️

  This project was bootstrapped with Create React App. - Source: dev.to / over 1 year ago

• You should know this before choosing Next.js

  I could totally see how you'd arrive there. Backstory: create-react was a starter boilerplate for React built and maintained by Facebook. This was when webpack was the standard and just getting a local development environment to "hello... - Source: Hacker News / over 1 year ago

View more

• Help! Why does chrome console inner text and my program inner text not return the same values? (spent nearly the whole day trying to extract an element). Turned to reddit as its always had the best community. Any help is MASSIVELY appreciated. Puppeteer!!

  The webpage is LinkedIn.com. While this isn’t a framework, I know that are using https://cli.emberjs.com/release/. Source: about 5 years ago