Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2007-03

CGI (with Free Pascal) vs PHP

19 messages · 9 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Graeme Geldenhuys

Hi,

If you where planning on writing a new online inventory system with a Firebird DB as backend. Yes that is what I'm about to do... What would be the best choice of language?

For one I don't know PHP, but was told it is really easy to learn. I know Object Pascal / Delphi very well.

What would be the advantages of one over the other. Currently when I write Free Pascal applications I use tiOPF (Object Persistent Framework) to handle all my object persistence. This also allows me to switch DB backends without any code changes. I guess using CGI with Free Pascal I can still take advantage of that.

So 1 point to CGI and 0 to PHP. :-)

Any more?

Graeme Geldenhuys There's no place like S34° 03.168' E018° 49.342'

Reply by email

Michael Van Canneyt
to Graeme Geldenhuys
Graeme Geldenhuys wrote 5 lines
Hi, If you where planning on writing a new online inventory system with a Firebird DB as backend. Yes that is what I'm about to do... What would be the best choice of language?

FPC ;-)

For one I don't know PHP, but was told it is really easy to learn. I know Object Pascal / Delphi very well.

PHP is easy to learn. But it's nothing like Object Pascal.

Show quoted text 5 lines
What would be the advantages of one over the other. Currently when I write Free Pascal applications I use tiOPF (Object Persistent Framework) to handle all my object persistence. This also allows me to switch DB backends without any code changes. I guess using CGI with Free Pascal I can still take advantage of that.

Yes.

So 1 point to CGI and 0 to PHP. :-) Any more?

Seems you already made your choice :-)

You can also create an apache module with FPC. I would recommend that;
It'll be a lot faster than CGI.

If you want to reuse your existing code, I'd opt for that approach.

Michael.

Reply by email

Graeme Geldenhuys
to Michael Van Canneyt
Michael Van Canneyt wrote
> Firebird DB as backend. Yes that is what I'm about to do... What > would be the best choice of language? FPC ;-)

Asking in this mailing list, I would have guessed that much. :-)

You can also create an apache module with FPC. I would recommend that; It'll be a lot faster than CGI. If you want to reuse your existing code, I'd opt for that approach.

Sorry if this sounds stupid, but what is the difference? Memory usage, threading, etc?
I've only ever setup websites with Apache and written basic CGI apps.

Is there a speed difference between CGI and PHP?
Memory usage?
Session information?

Graeme Geldenhuys There's no place like S34° 03.168' E018° 49.342'

Reply by email

Bisma Jayadi
to Graeme Geldenhuys: If you where planning on writing a new online inventory system with a Firebird DB as…
If you where planning on writing a new online inventory system with a Firebird DB as backend. Yes that is what I'm about to do... What would be the best choice of language?

Of course, Pascal! :)

For one I don't know PHP, but was told it is really easy to learn. I know Object Pascal / Delphi very well.

For pascal developers, PHP is a mess. We use it simply because everybody use it, for matter of community support.

Show quoted text 5 lines
What would be the advantages of one over the other. Currently when I write Free Pascal applications I use tiOPF (Object Persistent Framework) to handle all my object persistence. This also allows me to switch DB backends without any code changes. I guess using CGI with Free Pascal I can still take advantage of that.

There's a pascal based CGI framework used to be called PSP (Pascal Server Page) but the authors had change the name to PWU (Pascal Web Utility?). Before I know PWU is existed, I use PHP, but now, I choose PWU. If you prefer OOP approach, you can use O-PSP (object PSP) another branch of the (default) procedural PSP.

So 1 point to CGI and 0 to PHP. :-)

If building CGI with no framework, I prefer using PHP. But since I knew PWU, I switch to PWU. Slowly but sure, I'm converting my PHP apps to PWU. Using FPC and PWU, there's almost no boundaries to what you can do to a web based app. We can use almost any FPC's frameworks/components/libraries on our CGI app. If you want to dirt you hand a little more, it'd not too hard to convert your CGI app into an Apache module. :)

More about PSP/PWU, visit
http://z505.com/cgi-bin/qkcont/qkcont.cgi?p=Powerful%20Web%20Utilities

-Bee-

has Bee.ography at:
http://beeography.wordpress.com

Reply by email

Bisma Jayadi
to Graeme Geldenhuys: Asking in this mailing list, I would have guessed that much. :-) Sorry if this sounds…
Show quoted text 6 lines
Sorry if this sounds stupid, but what is the difference? Memory usage, threading, etc? I've only ever setup websites with Apache and written basic CGI apps. Is there a speed difference between CGI and PHP? Memory usage? Session information?

