00:01
Their proper restriction for changes in programming language can depend on the goals and context of the language evaluation.
00:13
So here are some considerations as the first is the backward compatibility.
00:21
It's backward compatibility.
00:25
So it is an essential to maintain the backward compatibility as much as possible to ensure that the existing code basis continues to work correctly with a newer language version.
00:38
Averse and breaking the changes can cause the significant disruptions for the developers and the organization.
00:45
The second is of its deprections and the transaction and the transitions period and with the transitions of the periods.
00:59
So when they introduce in the new feature or the disruptions old ones the programming language can change accordingly.
01:08
So as the disruption will cause the changes with it.
01:12
The next comes with the community feedback with the community feedbacks as the programming language design should actively seek the feedback from the developers community to understanding the needs pain points and the preferences community as the decision can leads to the more balanced language.
01:38
The fourth step we take as a standardization standardization.
01:44
So with respect to the establishing standard for the programming language can help to ensure the consistency across the different across its different implementation as well as to reduce its fragmentation.
01:59
As the next is the clear documentation clear documentation...