| Re: How do we manage large code sets in PHP? [message #169663 is a reply to message #169661] |
Wed, 22 September 2010 03:44   |
Hamish Campbell
Messages: 15
Registered: September 2010
Karma:
|
Junior Member |
|
|
On Sep 22, 12:15 pm, Michael <MichaelDMcDonn...@yahoo.com> wrote:
> On Sep 21, 4:20 pm, The Natural Philosopher <t...@invalid.invalid>
>> PHP is BASIC, for web designers. The OSS answer to Visual Basic. It's a
>> great little tool: A professional large project programming language? No.
>
> Thanks for your response. But if that's the case, (can't be used for
> large programming projects), what do we use instead?
TNP's comments were misleading - the size of the codebase has nothing
to do with whether you would need a compiled option. SPL autoloading
<http://php.net/manual/en/function.spl-autoload.php> will let you load
class libraries dynamically as required. You start to use compiled PHP
modules because you need significant performance gains (e.g. very high
traffic websites) or you are doing something unusually computationally
expensive. Until that point, it is generally a huge time (=money)
saver to write interpreted (rather than compiled) code.
PHP is a perfectly good language for building websites of any size,
and the perception that it's somehow inferior to the task than "real"
programming languages is a throwback to simpler times. Of course, if
you'd like to write everything from scratch in C or C++, no one is
going to stop you, but you're in the wrong place to get help there.
* footnote: You might also be interested in HPHP - Facebook's Open
Source PHP compiler (see <http://github.com/facebook/hiphop-php>). It
allows you to continue writing PHP but compile it into a server
instance. It's a pain to set up but it actually works really well,
especially if you're deploying to multiple machines.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]