Vs.

Comparing Ember Octane vs React w/ hooks

Ember vs React Cheatsheet

Ember is known for its convention over configuration approach, which makes it easier to set up a new project quickly. Ember also provides more out-of-the-box functionality than React. On the other hand, React is more flexible and lightweight, making it easier to integrate with other libraries and frameworks.

Introduction

Generating a new project

React is not as much of a framework as Ember, the examples below are shown with a minimal React setup. If looking for a full featured framework with React, try Nextjs. These examples will work in Next as they only focus on core component features.

When starting a new poject in ember we can use the ember cli tool. In react there are many tools that are used to create new react projects. For this we can use Vite, a bundler that includes a lot of the same tools the ember cli does: dev server, auto reloading, bundler and compiler/build tool.

Ember

ember new project-name --lang en

React

npm create vite@latest project-name -- --template react-ts

Dev server

Both Ember and React typically will have the same development server command, verify in package.json or documentation.

Both

npm run dev

Creating components

In ember, we use the ember-cli to use generate new component and other entities. React by default doesn't have a generator or a cli tool, we can create the files manually.

Ember

ember generate component my-component

React

# component filename convention is CapitalCamelCase
touch src/components/MyComponent.tsx

Directory structre

In ember, we have two files to represent a component: the js file and hbs file. If not using pods then we have two files co-located in the same location. React has one file per component (jsx).

Ember

app/
  components/
    my-component.hbs
    my-component.js

React

src/
  components/
    MyComponent.jsx  
    # (or .tsx for typescript)