EmberConf 2017: State of the Union
emberjs.com
EmberConf 2017: State of the Union
1–10 of 21 posts
Re: EmberConf 2017: State of the Union
#2A great read that recaps the history of Ember, what helped it stand out from the crowd in the past, and what worked and what didn't, segueing into the introduction of Glimmer.js, a standalone UI component library extracted from Ember 2.10. Congrats to Tom, Yehuda, Godfrey, and the rest of the Ember Core Team! Looking forward to another productive year.
Re: EmberConf 2017: State of the Union
#3I was playing with glimmer.js, it feels like you can now "NPM your way to a full app" similar to the react eco system (if you're into that sorta thing).
Re: EmberConf 2017: State of the Union
#4I hope they start making TypeScript a first class citizen in Ember, just as they have done with Glimmer, it really makes development so much easier, hopefully with .get() and .set() going away it will make it easier for the typescript compiler to figure out what is mutating what.
Re: EmberConf 2017: State of the Union
#5I hope they start making TypeScript a first class citizen in Ember, just as they have done with Glimmer, it really makes development so much easier, hopefully with .get() and .set() going away it will make it easier for the typescript compiler to figure out what is mutating what.
There was a lightning talk on TypeScript at EmberConf that also gave a status update on how TS and Ember work together:
* https://www.youtube.com/watch?v=ZCHFjGSCqP4&feature=youtu.be...
It looks like full support could be landing soon. I know TS 2.2 added flexible enough class modeling to handle Ember's object system: https://blogs.msdn.microsoft.com/typescript/2017/02/22/annou...
Of course we're attacking that from the other side as well, and experimenting with native ES classes in Glimmer.
Re: EmberConf 2017: State of the Union
#6I hope they start making TypeScript a first class citizen in Ember, just as they have done with Glimmer, it really makes development so much easier, hopefully with .get() and .set() going away it will make it easier for the typescript compiler to figure out what is mutating what.
There was a lightning talk on TypeScript at EmberConf that also gave a status update on how TS and Ember work together: * https://www.youtube.com/watch?v=ZCHFjGSCqP4&feature=youtu.be... It looks like full support could be landing soon. I know TS 2.2 added flexible enough class modeling to handle Ember's object system: https://blogs.msdn.microsoft.com/typescript/2017/02/22/annou... Of course we're attacking that from…
<3 mixonic, thanks for the reply, I was scouring the repo / blog for any word on typescript support, this looks promising.
Re: EmberConf 2017: State of the Union
#7GlimmerJS is going to be amazing. I can't wait to check it out soon.
Re: EmberConf 2017: State of the Union
#8Yes! Ember is a really awesome framework, when coming from the likes of Django where there is a blessed version of everything you need (like a router, file layout, template language etc) it's really nice for those to all be included.
This post hits the nail on the head with Embers problems though, and it does seem like it's been left behind a bit in terms of using the latest and greatest tools. For example migration to Babel 6 from Babel 5 is only just finishing for the core components. get() and set() are also not so nice for newcomers.
As the post highlights this is mostly due to the projects age and baggage Ember carries. I see this as a positive though, Ember is pretty damn mature and well thought out, even if it's lacking in some syntactical sugar (and sometimes the latest and greatest in JS libraries/tools is such a fast moving target that it's just not possible to track it).
The future is looking bright for Ember! Well done!
Re: EmberConf 2017: State of the Union
#9Glimmer looks awesome! Is it easy switch out handlebars for some other templating language?
Re: EmberConf 2017: State of the Union
#10[deleted]