JavaScript is constantly changing. And hopefully these changes are improvements. If you've been in the JavaScript world for any length of time, you can point to those changes as examples. We can look at s5 and s6 standard. Both of these releases were huge. But because they are so big, they can become difficult to assimilate, both by programmers and by JavaScript engines.

In this movie, we're going to take a look at the change process. For ACMA script, the standard the JavaScript is based on. As we get into the process of changes, it's important to note that the evolution of ACMA script or the way that ACMA script can be changed, has changed itself. So that whole process is different. ies six was such a large release and occurred about six years after f5 that it was determined And there's got to be a better way. Since that time, releases happen much sooner, once per year, and there is less in the release.

Since 2015, when ESX was released, there should be an ECMO script released each year. Now, the features released need to be supported. And most likely new releases are only supported by the latest browsers or updated engines. But the goal is to do a release each year. And that goal is controlled by the committee. So since I mentioned the committee, let's look at some of the concepts that apply to this evolution of ECMO script.

First off this committee that controls this evolution is called the technical committee 39 and it is the committee that controls the evolution ECMAScript base They make the decisions of what goes in to atmospheric. Now, the committee consists of representatives of different companies. And these are usually companies that have some sort of stake in JavaScript. And finally, consensus is required from the committee. So in order for something to move forward, there has to be consensus about that feature. Now, there currently is a process for releases that help accomplish the goal of smaller more frequent releases.

So I want to show you that process so you're familiar with it. I won't go into a lot of detail in it, but at least you'll understand how releases happen. With the ACMA script standard. So this consists of four stages and the first stage is zero. Now this is basically stage zero Basically just an idea for a feature and usually this comes from a member of the committee or it could be a non member who is registered as a contributor. Now, stage one is the formal proposal for the feature.

Now, this particular stage requires a champion for this feature for the proposal. Now that champion or co champion must be a member of the TC 39 committee. Now, stage two this is the first version of what will be in the specification. So this is the draft. Once a feature reaches this point, stage two, inclusion of the feature in the standard is likely. Now, this requires a formal description of the syntax and the semantics The new feature.

Now stage three is the candidate stage. The proposal is mostly finished at this point, and now needs feedback. And so basically in this stage it is being tested and receiving feedback. Then we move on to stage four, which is where the feature is finished and in this case, the proposal is ready to be included in the standard. And if a feature reaches stage four, and there's no guarantee that a feature starting at stage zero is going to make it all the way to stage four, that's the reason there are these five stages in this process. But if it does reach stage four, the proposal will be included in the ACMA script specification as soon as possible.

Now This does not mean that it's inclusion in the very next release is going to happen is probable, but it's not 100% sure, because it could take longer before it shows up in the specification. So those are the stages a feature must go through. This keeps features moving instead of lumping them all together in a single large release. When one is done, when one feature is done, ready, it goes into the next release, and there is a scheduled release each year. Now I've included a link in the description of this topic, to a great article where a lot of this information comes from and it even goes into more detail. So if you would like to read more about this, see that link.

Alright, let's move on to the next topic and look at the new features available with ACMA script 2016