For informations, comparison, and benchmark, visit

http://www.wrensoft.com/zoom/benchmarks.html
http://www.psp.furtopia.org/doc/overview-1.5.0.html http://leonardorame.blogspot.com/2006_10_01_leonardorame_archive.html

-Bee-

has Bee.ography at:
http://beeography.wordpress.com

Reply by email

Florian Klaempfl
to Graeme Geldenhuys: If you where planning on writing a new online inventory system with a Firebird DB as…
Show quoted text 16 lines
Hi, If you where planning on writing a new online inventory system with a Firebird DB as backend. Yes that is what I'm about to do... What would be the best choice of language? For one I don't know PHP, but was told it is really easy to learn. I know Object Pascal / Delphi very well. What would be the advantages of one over the other. Currently when I write Free Pascal applications I use tiOPF (Object Persistent Framework) to handle all my object persistence. This also allows me to switch DB backends without any code changes. I guess using CGI with Free Pascal I can still take advantage of that. So 1 point to CGI and 0 to PHP. :-)

(Pascal) compiler based CGI is magnitudes faster than PHP, less resource consuming and much easier to maintain. The only advantage of PHP is that is easier to use for beginners and that's probably the only reason why PHP is so popular: you can hack quickly something together but maintainance, performance etc. are nightmares.

Reply by email

Chuck Burkins
to Florian Klaempfl
Florian Klaempfl wrote 6 lines
(Pascal) compiler based CGI is magnitudes faster than PHP, less resource consuming and much easier to maintain. The only advantage of PHP is that is easier to use for beginners and that's probably the only reason why PHP is so popular: you can hack quickly something together but maintainance, performance etc. are nightmares.

With all due respect (and that *is* a lot of respect), I disagree. I leave out the relative speed of PHP vs. compiled pascal, as I've never use Pascal in CGI. I have got over 100,000 lines of PHP code in service, so I think I can safely comment on that.

PHP does not in any way burden a modern web server, at least when used as an apache module. My test server at work has 128MB of RAM and only occasionally does it slow down noticably, typically when MySQL is working on a particularly ugly join. In my experience, the speed of well written PHP is indistinguishable from the speed of the same static HTML, as long as you leave out any database interaction (and Pascal of course would have database interaction as well).

PHP written by skilled programmers can be quite readable and maintainable. Certainly easier in my eyes that C and miles ahead of Perl. It is true that PHP is easy for beginners to pick up, but Pascal is actually easier for beginners in my opinion, after all it was used as a teaching language for years and you don't need to know HTML. I've always found the claim that languages are bad BECAUSE they are easier for beginners to learn to be condescending and elitist ( and I don't think that's what you are saying -- after all you develop in Pascal, a language that is often tarred with that same brush). It is true that languages that are easy to learn pick up a lot of beginners who never seem to progress beyond beginners, but I think the same thing happens with Pascal.

Now, you can certainly knock some programmers, and if you were to say you find PHP inelegant, I certainly agree with you. There are some pitfalls that you run into in PHP that you'd never hit in Pascal because one is loosely typed and the other strictly typed. On the other hand, the scoping rules in PHP, when used intelligently, work better than any other language I've programmed in, once you get used to them.

I think PHP is popular largely because the web is popular. PHP is quite good for programming web pages. It's easy to install, well supported, has a rational syntax, quite feature rich, generally readable, and very easy to change quickly. It's an agile language in the sense that you can prototype a solution, tweak, refine and come to a solution that makes the customer happy very easily.

Now on to the I were setting up an online
inventory system, I'd certainly do it in PHP. But then I know PHP. The original poster does not, and I'm not going to say that he should learn it to complete a project. It certainly is a problem domain where PHP shines, but the Graeme's time would probably better spent solving the problem in a language he's facile in than learning a new one, regardless of how trendy and popular it is.

With high regard,
Chuck Burkins

Reply by email

