Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #80570 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2014-11-12 08:56 +1100 |
| Last post | 2014-11-12 08:56 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Communicating with a PHP script (and pretending I'm a browser) Chris Angelico <rosuav@gmail.com> - 2014-11-12 08:56 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-11-12 08:56 +1100 |
| Subject | Re: Communicating with a PHP script (and pretending I'm a browser) |
| Message-ID | <mailman.15695.1415743024.18130.python-list@python.org> |
On Wed, Nov 12, 2014 at 4:55 AM, Ethan Furman <ethan@stoneleaf.us> wrote: > On 11/11/2014 09:30 AM, Larry Martell wrote: >> >> >> They are technically savvy. They are a 100% PHP shop. They have a big, >> complicated app that they've been working on for 10 years. No one >> there knows python or django. They want to put some new frontends on >> their app. I was bought in for another project (involving Google Tag >> Manager and Google Analytics), which I completed. Then they asked me >> about this project. I told them they should redo their app in Flask or >> Django. It took some cajoling, but they eventually said OK. But then a >> few days later they said before I went off and reimplemented >> everything in python, could I just build the new frontend and call the >> existing PHP code. This would enable them to get the new frontends out >> to their clients sooner, and then I could go back and port the PHP to >> python. I don't see what is so wrong with that. > > > Sounds like an excellent game plan to me. :) I wouldn't go so far as "excellent", but certainly it's not nonsensical. It's just a question of balancing the cost of the hybridization (development effort that, once the Python rewrite is complete, will be discarded) against the time gain of getting *something* sooner. Also, this will probably have a significant impact on performance/throughput, so everyone needs to be aware that benchmarking Python by looking at the new app's performance would be horribly unfair. But this is a viable proposal. ChrisA
Back to top | Article view | comp.lang.python
csiph-web