On Fri, Mar 11, 2011 at 11:39 PM, David Hutto <smokefl...@gmail.com> wrote:
> On Sat, Mar 12, 2011 at 2:34 AM, Tommy Pham <tommy...@gmail.com> wrote:
>> On Fri, Mar 11, 2011 at 11:26 PM, David Hutto <smokefl...@gmail.com> wrote:
>>> On Sat, Mar 12, 2011 at 2:22 AM, Tommy Pham <tommy...@gmail.com> wrote:
>>>> On Fri, Mar 11, 2011 at 10:34 PM, David Hutto <smokefl...@gmail.com> wrote:
>>>>> Although, right now, if I were going to be using all of those
>>>>> languages in unison(and I am), then I'd go with C, and spit them out
>>>>> to the browser for lower level control, as well as, to remain familiar
>>>>> with some of the main languages being used currently.
>>>> But then how portable is your app?
>>> I'd have to refer to your reply:
>>> "This would depend on the original application design & code."
>>> If the original app is meant for specific hardware, and a specific
>>> company, then portability is null point.
>> If that's the case why even bother with PHP?  Why not just do it in C
>> for pure speed?
> Speed wasn't the point- Multiple technology usage was the point. And
> if you're going to poise a browser for multiple intercepts(in terms of
> languages), then C *seems* to be the best was to move toward the
> displayment of it's descendants.
> If it's going to be a multi-language project, then it needs to be
> addressed with a multilanguage source to stem from, and C would seem
> like the optimum epicenter for propagation of this.
> I thought one of the major points of PHP is 'develop
>> anywhere and deploy anywhere'.

In the OP's case, where would C fit in when you have HTML, JS, and PHP
- PHP would produce the resultant text in addtion to JS & HTML.  What
would be the 'specific need' to do work in C where PHP, its many
extensions and library (PECL & PEAR), and lots of the other PHP code
based libraries/frameworks out there already to do the job?  The way I
look at it, if too many languages are involved then most likely the
application design is over complicated.

SQL = back end data storage
PHP = processing input/output, including back end data
HTML/XML = document layout for nice hierarchical format
JS/Flash = client side effects and processing to offload some server load

Each already designed and made to do the the specific function and are
nicely coupled together.  From the above, I've yet to see the need to
write C code for the PHP based application - with the exception of
threads, and let's not get into it again... lol.

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to