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 :)
-
-
4: I think people have a sense that we could just do what browserify would have done, which is definitely possible. I'd feel much better about it if someone wrote up an RFC at least exploring these questions.
-
5/5: fwiw, almost the entirety of why wrapper packages are needed in Ember today is because there is no persistent, long-lived defacto standard about these questions. We could live with whatever, I think, if we at least explored the questions and had answers.
-
(I hope this doesn't come off as dismissive or stalling; I'm hoping to unlock some effort by writing down what thorny issues have made this hard to do historically)
-
Oh, and if the answer to any of the above is configuration: - let's design the config - we'd need to deal with how dependencies are supposed to deal with their own dependencies.
-
I'd also take near-term incremental improvement ideas.
-
Can we copy webpack? (Not all of it, just talking about their approach to all of the above)
-
If we wrote down the answers to the above, and the answer wasn't "webpack implementation details" then absolutely. Webpack's implementation details are in many ways the 2017-era defacto standard, so if we document it and use the same strategy, +1.
-
But "just copy webpack" is not an RFC :)
- 10 more replies
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.