Re:The State of JavaScript – Survey results
by lossolo on Monday October 03, 2016 @05:23PM
(#12631458)
If you are building simple app then it's really easy with Ember but you need to remember that Ember is very opinionated and if you need something that is not exactly standard or creators didn't predicted that someone would use something in certain way then you have problem and you spend time fighting with framework. I've been there, lot of time wasted fighting with Ember in corner cases but if you get this out of the equation Ember is really good and you can be really productive using it.
[ Parent
| on HN ]
Re:The State of JavaScript – Survey results
by OhSoHumble on Monday October 03, 2016 @05:26PM
(#12631483)
Yeah, I do like the convention over configuration approach. Sails is somewhat similar. Not fighting against "the Ember way" is valid advice.
However, I see this advice everywhere. When I'm googling "how do I do this in Ember" I usually get a good set of practices.
What's interesting, is there is another thread on HN about a WalmartLabs platform release that bundles React and a bunch of other boilerplate libraries a la Facebook's "create react app" and it looks really cool.
Re:The State of JavaScript – Survey results
by steveax on Monday October 03, 2016 @09:34PM
(#12632733)
We have a pretty large Ember app that consumes a variety of data from many sources (clojure services and middleware). I find I rarely have to "fight" the framework, but often have provide overrides through the various lifecycle hooks. Usually these patterns are well established and documented, but it does mean learning a pretty large API.