Why some programmers like to use a very old development environment

First of all, I am also a novice, just into the workplace for a year. So I feel puzzled.
I've been to two companies, almost the same,
MSSQL 2000,
MySQL 5.0
PHP 5.2
Jquery
TP 3.1,3.0

Personal opinion, software, development environment upgrade for a reason, generally better than the old version
A few days ago, one of our developing PHP projects was moved from win to CentOS,
Even asked me to install php5.2,mysql5.0.
As a person who likes new technology, I don't understand why.

This issue has been closed because of a discussion-based question of non-technical questions

Reply content:

First of all, I am also a novice, just into the workplace for a year. So I feel puzzled.
I've been to two companies, almost the same,
MSSQL 2000,
MySQL 5.0
PHP 5.2
Jquery
TP 3.1,3.0

Personal opinion, software, development environment upgrade for a reason, generally better than the old version
A few days ago, one of our developing PHP projects was moved from win to CentOS,
Even asked me to install php5.2,mysql5.0.
As a person who likes new technology, I don't understand why.

It means you really don't know the truth about stability over everything.

If you are developing a new project it is possible to use a new, production-ready product that is dependent on the production environment.

There may be many reasons, such as a destination environment, such as an existing code.
The new version is certainly better than the old version of the features, such as PHP5.4 after the json_encode of Chinese processing. But the environment can change, but the old code can't keep up.
If you do now most of the services of PHP update to 7.0, then http_raw_post_data probably can kill 90% of the application.
Now our unit has a product with php5.2 and TP 3.1. And there are some people are old school or do not think enterprising, I then changed http_raw_post_data to Php://input abortions before the quarrel with colleagues for a period of time, and now each time the JSON is urlencode back and forth will be three or four times, is also no solution.
Like the PHP environment is OK, if it is a different language environment, but also often appear the more updates, the more bad the bug, is also very embarrassing. So it is generally the pursuit of a most stable environment. So until now is still XP everywhere, win2003 blossom.

The first is stability second is afraid of code incompatible with the new version

https://www.zhihu.com/question/29763362

• Stability is more than everything, and this is already being said upstairs. The new technology has its advantages, but no one is willing to do the first person to eat crabs, leading to new technology information Small (relative), out of the question to find ready-made answers are difficult, all need to solve their own, and often the actual situation does not have so much time to solve.
  The boss does not bird your technology is not new, is not enough geek, business projects in the continued stability is the king.

• Compatibility issues, this problem is not limited to PHP problems, typically such as Python2 and Python3.

• If the new technology is really good, it will certainly replace the old technology, but first of all to wait for his community to mature, before the actual project to adopt.

If you like the new technology, like geek, then you can work in the spare part of your own, to contribute to this new technology community.

Everyone with the IDE, auxiliary plug-ins, aids may not be the same, this idea for different people's habits and usage! The latest tools and Ides may have powerful personalization features, but developers need time to learn, understand and adapt, especially on-line products, and the need to fully understand the new tools, which requires a great cost of investment.

With the question of the problem, the development environment version of the problem, if the product is a very old project, it may contain some old configuration and support, if you switch to a new environment, compatibility is the biggest problem! In order to ensure that the project adapts to the new development environment, there may be significant changes to the project, which is a disaster for online products ...

The software system and the development environment use the habit to stabilize after not to move, stable good!!!

1, the new version from release to stability takes time
2, even if the stable version, a certain period of time will continue to find new bugs
3, some of the new version is not compatible, will lead to great changes, heavy workload, but also prone to problems

Therefore, safety first, such as the new version of the mature slowly migration, not only the new version. As a personal casual play the new version of course, as a project can not play like this.

