<story><title>Why CCP is still using Python 2</title><url>http://www.robg3d.com/?p=1175</url></story><parent_chain></parent_chain><comment><author>ChuckMcM</author><text>It was an interesting read, I&amp;#x27;m not sure if they are like the shark, already dead but the message hasn&amp;#x27;t gotten to the swimming part yet, or like a harbinger of the future.&lt;p&gt;One of the things engineers are going to have to come to grips with is that you can actually be &amp;quot;done&amp;quot; doing new design. It&amp;#x27;s really really hard in FOSS stuff because bug fixing is so much less rewarding than new feature development. But programming languages are tools, and if you&amp;#x27;re familiar with tools in the physical world you realize that once you get to a certain optimum, there isn&amp;#x27;t a lot of &amp;#x27;new feature&amp;#x27; to add.&lt;p&gt;The nature of tools is why a good oscilloscope or bandsaw is still a good oscilloscope or bandsaw 25 years later. It does what it needs as well now as it did when it was new. If there is some new &amp;#x27;space&amp;#x27; to work in, you might need a variation of the tool, but the basic tool is fine.&lt;p&gt;Computers, and computer tools, are maturing. We&amp;#x27;ve seen this in the slowing of the upgrade cycle, the resistance to change that the OP writes about, people are ok with their tools. That will be a different world of computers than we are used to I suspect.</text></comment>
<story><title>Why CCP is still using Python 2</title><url>http://www.robg3d.com/?p=1175</url></story><parent_chain></parent_chain><comment><author>jaimebuelta</author><text>Let&amp;#x27;s face, there&amp;#x27;s going to be projects that will NEVER be ported to Python3. Not a couple, a lot. Why should they? If they are using software for making money, it works and porting it to Python3 maybe is just too expensive and too risky.&lt;p&gt;The point is that, as time past, hopefully more new projects will be created in Python3, and they can drive the development of more and more modules and tools, and, eventually, all new projects are in Python3 and Python2 is just legacy.&lt;p&gt;Legacy code happens. And for good reasons. And there are lots of people working on them and earning money. Software is a means to an end. I love to use new technology and using old tech drives me crazy, but from the point of view of business, it&amp;#x27;s a decision that makes sense. There are still COBOL systems that behave perfectly.&lt;p&gt;EVE is a game. It currently works. Its players don&amp;#x27;t care if it&amp;#x27;s done in Lisp, x86 assembly or Haskell. The people working with the code care, but to migrate it to Python3 is simply to costly and risky to do. And will probably always be.
If they start a new project, they may be starting it on Python3. And that&amp;#x27;s fine. That&amp;#x27;s the way it should.</text></comment>