# Ember.js - Octane is Here

**URL:** <https://discuss.emberjs.com/t/ember-js-octane-is-here/17349>\
**Category:** Blog\
**Created:** [December 20, 2019, 10:30pm UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349 "2019-12-20T22:30:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ember-blog](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ember-blog/32/16286_2.png) [@ember-blog](https://discuss.emberjs.com/u/ember-blog)\
**Post date:** [December 20, 2019, 10:30pm UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349/1 "2019-12-20T22:30:41Z")

</div>

Ember 3.15 is Octane! Curious what Octane means for web development? This blog post will get you oriented.

* * *
This is a companion discussion topic for the original entry at [https://emberjs.com/blog/2019/12/20/octane-is-here.html](https://emberjs.com/blog/2019/12/20/octane-is-here.html)

---

<div class="post-metadata">

**Author:** ![rajasegar](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/rajasegar/32/16575_2.png) [@rajasegar](https://discuss.emberjs.com/u/rajasegar)\
**Post date:** [December 21, 2019, 1:46am UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349/2 "2019-12-21T01:46:29Z")

</div>

Thanks for the detailed blog post, it will be really helpful for anyone who wants to start with Octane. I have a small concern. In the Glimmer components section, for the after example, we are just showing how the template will look like and in the before example, we are showing the component.js , even though the properties @isEnabled and @isActive are coming from the component I think we should also include the component.js in the after example. Otherwise this gives an impression that we don’t need component.js in Octane for new developers or someone starting with Ember.js

---

<div class="post-metadata">

**Author:** ![chriskrycho](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/chriskrycho/32/17763_2.png) [@chriskrycho](https://discuss.emberjs.com/u/chriskrycho)\
**Post date:** [December 21, 2019, 2:12am UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349/3 "2019-12-21T02:12:26Z")

</div>

In that specific example, you _don’t_ need a backing class! (The guides cover when you do and don’t in detail, so I think it’s fine not to get into the nitty-gritty here.)

---

<div class="post-metadata">

**Author:** ![OmShiv](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/omshiv/32/16852_2.png) [@OmShiv](https://discuss.emberjs.com/u/OmShiv)\
**Post date:** [December 30, 2019, 5:24am UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349/4 "2019-12-30T05:24:11Z")

</div>

Chris is right. The example (working version) doesn’t need a JS class. In fact, even the **before** part could be done without JS. I guess the example shows how convenient and apparent (official) it is using Octane.

---

<div class="post-metadata">

**Author:** ![wellington1993](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/wellington1993/32/12231_2.png) [@wellington1993](https://discuss.emberjs.com/u/wellington1993)\
**Post date:** [January 22, 2020, 2:25pm UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349/5 "2020-01-22T14:25:53Z")

</div>

Nice work!

Honestly, I didn’t like the classic version when I tried to use Ember for the first time. But now I like so much the Octane and I will try again!

Thanks!

---

<div class="post-metadata">

**Author:** ![Justin\_Hansen](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/justin_hansen/32/16945_2.png) [@Justin\_Hansen](https://discuss.emberjs.com/u/Justin_Hansen)\
**Post date:** [March 1, 2020, 4:52pm UTC](https://discuss.emberjs.com/t/ember-js-octane-is-here/17349/6 "2020-03-01T16:52:37Z")

</div>

Hey there great work with the new version of Octane. I had a question, however, about the future of ember. The 2020 Roadmap which seems very important isn’t even on the website but can be found by a Google search. This obviously doesn’t do good for folks wanting to check the website and see where ember is going. The suggestions of simplification and modernization is great. Some other links like Performance on the website start on 2013. Surely someone should be updating the website so it looks up to date.

Also, tree shaking would be a great addition to focus on in ember as well as as much support as possible for ES6 like features integrated into the platform.

Thanks!
