News for hackers. Stuff that matters.
Re:Ember v3.7 Released by Macha on Sunday January 13, 2019 @07:43PM (#18899721)
On a team that uses it.

It's... fine. If you know Ember, you can build a reasonable app pretty quickly. If you have a team that knows Ember and likes it, there's not going to be giant gains to switching to something newer. Certainly not enough to justify a rewrite. The integration between the framework and Ember Data is nice if you have an API that natively works by the JSON API standard that Ember Data expects. It's big selling point is it's more of a one stop shop than something like React and Vue where you have to bring your own data layer and router etc.

However... if it was up to me, I wouldn't use it again:

If your API doesn't emit JSON API, expect to write a lot of serializer/adapter code.

The Ember object model breaks browser debugging (and no, the Ember Inspector doesn't make up for it, you can't dig down into objects there, the best you can do is send it to $E, then manually issue $E.get() calls). You end up looking in foo._internalModel._data to get a decent look at what the data actually is.

The build tools are slow. Broccoli still cannot output sourcemaps which map back to real source.

The framework has strong opinions about app layout, based on Rails. It groups by concept. So you have folders for models, controllers, components etc. While you can nest within it (so you can have controllers/my-feature/{a,b}.js and components/my-feature/{c,d}.js), it still ends up with your code for a feature all over the place. I'd much rather have my-feature/{controllers/{a,b},components/{c,d}}.js and have all code for a feature in one place. Pods were supposed to fix this, but have been abandoned.

The public API is too prone to spitting out objects that only have private APIs. e.g. look at adapter.createRecord (https://emberjs.com/api/ember-data/3.7/classes/DS.Adapter/me...) . You get based the data in a DS.Snapshot. What public supported actions are available with a Snapshot? (None: https://emberjs.com/api/ember-data/3.7/classes/DS.Snapshot). RecordArray in the past was similar, as were the factory and transition APIs.

Because of the above point, many popular addons are tied to APIs that are considered internal and prone to breakage. This means while the Ember team advertise "Just follow the deprecations, you can update with ease", you really can't. Your addons will break and will need to be updated in parallel and if they've updated their APIs at the same time, you're kind of SOL.

Re:Ember v3.7 Released by froglegs on Sunday January 13, 2019 @09:29PM (#18900162)
What version are you on? Aside from existing “pod” structure, the newer module unification feature follows a structure more in line with what you describe.

Which addons are problematic? I don’t doubt they exist but seems like any large/complex framework will suffer that problem. EmberData is a separate project from emberjs core.

How does vue+vuex+vue router or equiv react setup avoid same issues?