Labs/Weave/PythonMigration: Difference between revisions

# The trend in operational support towards Python installations, provides us with better infrastructure knowledge, problem response, and shareable tools.

# We now have much greater in-house Python expertise than PHP. Many of our recent hires have been high-profile figures in the Python community. This will lead to higher quality of code, but also higher quality of reviews.

# The current PHP codebase was originally written to support a model that has been refined extensively since it was first written. We can leverage this knowledge to write a cleaner server that will be easier to mdoify going forward.

# It seems that the transition is inevitable at some point, and this transition will be more painful the longer we wait.

# The current code is tested and functional. We can mitigate this with an extensive testing suite (which already exists) as well as the more extensive use of unit testing that Python supports.

# External users with current installations will suffer some migration pain. Much of it we can mitigate, and the underlying storage isn't changing, but some systems may not offer Python as an option.