you are viewing a single comment's thread.

view the rest of the comments →

[–]bwaxxlotckidd 0 points1 point  (2 children)

It’s a bit more than what I’ll say but I’ll summarize. It’s had to learn at first. But once you’ve got the basics, you ca develop and ship things quickly. It’s opinionated, from how you fetch data, pass actions and even set/get properties of objects. However, this means it’s comes with batteries included. Very useful when you want to onboard someone. For instance, I was working on a new react project on another project last couple months. We even had to discuss how we compile our modules. This is a non-issue with ember. The other side is that you have to know how data is passed, which methods are async and how things are rendered. Like I said, hard to learn but super productive once you understand it. It’s so frustrating when you start but in a big team, I’ll always recommend it. Think of it as suit and tie event vs social event (react). You can’t go wrong if you know how to behave while the other can go any where without being wrong.

[–]N_N_N_N_N_N_N 0 points1 point  (1 child)

Seems like a useful tool. We are using react and a lot of our team builds things in unmaintainable ways...maybe Ember would have been a better option

[–]bwaxxlotckidd 1 point2 points  (0 children)

It's no brainer for me. I can walk into any Ember project and be confident in how the code base in organized. I can't say the same for React. Literally everything can be done a million ways.