Short version: We are still learning from the community because they adopt Octane and will not recommend Octane as the default Ember mode in Ember 3.14. You can continue to opt-in to Octane in Ember 3.14, and the developer experience for doing so is constantly improving.
Octane feedback is positive
Since Ember 3.13, Ember developers can choose to join Octane.According to their own estimates, some developers have Ship the Octane application to the production environment! As expected, this led to a lot of feedback from the community.
The feedback on the new programming model has been largely positive.
Not a new application, but @Talkie The past few months have been gradually turning to Octane. As of this week, we are running Glimmer components in production.I paired up with many colleagues this week, most of them from @reactjs. Octane is exciting!
— Gavin Joyce (@gavinjoyce) October 5, 2019
Ember 3.13 provides full functionality for Octane in the core framework. 3.13 contains all the functions required by the application to use the Octane programming model. Most developers who use Octane can safely become early adopters.
We hope to be ready recommend Octane number All Ember 3.14 users, after eliminating the error, ended the work of the Ember checker, focused a lot of energy on the documentation, completed code modifications, and helped the plug-in ecosystem to provide a good experience for Octane users.
Ember contributors answered the phone and greatly improved Octane’s polishing level.
However, there are still some remaining issues that mean that 3.14 will not meet our expectations of Octane MVP.
Decoupling jQuery removed
Since 3.13, one of the most consistent feedback we have received from users is that disabling jQuery integration was an unexpectedly difficult part of their migration.
Initially, we thought the migration process would be simple.Developers should be able to adopt
@ember/jquery The plug-in serves as a transition tool.
For various reasons, the truth is more subtle than that, and the removal of jQuery has dominated the conversion process for many users.
because there’s none Technical The reason for combining the removal of jQuery and Octane integration, We decided not to require the Octane application to disable jQuery integration. This requirement change has been implemented since version 3.14.0.
Complete inspection work
Ember 3.13 released a new debugging API, allowing Embers inspector Glimmer components (and any components that use a custom component manager) are displayed in the component pane.
However, the existing code in the inspector ended up being more difficult to process than expected, and the integration of these new debugger APIs has not yet been completed. The checker is a key tool for new Ember developers to learn the framework, and we think this part of the Octane story is incomplete.
The documentation is probably the most important part of Octane. If we do not have clear documentation on the Octane programming model, developers will encounter difficulties in constructing their own framework thinking.
Before EmberConf (March last year), we had been working on updating the documentation with the new Octane idiom. The learning team led the work, and the people on the framework team provided a lot of extra work. From top to bottom, the guide and API documentation are kept up to date with the new idioms.
In other words, we still have some things to do.
First of all, the current API documentation does not include
@glimmer/componentThe learning team is actively working on this work and should be completed soon.
Second, although the template and component guides have been updated with the latest Octane idioms (thanks Chris H Garrett!), the current preview guide does not fully adopt the teaching method of the new programming model. People are actively working to provide a starting point that is more consistent with Octane, but it is not fully prepared yet. This should also be done as soon as possible.
If you have tried Octane in Ember 3.13, please continue to use it. The functions that make up Octane are now stable, which means they come with semantic version control to ensure that any Ember function is available.
If you wait until Ember 3.14 to try Octane, then do so only if you are willing to accept the Octane version that the Ember team considers to be incomplete recommend It’s pretty good for all users. Ember 3.14 is a good time for adventurous users to try to update their production application to Octane and report any issues you find.
Swing and miss
We said that we would like to recommend Octane to all users of 3.14.
Missing this goal is disappointing, But the correct use of Octane is the most important thingIf we decide to recommend Octane in Ember 3.14, or postpone the release and promise to release it within a few weeks, we will run the risk of making the Octane experience not as we had hoped.
This will frustrate the entire effort.
forward! Let’s make the shipping version of Octane as amazing as we know it.