Michael Van Canneyt
to Chuck Burkins
Chuck Burkins wrote 21 lines
On 3/6/07, Florian Klaempfl wrote: > > (Pascal) compiler based CGI is magnitudes faster than PHP, less resource > consuming and much easier to maintain. The only advantage of PHP is that > is easier to use for beginners and that's probably the only reason why > PHP is so popular: you can hack quickly something together but > maintainance, performance etc. are nightmares. With all due respect (and that *is* a lot of respect), I disagree. I leave out the relative speed of PHP vs. compiled pascal, as I've never use Pascal in CGI. I have got over 100,000 lines of PHP code in service, so I think I can safely comment on that. PHP does not in any way burden a modern web server, at least when used as an apache module. My test server at work has 128MB of RAM and only occasionally does it slow down noticably, typically when MySQL is working on a particularly ugly join. In my experience, the speed of well written PHP is indistinguishable from the speed of the same static HTML, as long as you leave out any database interaction (and Pascal of course would have database interaction as well).

Well. Since we switched to Mantis (PHP based, Apache module) for the bug-tracker, we have nothing but problems with the webserver.

So obviously, your mileage may vary.

Michael.

Reply by email

Florian Klaempfl
to Chuck Burkins: With all due respect (and that *is* a lot of respect), I disagree. I leave out the…
Show quoted text 13 lines
On 3/6/07, Florian Klaempfl wrote: > > (Pascal) compiler based CGI is magnitudes faster than PHP, less resource > consuming and much easier to maintain. The only advantage of PHP is that > is easier to use for beginners and that's probably the only reason why > PHP is so popular: you can hack quickly something together but > maintainance, performance etc. are nightmares. With all due respect (and that *is* a lot of respect), I disagree. I leave out the relative speed of PHP vs. compiled pascal, as I've never use Pascal in CGI. I have got over 100,000 lines of PHP code in service, so I think I can safely comment on that.

I agree that you can write good code in PHP as well as one can in Perl but it requires a lot discipline and most people don't do so in PHP and Perl while pascal forces them to do so. Probably one of the reasons why Pascal and Ada aren't that popular.

PHP does not in any way burden a modern web server, at least when used as an apache module.

Well, feel free to solve our problems with mantis ;) I know a lot of other people permanently fighting with the load of their servers and I'am rather sure the only reason is the resource wasting of PHP.

Show quoted text 5 lines
PHP written by skilled programmers can be quite readable and maintainable. Certainly easier in my eyes that C and miles ahead of Perl. It is true that PHP is easy for beginners to pick up, but Pascal is actually easier for beginners in my opinion,

Pascal doesn't allow you hack together something like PHP allows. A pascal based web application is harder to write than a PHP one. See above.

Reply by email

Daniël Mantione
to Chuck Burkins: With all due respect (and that *is* a lot of respect), I disagree. I leave out the…

Op Tue, 6 Mar 2007, schreef Chuck Burkins:

Show quoted text 21 lines
On 3/6/07, Florian Klaempfl wrote: > > (Pascal) compiler based CGI is magnitudes faster than PHP, less resource > consuming and much easier to maintain. The only advantage of PHP is that > is easier to use for beginners and that's probably the only reason why > PHP is so popular: you can hack quickly something together but > maintainance, performance etc. are nightmares. With all due respect (and that *is* a lot of respect), I disagree. I leave out the relative speed of PHP vs. compiled pascal, as I've never use Pascal in CGI. I have got over 100,000 lines of PHP code in service, so I think I can safely comment on that. PHP does not in any way burden a modern web server, at least when used as an apache module. My test server at work has 128MB of RAM and only occasionally does it slow down noticably, typically when MySQL is working on a particularly ugly join. In my experience, the speed of well written PHP is indistinguishable from the speed of the same static HTML, as long as you leave out any database interaction (and Pascal of course would have database interaction as well).

PHP has serious defficiencies, one is raw performance, another is the way it deals with libraries, which is just like a C compiler, include all files you need. This means once you get a large PHP library, it starts to suck, even though you only use one procedure in your library.

Another issue is the dealing with databases. The php way is to do text substition, which is a serious risk of SQL injection vulnerabilities. More often than not, PHP does not do database connection pooling, and this because everyone is writing his own database abstraction layers, there exists no good database API in PHP.

Now Pascal has its defficiencies in web programming too. CGI programming tends not to be very scalable, allthough it compensates by raw performance. The trouble is when databases come in, connection pooling is almost impossible to achieve with CGI.

PHP written by skilled programmers can be quite readable and maintainable. Certainly easier in my eyes that C and miles ahead of Perl.

Yes, but you know what we mean. In syntax PHP cannot match Pascal. This does not mean Pascal should be used just for its syntax, but its properties of writing readable and self-documenting code have not been matched by much languages. I like to code web pages in TCL. Comparing TCL and PHP, TCL beats it, both in power and readability. Even TCL does not have the same syntax properties as Pascal.

