Re: Re: Delaying $(document).ready() in jQuery until php script finish

On Sat, Mar 12, 2011 at 2:34 AM, Tommy Pham <tommyhp2@gmail.com> wrote: > On Fri, Mar 11, 2011 at 11:26 PM, David Hutto <smokefloat@gmail.com> wrote: >> On Sat, Mar 12, 2011 at 2:22 AM, Tommy Pham <tommyhp2@gmail.com> wrote: >>> On Fri, Mar 11, 2011 at 10:34 PM, David Hutto <smokefloat@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'. >