PHP и другие языки
PHP самый лучший язык для web программирования, а как насчет других языков?
- PHP против ASP?
-
На самом деле, ASP сам по себе языком не является, это акроним для Active Server Pages, в действительности для программирования с ASP используется Visual Basic Script, JScript и C#, среди прочих. Наибольшим недостатком ASP является то, что это частная система и по родному используется только на Microsoft Internet Information Server (IIS). Это ограничивает его доступность только для Win32 серверов. Существует пара проектов в работе, которые позволяют ASP выполняться в других окружениях и на других web серверах: » InstantASP от » Halcyon (коммерческий), Chili!Soft ASP от » Chili!Soft (коммерческий) и » Mono (опенсорс). Считается, что ASP медленнее и более громоздкий чем PHP, а также менее стабильный. Некоторыми плюсами ASP является то, что так как в нем в основном используется VBScript, то подхватить язык относительно легко, если вы уже знаете как программировать в Visual Basic. Поддержка ASP по умолчанию включена в IIS, что упрощает его установку и запуск. Однако, встроенные в ASP компоненты очень ограничены, поэтому если вам требуются "продвинутые" возможности, такие как взаимодействие с FTP серверами, вам придется покупать дополнительные компоненты.
- PHP против Cold Fusion?
-
В общем считается, что PHP быстрее и более эффективен для сложных программных задач и для пробования новых идей. Также на PHP обычно ссылаются как на более стабильный и менее требовательный к ресурсам. Cold Fusion имеет лучшую обработку ошибок, абстракцию баз данных и разбор дат, хотя в PHP 4 тоже уделено внимание абстракции баз данных. Отличительной сильной стороной Cold Fusion является его превосходная поисковая система, но многие резонно аргументируют, что поисковая система это не то, что должно быть включено в скриптовый язык для веб. PHP работает почти на каждой существующей платформе, Cold Fusion доступен только для Windows, Solaris, Linux, MacOS и AIX. Cold Fusion имеет хорошую IDE и в общем в нем легче начинать, тогда как PHP вначале требует больше знаний по программированию. Cold Fusion был спроектирован в расчете на не программистов, когда PHP сосредотачивается на программистах.
- PHP против Perl?
-
Наибольшее преимущество PHP перед Perl это то, что PHP был спроектирован для написания скриптов для веб, в то время, как Perl был создан для более широкого круга задач и поэтому может быть очень сложным. Гибкость/сложность Perl усложняет совместную работу разработчиков с разным уровнем квалификации. PHP имеет менее запутанный и более строгий формат без ущерба для гибкости. PHP проще интегрировать в существующий HTML, чем Perl. По большому счету, PHP имеет почти что все 'хорошие' функциональные возможности Perl: конструкции, синтаксис и так далее, не становясь таким же сложным, каким может быть Perl. Даже командная строка PHP (CLI) достаточно мощна для выполнения сложных задач, таких, для которых традиционно использовался Perl. Perl довольно испытанный и точный язык, он существует с конца восьмидесятых, но PHP довольно быстро созрел, и продолжает делать фантастические успехи.
Коментарии
If you ever tried to configure a web server for WAP, serving WML content you know it's not an easy job. You can easily make dynamic WML pages for mobile phone users with PHP. All the options and extras from DB+PHP oriented web-site can easily be transfomed into a WAP version of your site. With a single line - Header("Content-type: text/vnd.wap.wml"); you can be in another "mobile" dimension :). Take all you need ... and even more.To ahabra,
Very interesting page. I would ask the following, however as you investigate this topic further... you'll soon become the PHP vs. Java guru.
Your comparisons are interesting and well thought out. I would also add some higher-level (less computer-science oriented, simply because the task at hand is generating web pages 'on the fly'). As a pure CS language, there is no doubt that Java is superior. But as a web page generator, I have moved from a Java-centric approach to a PHP approach, leveraging servlets or beans as needed "under the covers".
Therefore, some higher-level things to consider:
1) Compare the complexity of real-world production applications (postnuke.com vs ? in content management, phpbb.com vs. ? in discussion boards, jpgraph vs. ? in graphing). In my mind, the proof is in the pudding - which technology results in the better, more production-ready applications? They may be out there for Java - I would just like to know where they are and who is using them.
2) Compare slinging (generation) of markup which is where PHP excels (as it was designed to sling markup - this includes features such as character transformations, variable accessibility, web page captures (see the fopen call which captures a web page in a single function call). Your point about a string being encapsulated in a string class is somewhat irrelevant if you are a programmer cranking markup. Embedding object-oriented code into a page can be much more painful (and slower to execute) than leveraging traditional coding techniques.
3) Compare native database and directory support. Java would have the advantage in generic database access (JDBC) but PHP has the advantage in LDAP support (JNDI has several bugs which we have run into - quite painful) and native database access (e.g., Oracle or MySQL integration).
Overall, well done - and a very popular topic! It's worth building it out further.
I've been working with PHP, JSP, Java and CFM for 2 years now.I can tell that for web development only, php is not nearly as good as cfm on speed, on ease to use and on interaction.
On the other hand you just can't do anything very special with CF like opening a socket with the ease of php.
I would say : use what you need for your application, cfm is truly the fastest, as it has a daemon running instead of a per request, plus the ability to cache queries that is awesome.
php is fast but is a pain on some aspects and has loads of bugs.
JSP have almost no bug at all, or at least i did not find any, but it is hard to debug.
Good thing on JSP is that you can write real applications and have perfect interaction by using classes, plus it is much more of a serious language.The only problem is that you take at least twice times to make same program on JSP and it is not even close as well documented and easy to use as php.
My experience with ASP and PHP is about equal, I think they both serve equally as good of a purpose depending on what the programmer is trying to do. I do like the syntax of PHP a lot and the speed of it is great, although the client/server interactivity of ASP with Windows and MAC clients is what I'm excited to see grow with future versions of PHP.I have to note that a very big advantage of PHP over ASP is that PHP has much easier commands...
Take openening of a file in ASP...
First create a file object... I put this into a function because the line is simpy to long and I called it "Init fileobject"
<%
Initfileobject 'The Sub I created in order not to type that idot line all the time
Set Fil = FileObject.OpenTextFile(Server.MapPath("data")&"\datafile")
datavar = Fil.ReadLine
CloseFile Fil
Set Fil = Nothing
Set FileObject = Nothing
%>
Why always those objects...
The same thing in PHP
<?php
$fil = fopen("data/datafile","r");
$datavar = fgets($fil);
fclose($fil);
?>
That's all...
And that while VBScript is based on BASIC (BEGINNERS Allpurpose Symbolic Instruction Code)...
I code too shortly in PHP to make a full analysis yet, but the complex object structues of VBScript is something I really put in question, PHP has a much easier syntax when it comes to that...
One of the first things I saw was that PHP is based on C, which is one of the hardest programming languages in the world. That makes the syntax of for example the "for" statement less to my desire, which I like better in VBScript (ASP)... If you are an experienced C or C++ programmer, I think PHP makes automaticly the best choice out of PHP vs ASP.
But I did find out in only 1 hour that the syntax of PHP gives you much less typing than ASP, that is a fact. I think that for the rest the pick of language is pretty personal.
When it comes to stability. ASP servers crash very much. I don't think ASP itself is the evil one in this. ASP only runs on Windows servers, and we all know how much Windows crashes. I truely believe that also picks a part of the puzzle...
...Well, all I can say about ASP.NET and the .Net frameworks is that rather than adopt them we decided to switch all of our development to PHP and other open-source tools. We simply got tired of all the churing of the development platform from $soft: things like changing API's during final betas, undocumented api's etc.
Ive programmed in C, C++, VB, ASP (since the original beta in 1995) and ASP.Net, Com, Com+, .Net Frameworks and in C("sharp"). The fact of the matter is that most of these new and "improved" development tools dont save much, if any money, and are mostly, unnecessary. We have found PHP to be an excellent replacement for similar $soft tools and technologies for web development.
Its true that there is a bit more code required to supplement things that $soft and others give you for a price, but the bottom line is that most of these things are not very difficult to do properly. In our business there is a huge risk from not having access to source code and we simply cant be held hostage by a third party company: when you add up the dollar value of this risk for our business it far exceeds the few dollars we need to spend in extra supplemental coding - which is done once so its a one-time cost.
I really must take issue with (Cash at nospam dot thesilverside dot com)'s comments regarding enterprise applications and PHP.
Yes, PHP is an interpreted language (but...PHP Accelerator? also you can write caching *with* PHP, also checkout http://shootout.alioth.debian.org/, and have you seen the benchmarks for Pharrot?). Adding more tiers into your application is a recipe for disaster since it reduces scalability by creating bottlenecks/crossovers and has a big impact on transparency. I'll admit that for a very few applications, then server hardware is more expensive than developer time - like if you're turning around more than 500000 hits/hour, then it may work out cheaper to develop in 'C' with half the servers than PHP, but this is far from the sort of volume I've seen on an enterprise application. There's a lot been written elsewhere on PHP and scalability which I won't repeat here.
There are issues with using PHP for this kind of application. Firstly managment of privilege - but that applies (AFAIK) to any web-based system. There's also the problem of namespace collisions in large apps.
Since I regularly develop embedded applications with PHP using HTTP as the communications substrate for transactions spanning 6 or more origanisations, I'd like to know whay I shouldn't be using PHP / processing synchronously, and how I can create a near real-time system without synchronous operation.
It'd be a sad world to live in where there was only one programming language/methodoly/idiom - diversity is a great thing. Java provides beans and struts, Coldfusion provides fast development and .NET....(suggestions please). PHP comes closest to solving my problems, many of which are very much in the enterprise applications domain.
Another thing related to PHP vs ASP.
In PHP, it's possible to make sure your Include files are not included more than once. Where as in ASP/VBScript, you can't due to the fact that SSI is processed before the VB code.
I think there's been a slight overlook within the comments about PHP's model for OOP.
Firstly, I was absolutely thrilled to see the enhancements of PHP5. I've been using PHP for... gees... a long time now. But what's always been lacking has been fully implemented OOP. Now, granted, there are ways to do things like method overloading, but c`mon.... really... Now, I know the argument is that PHP is related to the web - not application development. I believe that the PHP community today suffers from this mentality. The fact of the matter is that the world is rapidly shifting towards an SOA mentality, and rich applications presented through the web. In light of this PHP should be regarded as valuable tool for application development.
I would say that while PHP has tremendous strength, it equally lacks in its implementation of OOP requirements. I find that most suggested "design patterns" are weak workarounds in PHP. C# (.NET), Java -- hell even ActionScript have a fully OO implementation allowing effective implementation of recognized design patterns. Futhermore, due to PHP's lack of OO support, true collaborative team development is greatly hindered. This is particularly evidenced in the lack of strict type casting. Legit development teams rely on this to effectively lock down their interfaces, implement error handling, etc etc etc.
I'm very dissappointed to see that languages (like C#), sponsored by the likes of M$ have been able to develop such mature OO languages so rapidly, while PHP remains... well... practically in the stone age.
Once these issues are addressed I think we'll see more support of PHP, and less resistance to its place in the enterprise. Abstraction is a stupid thing to bicker about. How long does it really take to write a good data abstraction layer - that can be repurposed. What's more important is the capability of the language.
Hopefully IBM will jump in here and kick things into high gear. Let's get rid of all the back support and compatabilities for legacy code in favor of maturing the language and increasing its value (and decreasing objections from the enterprise market)
I think it's worth to mention that it's incredible easy to write a PHP module in C and use it in your scripts with the speed of true machine language. All the PHP API functions are there and there's plenty of examples due to the many existing modules and their source codes.
The advantage here is programming the relative simple business logic in PHP and programming those core functions that really require speed in PHP modules, if you really have to.
Compiled Java classes act more like optimised / confuscated scripts and still needs an interpreter in the end.
The only disadvantage about PHP is the somewhat quirky language and inconsistant (and long) function names, which makes it hard for newbies to learn from scratch.
Tim Bray, who - among many other things - co-edited the XML 1.0 and XML namespace definitions, was invited to the International PHP Conference to give a keynote about "How to combine PHP technology with Java based on Enterprise Systems". I had the pleasure to talk with him and I like his spirit. During his keynote, he presented some very interesting comparison between the popular development "frameworks" PHP, Ruby on Rails (RoR, Rails) and Java
http://www.tbray.org/talks/php.de.pdf
in that he show PHP the first in scalability
Comparison of programming languages is a pretty spurious exercise, but here goes:
I have programmed with Perl for many years and have yet to find anything I want to do that Perl can't deliver. It is justifiably described as the "Swiss Army Chainsaw" of programming.
I am much less experienced with PHP but have found it to be relatively lightweight. PHP isn't Perl.
However, in my opinion PHP is much easier to work with and does what it's designed to do more elegantly than Perl. PHP is usually the best option within the areas where PHP is designed to excel.
I wouldn't want to be without either tool. Having both is the best solution.
I have taken ZCE (Zend Certified Engineer) before couple of years and I am working in the field of Compiler Construction. However, from my opinion PHP is the best language that is used to design web solution because it extendable language. As a programmer in C, I found PHP internally as easy as externally.
PHP is the best ever !.
PHP is just and interpreted language though it is strong enough to develop any kind of page you want to develop.
ASP.NET is a part of a framework which means you may use the framework's abilities. Your ASP.NET application can be a part of a mobile, Windows, Windows Service, Smart client or even unmanaged code supported.
ASP and PHP are both programming languages that are commonly used to create websites.
Both ASP and PHP are languages used to build Dynamic Web sites that can interact with Databases and exchange information.
Cost
To run ASP programs one needs IIS installed on a Windows platform server, which is not free. PHP programs run on Linux, which is free.
Speed
If we compare the speed of ASP and PHP then PHP has an upper hand. PHP code runs faster than ASP. http://asp.net-informations.com ASP is built on COM based architecture, which is an overhead for the server whereas PHP code runs in its own memory space.
Platform
PHP programs can run on various platforms like Linux, Unix, Windows and Solaris whereas ASP is mainly associated with Windows platforms. However, ASP can run on a Linux platform with ASP-Apache installed on the server.
Bang