The brief model: We’re nonetheless studying from the group as they undertake Octane,
and will not be recommending Octane because the default Ember mode within the Ember’s 3.14
launch. You’ll be able to proceed to opt-in to Octane in Ember 3.14, and the developer
expertise of doing so is constant to enhance.
Octane Suggestions has been constructive
Ember builders have been in a position to opt-in to Octane since Ember 3.13. By their
personal estimation, some builders have been transport Octane apps to
manufacturing!
This has, as anticipated, resulted in substantial suggestions from the group.
The suggestions concerning the new programming mannequin has largely been constructive.
Not a
new app, however @intercom has been
incrementally transferring to Octane for the previous few months. As of this week,
we’re operating Glimmer parts in manufacturing. I spent this week pairing
with a lot of colleagues, most coming from @reactjs. There’s
common pleasure with Octane!— Gavin Joyce (@gavinjoyce) October
5, 2019
Polish
Ember 3.13 is feature-complete for Octane within the core framework. 3.13 accommodates
all of the options purposes want in an effort to use the Octane programming mannequin.
Most builders working with Octane can safely be topped early adopters.
We anticipated to be able to suggest Octane to all customers by Ember 3.14,
after squashing bugs, wrapping up work on the Ember inspector, focusing a variety of
effort on documentation, finalizing codemods, and serving to the addon ecosystem
present a superb expertise to Octane customers.
And Ember contributors took up the decision and considerably improved the extent of
polish for Octane.
Nevertheless, there are a handful of remaining points that imply 3.14 will fall brief
of what we count on from an Octane MVP.
Decoupling jQuery Removing
One of the vital constant items of suggestions we acquired from customers since 3.13 is
that disabling jQuery integration was an unexpectedly onerous a part of their
migration.
Initially, we thought that the migration course of can be straight ahead.
Builders ought to have been in a position to undertake the @ember/jquery addon as a
transitioning device.
For varied causes, the reality is somewhat bit extra delicate than that, and
eradicating jQuery dominated the transition course of for a lot of customers.
As a result of there isn’t any technical cause to couple the removing of jQuery
integration with Octane, we determined to not require Octane apps to disable
jQuery integration. This requirement change is applied as of the three.14.0
launch.
Ending the Inspector Work
Ember 3.13 shipped new debugging APIs that enable the Ember
Inspector to point out
Glimmer parts (and any parts utilizing a customized part supervisor) within the
part pane.
Nevertheless current code within the inspector ended up being tougher to work
with than anticipated, and the combination work for these new debugger APIs
stays uncompleted. The inspector is a key device for brand new Ember builders
studying the framework, and we contemplate this a part of the Octane story
incomplete.
Documentation
Documentation might be an important a part of Octane. If we do not have
clear documentation concerning the Octane programming mannequin builders will wrestle
as they construct their very own method to consider the framework.
Since earlier than EmberConf (final March), we have been engaged on updating the
documentation with new Octane idioms. The Studying Staff has led this effort,
with a variety of further work offered by people on the Framework Staff. Each the
guides and API docs are updated with the brand new idioms, from prime to backside.
That mentioned, we nonetheless have a handful of issues left to do.
First, the present API docs do not but embrace the documentation for
@glimmer/part. The Studying Staff is engaged on that actively, and it
must be finished quickly.
Second, whereas the template and part guides are up to date with the newest
Octane idioms (thanks Chris H. Garrett!), the present preview model of guides
do not absolutely embrace the pedagogy of the brand new programming mannequin. There’s an
energetic effort to supply a place to begin that’s extra aligned with Octane, however
it is not fairly prepared but. That, too, must be finished quickly.
What’s Subsequent
For those who tried out Octane in Ember 3.13, carry on utilizing it. The options that make
up Octane at the moment are secure, which implies they arrive with the Semantic Versioning
ensures any Ember function has.
For those who had been ready till Ember 3.14 to check out Octane, solely achieve this should you’re
prepared to just accept a model of Octane that the Ember staff does not really feel is
polished sufficient to suggest to all customers fairly but. Ember 3.14 is a good time
for adventurous customers to strive updating their manufacturing apps to Octane, and
report again any issues that you simply discover.
Swing and a Miss
We mentioned we anticipated to suggest Octane for all customers with 3.14.
Lacking this aim is disappointing, however getting Octane proper is probably the most
necessary factor. Had we determined to suggest Octane at Ember 3.14, or delayed
the discharge and dedicated to transport it in a number of weeks, we might have risked
having Octane be an expertise considerably lower than what we aspire for it to be.
And that might have defeated the entire effort.
Onward! Let’s make the transport model of Octane as superb as everyone knows it
might be.