Show quoted text 25 lines
It is true that PHP is easy for beginners to pick up, but Pascal is actually easier for beginners in my opinion, after all it was used as a teaching language for years and you don't need to know HTML. I've always found the claim that languages are bad BECAUSE they are easier for beginners to learn to be condescending and elitist ( and I don't think that's what you are saying -- after all you develop in Pascal, a language that is often tarred with that same brush). It is true that languages that are easy to learn pick up a lot of beginners who never seem to progress beyond beginners, but I think the same thing happens with Pascal. Now, you can certainly knock some programmers, and if you were to say you find PHP inelegant, I certainly agree with you. There are some pitfalls that you run into in PHP that you'd never hit in Pascal because one is loosely typed and the other strictly typed. On the other hand, the scoping rules in PHP, when used intelligently, work better than any other language I've programmed in, once you get used to them. I think PHP is popular largely because the web is popular. PHP is quite good for programming web pages. It's easy to install, well supported, has a rational syntax, quite feature rich, generally readable, and very easy to change quickly. It's an agile language in the sense that you can prototype a solution, tweak, refine and come to a solution that makes the customer happy very easily.

PHP got its social contacts right, causing many people to evangelise it. Further, besdides that it was easy to learn, had good documentation, and due to the work of Linux distributions, easy to set up and get running.

Now on to the I were setting up an online inventory system, I'd certainly do it in PHP. But then I know PHP.

I won't, PHP is not professionals. If things get big, either in code or in performance, PHP becoems a serious handicap.

Show quoted text 5 lines
The original poster does not, and I'm not going to say that he should learn it to complete a project. It certainly is a problem domain where PHP shines, but the Graeme's time would probably better spent solving the problem in a language he's facile in than learning a new one, regardless of how trendy and popular it is.

... and if you learn a language, you'd better learn a good one :)

Daniël Mantione

Reply by email

Jonas Maebe
to Michael Van Canneyt: Well. Since we switched to Mantis (PHP based, Apache module) for the bug-tracker, we have…
Michael Van Canneyt wrote 11 lines
> PHP does not in any way burden a modern web server, at least when > used > as an apache module. My test server at work has 128MB of RAM and only > occasionally does it slow down noticably, typically when MySQL is > working on a particularly ugly join. In my experience, the speed of > well written PHP is indistinguishable from the speed of the same > static HTML, as long as you leave out any database interaction (and > Pascal of course would have database interaction as well). Well. Since we switched to Mantis (PHP based, Apache module) for the bug-tracker, we have nothing but problems with the webserver.

Well, he explicitly mentioned the problem that Mantis has: we use it in combination with MySQL (I don't even know if it supports another database), and Mantis does a lot of joins (don't know if they are ugly though).

Jonas

Reply by email

Daniël Mantione
to Jonas Maebe

Op Tue, 6 Mar 2007, schreef Jonas Maebe:

Show quoted text 18 lines
On 6 mrt 2007, at 13:16, Michael Van Canneyt wrote: > > PHP does not in any way burden a modern web server, at least when > > used > > as an apache module. My test server at work has 128MB of RAM and only > > occasionally does it slow down noticably, typically when MySQL is > > working on a particularly ugly join. In my experience, the speed of > > well written PHP is indistinguishable from the speed of the same > > static HTML, as long as you leave out any database interaction (and > > Pascal of course would have database interaction as well). > > Well. Since we switched to Mantis (PHP based, Apache module) for the > bug-tracker, we have nothing but problems with the webserver. Well, he explicitly mentioned the problem that Mantis has: we use it in combination with MySQL (I don't even know if it supports another database), and Mantis does a lot of joins (don't know if they are ugly though).

That is not the real problem with Mantis. Mantis views a database record as an object with methods and fields. If you modify a field the record is retrieved from the database and stored again.

So, during a page request hundreds of queries can get executed, instead of requesting all data for the page at once, Mantis uses one query per record.

Daniël

Reply by email

