If you use Ember or have used it in the past, what would it take for you to feel great about using it for your next new project (and recommending it to your friends for new projects)? Feel free to say "I'd already use it" but be honest :)
-
-
Using ember data on write or multiple read workloads is good in the simple case, but quickly becomes useless. And as your app grows in complexity updating models and having things change crossed the app causes bugs.
-
Do you prefer something like redux?
-
Well I like the one directional data flow of redux. I don't love its implementation/word choices. I prefer something akin to the Elm Architecture. (I've built in apps in all three now).
-
Can you summarize what you like about the Elm programming model? (I know elm, I specifically want to know what is appealing
) -
Msg+Data's go out of views, data comes into views. The same high level architecture of Redux.
-
I like plenty of things about Elm, the compiler, the types, the std lib, but the architecture is really productive.
End of conversation
New conversation -
-
-
On which part? :P Configuring multiple adapters or serializes by adding mostly blank files with correct names is not good.
-
Are you familiar with the (near term) plans to move adapters and serializers to add-ons?
-
Nope but that would be helpful!
End of conversation
New conversation -
-
-
I really want to love ember. But I lost more than a week on having files names wrong, or not having a file at all. With nearly useless error messages. As well as trying to use OSS packages that had bugs or were not maintained. All but one I ended up removing and rewriting.
-
Can you give some examples of where wrong filenames triggered useless errors or silent failures? I want to try to focus on an Error Message Initiative in 2018 so it'll help :)
-
I had "articles" instead of "article". So it was using the other serializer I had configured which used a Jsonapi-like serializer. That adapter would blow up with a massive stack trace on the 10% of requests that had no included items.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.