There will be greater resistance to the promotion, and the effect is not good. Because of the version number, people will have different concerns about it. They’ll say, ok, I get it, I’ll check it out when it releases the stable version. What he really meant was, “I won’t bother with it until the inventor of the language gives me a stable version. Because I’m not sure the author is serious or capable of getting it done before releasing the stable edition.”
There is no such thing as perfect. By comparing with different things, we can always find the flaw in something. In the case of programming languages, even if it gets to 5. X, 6. X, or 7. X, it won’t be perfect.
Why release a stable version number? It’s a way of telling the user, "you can do something with it, and it won’t go wrong as far as the language promises. ". If you have to release a 1.0 version that you think is perfect, I don’t think that day will ever come. Because in the long course of development, the cognition of language developers will change, and a lot of things around them will affect them. They may change their original intention and gradually get lost.
As for version compatibility, let me also answer that question. If it’s backwards compatible that would be great, users would love it. If compatibility is not possible, the risk needs to be taken seriously from the user’s perspective, since the value of the language lies with its users rather than its inventors or development teams (for example, upgrading from php4 to php5 results in little modification of the user’s project code. The upgrade from php5 to php7 is still the same, and users feel great. In the words of the PHP product team, it was “user friendly and extremely harsh on compilers” -because it was so focused that the advent of ROR and Django in the early days still didn’t bother PHP. Because of some historical reasons there are still some PHP users complain, it is to make some changes, but by every upgrade to make changes to the user by availability of impact of the project, rather than violence. - this could be a one of the reasons why it continues to popular. As for Py3k, from the strategy of the market I think is a risky operation, many old customers don’t want to turn to py3. If it weren’t for the current ai wave, py’s fate would most likely be similar to ruby’s).
I think this topic can continue, please let me hear more creative ideas.
My background:
At present, I seldom do development work by myself. There are nearly 80,000 employees in my company, and I am in charge of the product development work of three teams. I’m looking at it more from a product perspective than a technology perspective.
Here are the techniques I’ve used
Java, 14 years
C + +, 3 years
PHP, 10 years
Python, 8 years