Michael Van Canneyt
to Daniël Mantione
Daniël Mantione wrote 30 lines
Op Tue, 6 Mar 2007, schreef Jonas Maebe: > > On 6 mrt 2007, at 13:16, Michael Van Canneyt wrote: > > > > PHP does not in any way burden a modern web server, at least when > > > used > > > as an apache module. My test server at work has 128MB of RAM and only > > > occasionally does it slow down noticably, typically when MySQL is > > > working on a particularly ugly join. In my experience, the speed of > > > well written PHP is indistinguishable from the speed of the same > > > static HTML, as long as you leave out any database interaction (and > > > Pascal of course would have database interaction as well). > > > > Well. Since we switched to Mantis (PHP based, Apache module) for the > > bug-tracker, we have nothing but problems with the webserver. > > Well, he explicitly mentioned the problem that Mantis has: we use it in > combination with MySQL (I don't even know if it supports another database), > and Mantis does a lot of joins (don't know if they are ugly though). That is not the real problem with Mantis. Mantis views a database record as an object with methods and fields. If you modify a field the record is retrieved from the database and stored again. So, during a page request hundreds of queries can get executed, instead of requesting all data for the page at once, Mantis uses one query per record.

This is not the only problem. To be able to do multiple MySQL queries at once (the MySQL C client does not allow this), PHP must retrieve the whole record set at once, and keep it in memory, thus wasting a lot of memory.

That has nothing to do with Mantis, but is a design problem of MySQL - and thus PHP. But unfortunately, MySQL is used most for PHP web apps, it gets shipped as the default.

Michael.

Reply by email

Jason P Sage

I would like to put my two sense in because I have been doing extensive FreePascal Web programming, and I have to agree that FreePascal has a nice structure and PHP often can get quite ugly.

For many applications PHP is just fine.

The points you guys are bringing up are good ones - like security with "text injections" possibly begin exploited with PHP and for rather large complex applications - things can get dicey in PHP - as far as hard to maintain and performance becoming an issue. But in all fairness - well written PHP can do many great things.

PHP has many "features" that FreePascal doesn't, and FreePascal has many features that PHP doesn't. What is available for each will likely change over time.

Personally, I'd rather have my FreePascal Syntax, smartLinking, Socket library, multi-threading library, ability to call dlls, inline functions, true object oriented binaries versus emulated OO script (Which is likely OOP underneath but it still parsed).

I can write a desktop application, a web application, an embedded application, a database application, a daemon - all with one language.

PHP was never designed to be quite this flexible. My point is, like Daniel said "Better learn a good language"; I'd rather learn a language I can use for anything - than another vogue special interest language only because you be a master in a couple things - but not in everything. FreePascal has all the power required to create any kind of application
- therefore - I can ultimately do much more with it.

I've written a CGI application in FreePascal that gets some performance gain over typical CGI from a file based IPC. The CGI app just passes environment and request info to the main multi-threaded database application, and then sends the output back to the client when the big application finishes its thread. The idea being a small CGI program that doesn't grow as the application grows - is better than the typical CGI app that gets bigger and bigger as it evolves getting slower all the time. CGI is very portable. Performance is decent for a CGI application. FastCGI and a stand alone server are the next additions to this model for performance reasons.

PHP versus FreePascal: It's like an internal combustion airplane versus a Jet Airplane to me. You Might get the internal combustion airplane off the ground faster (PHP) but a Jet airplane will go farther and faster every time.(FreePascal of course).

Seriously - with FreePascal I can write FastCGI that does what I want versus what is available for PHP, I can write to any protocol I want, and it simply has all the power I'll ever need - for any application.

PHP is great also. I'll put my mmoney on FreePascal because it goes farther, faster, and can handle the long haul.

Jason P Sage

Reply by email

Chuck Burkins
to Daniël Mantione: Op Tue, 6 Mar 2007, schreef Chuck Burkins: PHP has serious defficiencies, one is raw…

This is an interesting discussion, guys. I really believe that there is no one perfect language and some languages are better at some problems than other. I should also know better than to argue with people who clearly know more than I do about *writing* a language, since I know nothing about it, and some (all?) of you are on the FPC development team.

Show quoted text 5 lines
PHP has serious defficiencies, one is raw performance, another is the way it deals with libraries, which is just like a C compiler, include all files you need. This means once you get a large PHP library, it starts to suck, even though you only use one procedure in your library.

