When the “Python Vs PHP” war matters
February 21st, 2008
Yesterday I had a meeting with a customer about a new site I should develop for them. Since they’re a book publisher, they wanted an online book store. Apart from the technical details (the site isn’t as simple as you may believe, they need a lot of not-so-easy-to-do stuff), the most important point we focused on is the fact that they have an internal IT technician that handles all their computer needs. If you’re asking yourself why this matters, keep reading:
- me (to be precise, my company) stopped development of PHP sites about one year ago in favor of Python
- we release the web site’s code to them
- for this project, we haven’t been asked any kind of future support; this means that when the site is finished, we won’t touch the product anymore (unless they don’t pay us to do the modifies they need)
- but they don’t want to pay us to these modifies, because they have their internal IT technician
- their technician knows only PHP (and he never even known the Python’s existence until yesterday)