These primitives are actually public so anyone can make a transform or parser to build their own custom template import syntax. This flexibility means we can experiment using these primitives before finalizing the API. We can even iterate on it later on to find the best fit for our ecosystem.
🎤 Stuart Guthrie (@stuartg99) of Freshwater, New South Wales, Australia talked about his experience since choosing Ember four years ago as the founder of Polonious Pty Ltd. "We selected Emberjs as it was community driven, the community was well led and had a good 'vibe', still does."
🥁 Serguei Cambour (@belgoros) of Belgium talked about using Ember on side projects, having discovered Ember as a framework from his background in Ruby on Rails. The RaRwE book helped with the Ember learning curve, and he uses the Ember Discuss or the relevant channel in the Ember Discord chat to ask questions.
🎷 Aad Versteden (@madnificent) of Belgium is the co-founder and CEO of redpencil.io, a consultancy which tries to keep the web an open space. Most of their backend work is semantic.works, which heavily pushes for Ember on the frontend. Aad would like to see the community more involved in ember-animated. He's also hopeful that Embroider will bring us tree shaking. Check out the full post to read about Aad's thoughts on the pros and cons of Ember Data.