Yes, this is a problem. In my experience, not a large one. Most languages have problems you have to work around, this is one of PHP's. For instance, I've had to work around the lack of hashes in Pascal (by including some kind soul's module).

Show quoted text 6 lines
Another issue is the dealing with databases. The php way is to do text substition, which is a serious risk of SQL injection vulnerabilities. More often than not, PHP does not do database connection pooling, and this because everyone is writing his own database abstraction layers, there exists no good database API in PHP.

The fact that there is no single database API (well, there is one in PEAR) is oft regretted. It is indeed a deficiency. I think you'd have to be careful about sql injection in ALL programs that take user input and use it in database queries, regardless of the language.

Yes, but you know what we mean. In syntax PHP cannot match Pascal.

I agree. But that is something of a matter of taste.

PHP is not professionals. If things get big, either in code or in performance, PHP becoems a serious handicap.

I don't agree. PHP is used by corporations all over the place now. I've been making a living at it since 2000. Search dice.com for 'PHP' and you get over 1500 hits. Search for pascal and delphi, and you get under 300. So if being a professional language means you can make a living at it, PHP qualifies. Of couse Visual Basic qualifies too, so I'm not sure that means anything ;)

As to scaling, that problem seems to be solvable. There have been some very large websites using php for a while. (digg.com and yahoo.com come to mind)

I'm don't want to evangelize PHP on a Pascal list, so I'll stop. PHP has problems. So does Pascal. I happen to like (and work in) both. The original poster wondered about PHP suitability to the task at hand. IMO, it's suitable.

And by the way, FPC rocks. Really.

-Chuck

Reply by email

Marco van de Voort
to Chuck Burkins
Show quoted text 6 lines
I agree. But that is something of a matter of taste. > PHP is not professionals. If things get big, either in code or in > performance, PHP becoems a serious handicap. I don't agree. PHP is used by corporations all over the place now.

Sure, but as vehicle for forums, content system etc. At least for me it is very hard to separate the package reuse part of the PHP buzz from the programmer use. (and with that I mean making webapps, not minimal package customization)

Reply by email

Bisma Jayadi
to Daniël Mantione: Op Tue, 6 Mar 2007, schreef Chuck Burkins: PHP has serious defficiencies, one is raw…
Now Pascal has its defficiencies in web programming too. CGI programming tends not to be very scalable, allthough it compensates by raw performance. The trouble is when databases come in, connection pooling is almost impossible to achieve with CGI.

I'm not quite agree with this. CGI programming without a solid framework indeed is not very scalable. But that's not the case if you have a good designed CGI framework. Even database connection pooling is not that hard to do when you have a good CGI framework. Maybe it sounds rather complex and complicated when we're talking about "framework", but as it exists, CGI programming would be as scalable as VCL/LCL based desktop applications.

PHP got its social contacts right, causing many people to evangelise it. Further, besdides that it was easy to learn, had good documentation, and due to the work of Linux distributions, easy to set up and get running.

Agree. This is pretty similar to why C is more popular then pascal. It's simply historical reason, C is born and used before pascal is good enough to compete with C. And the more popular a thing (especially software) the more difficult to be replaced even with something better.

... and if you learn a language, you'd better learn a good one :)

Totally agree. If I can do almost anything using Pascal, why should I learn another language? ;)

-Bee-

has Bee.ography at:
http://beeography.wordpress.com

Reply by email

Graeme Geldenhuys
to Michael Van Canneyt: This is not the only problem. To be able to do multiple MySQL queries at once (the MySQL…
Michael Van Canneyt wrote 7 lines
This is not the only problem. To be able to do multiple MySQL queries at once (the MySQL C client does not allow this), PHP must retrieve the whole record set at once, and keep it in memory, thus wasting a lot of memory. That has nothing to do with Mantis, but is a design problem of MySQL - and thus PHP. But unfortunately, MySQL is used most for PHP web apps, it gets shipped as the default.

I can't understand this either. I personally think Firebird is a much better RDMS and has a lot more features than MySQL, yet MySQL is a lot more known than Firebird. A real pitty, but that still doesn't stop me from using Firebird.

Graeme Geldenhuys There's no place like S34° 03.168' E018° 49.342'

Reply by email

Graeme Geldenhuys
to Jason P Sage: I would like to put my two sense in because I have been doing extensive FreePascal Web…
Jason P Sage wrote 7 lines
Personally, I'd rather have my FreePascal Syntax, smartLinking, Socket library, multi-threading library, ability to call dlls, inline functions, true object oriented binaries versus emulated OO script (Which is likely OOP underneath but it still parsed). I can write a desktop application, a web application, an embedded application, a database application, a daemon - all with one language.

That's guys for all you comments. I think this sums it up nicely. For me, Free Pascal now seems like the best choice for the job.

My main concern was that PHP does something radical that CGI (no matter the language) couldn't, or that PHP is a lot faster than CGI. With all the posts, I guess now there is no reason for concern.

Graeme Geldenhuys There's no place like S34° 03.168' E018° 49.342'

Reply by email