Building an Ember with React

Building an Ember with React.md

Building an Ember with React

Abstract

Use opinionated frameworks or use modular packages to construct the system you need? This conflict is as inevitable as Red team vs. Blue team. Let's explore this question in context of the front end web stack.

Ember is notorious for being an opinionated front-end framework while React is known for being the very lean build what you need library.

We will explore what it takes to assemble the minimum number of packages from the React ecosystem to create a minimum viable Ember.

Details

The first time I personally encountered it was Sinatra vs. Rails. Since then I've been reasonably mindful of when to go modular and when to go opinionated (Although I've messed this up a number of times).

This talk will detail what it takes to build a Minimum Viable Opinionated web framework.

The pieces we will for sure cover:

• Routing
• Build tooling
• Testing

The pieces I would like to cover:

• Resolver
• Computed properties
• Adapter / Serializer

Pitch

This talk will help the audience quickly become aware/more knowledgeable of: the front-end stack (i.e. a full architecture approach to SPA's), React, and Ember.

It will also help people evaluate critically choices they are making for their front-end libraries and frameworks.

As someone who has worked with both React and Ember, as well as someone who works on very large javascript applications, this is something I would be very passionate and qualified to talk about.

• "Ember is notorious for ..." => notorious means "famous or well known, typically for some bad quality or deed", and I don't think that's what you mean to say here. That's the dictionary definition, though, and since I'm not a native speaker, in spoken language it might not have this connotation.
• "The first time I personally encountered it was Sinatra vs. Rails." => "it" seems to refer to the "framework or libraries" debate but the reference is too removed here for the "it" to need no explanation.
• I think the message of the talk is not pronounced enough. You first mention Ember vs. React as implementing opposing principles of design but then you show how to build an opinionated framework with modular libraries. If the talk means to show that there is no real contradiction between these two viewpoints, that's fine, but I think you should say this explicitly. As a side note, it'll mean that React is right, if it's easy to build up a framework by just piecing together the bits, why bother with a framework. But I might get this totally wrong.