It will mean that you're in uncharted territory as far as that component is concerned, and will need to do some plumbing if you're the first one to do it (or deal with leaky plumbing if you're early), but you get the benefits of the conventional structure for the rest.
-
Show this thread
-
That's also a key difference between Ember CLI and "eject". Ember CLI provides structured escape valves, so you're only ejecting a small part, keeping the conventions and shared community for the rest.
1 reply 1 retweet 3 likesShow this thread -
It does mean that the framework has to provide reasonable escape valves for the thing you're trying to do, and that won't always be true, especially if you're trying a more off-the-path experiment.
1 reply 0 retweets 2 likesShow this thread -
If you really value conventional systems and want to do these kinds of experiments, Ember is wide open to exposing the necessary hooks to give you room to experiment, and contributors will help design the hooks to keep the "ejection" from impacting unrelated conventions.
1 reply 1 retweet 6 likesShow this thread -
A lot of the time (like if you're experiment with an alternative data layer), the hooks are already in place and you can to to town. But if you value being able to do experiments more highly than shared conventions, Ember isn't the framework for you.
1 reply 1 retweet 4 likesShow this thread -
Replying to @wycats
This isn’t a complaint or disagreement, I just wanted to share a timely story from today in case you have thoughts. Ember Data’s built-in features are for remote storage. For local storage I tried ember-local-storage and ember-localstorage-adapter. I ouldn’t get either working.
2 replies 0 retweets 1 like -
Replying to @CodingItWrong @wycats
The latter hasn’t been updated in a while, and the former seems to have storage of simple values as the primary use case, the storage of models secondary. I’m sure I could get help on Slack eventually. But as a smaller Ecosystem it’s harder to find existing answers on those.
1 reply 0 retweets 0 likes -
Replying to @CodingItWrong @wycats
Of course, you can’t control the size of your ecosystem. But in React I found https://github.com/rt2zz/redux-persist … and it seems pretty active. That’s a tangible experience for me in the last few days re. ease of adopting local storage
2 replies 0 retweets 0 likes -
Replying to @CodingItWrong @wycats
I’d def be happy to work with those folks to fix whatever’s going wrong with ‘em, to contribute to the ecosystem. (Esp since mentioning ‘em publicly!) But that’s harder than dropping in a broadly-adopted package.
1 reply 0 retweets 0 likes -
Replying to @CodingItWrong @wycats
I’m having trouble summarizing this dynamic I’m getting at. Maybe it’s that “sometimes packages in a large decentralized ecosystem may still be easier to adopt to packages in a centralized but small ecosystem, due to support.”
1 reply 0 retweets 0 likes
I think it's also that conventional ecosystems have more of an onus on teaching people how to build add-ons that fit in nicely with the idioms, and we don't always do a great job at that. It's probably a theme worth considering in Ember's next phase.
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.