Slashdot Mirror
PHP5 Coming Soon
Grip3n writes "PHP5 is well under development and a beta is expected out by March 2003 and released summer 2003. One of the more notable improvements which many PHP developers desired is a substantial improvement in PHP's performance. This is due to a new object model PHP5 will be introducing which handles objects by reference rather than by value. Co-creator Zeev Suraski states the new object model is inspired by the book, "Design Patterns"."
Who says Moore's Law is obsolete
so, they're planning to release the beta 10 months ago?
...that it'd be hard to "expect" something to be out by March 2002.
I hope they can get around their class and pseudo-object embedding problems that have plagues this language since 3.x. I stayed away from version 4.0 because of that.
Betas release you!!!!
It needs it. The zend engine needs to be redesigned to include class deconstructors and privite members.
AZTEK
How come there is no mention of this on the PHP Website?
I Just found small things like single forms.
Those apps would have the advantage that you can combine a usable & nice looking GUI with a web application (which can be used from everywhere.)
GUIs designed with HTML are usually quite limited.
--
Stefan
DevCounter - An open, free & independent developer pool
created to help developers find other developers, help, testers and new project members.
This sounds like a very good thing, and will address many of the things I find cumbersome about the language (namespaces!). But while it sounds full of objecty-goodness, does anyone know how backward compatible this will be with PHP4? It sounds like major changes are in the works, and rewriting my code in six months sounds about as much fun as putting pencils in my eyes.
This is the voice of World Control. I bring you Peace.
maybe I'll ditch ASP for PHP after all.
Hollow words will burn and hollow men will burn.
Funny, I didn't see it. :-P
From the article: PHP runs seamlessly under Windows, as do MySQL and Apache. WAMP anyone?
.] in the bank to make a great web language. (*cough* M$ *cough*) Neither do you need a couple thousand to deploy a website with dynamic content.
IMO this is what makes *AMP. Consistency between platforms. I use Apache, MySQL, and PHP religiously, and no matter what kind of machine I'm running everything on it is seamless.
I'm not saying this isn't true with other scripting languages, but being able to code on anything with a few tools no matter where I am is EXCEPTIONALLY nice.
PHP's use on large web application projects has been uncertain. Yahoo doesn't feel this way. Neither does Earthlink (WebMail)
But I suppose perception needs to change--you don't have to have a billion dollars [Article, still reading it. .
... because their website just collapsed under the collective weight of /.
My spoon is too big.
In soviet russia, Perl owns U!
I've been blaming PHP for the fact that I haven't gotten around to learning much of Perl or Java - I've been able to do everything I've needed to so far (Nothing TOO complex, obviously) with PHP. I've been "going to start playing with Java to learn it Real Soon Now" for well over a year at this point...
On the other hand - from the article:
"PHP5's object model has syntax very similar to the Java programming language, so it will be easy for J2EE programmers to learn it"
Using PHP as a metaphorical stepping stone to learn Java then?...works for me...
Hacker Public Radio is our Friend
Well, I have a couple of opinions.
:)
1. PHP is a little easier to learn than Perl (at least it was for me).
2. PHP was designed specifically to generate dynamic HTML, whereas Perl seems to be more of a general purpose language.
Then again, sometimes it depends upon the application. There are some things that may be easier to implement in one language than the other, you may need the features of one that the other lacks, etc...
Others may, and probably will, disagree
It's mostly a matter of entrenchment. Perl, being a more general purpose language, would likely perform better than PHP in a lot of areas, including web apps. PHP, however, is known as a "web language" simply because that's where it was marketed too and where it's used. People could (a few do) write full GUI apps in PHP, but there's no real advantage to using it in such an area when there are better options available.
At some point in history, PHP provided a few features which were relatively novel at the time, at least in the Free software arena, which has a tendancy to be a bit behind the rest of the world. [1] At this point though, you can get templating ala ASP in plenty of free and open languages, including perl.
I could be full of it though- other than having the benefit of entrenchment, does PHP have any features that truly set it apart from perl, python or any of the more mature languages?
[1] Not in all areas of OSS, of course, but this statement is relatively true for the mainstream of OSS. There are interesting projects and acedemic research things going on that are doing new and interesting things. Like the regular mainstream, most people in the OSS mainstream aren't interested in doing things better so much as doing them as they already know how.
Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
Why are PHP and Perl paired together so often? (I like both languages; don't get me wrong.)
After spending some time toying around with both, their syntactic similarities seem superficial, like the fact PHP has that "$" prefix on its variables and that they use the ugly "->" operator for OOP.
They seem like distant (free, open-source) cousins at best.
Joe
http://josephgrossberg.blogspot.com/
Joe
http://www.joegrossberg.com
Jeez, I just can't wait for March 2002 to come around.
:(
However, if time isn't circular, then we won't be getting any beta
Does anyone know if there's a push to port PHP to Windows? ChiliSoft ported ASP to *nix and you can do the mod_perl thang (well, almost) with ActivePerl under IIS, so it must be possible. Eh?
php is the best whether it is version 4 or version 5 ...
also taken from here
"PHP is not a blindingly fast language, especially when handling large code bases," notes George Schlossnagle, a PHP performance expert and principal consultant at Omniti, an Internet consulting company. "The lack of built-in script caching and language optimization make its out-of-the-box performance disappointing. Fortunately, when configured and tuned correctly, PHP can provide performance on par with Perl and ASP. "
Chris ,
Php Programmers.
However there are some things which I think need to be cleaned up.
The language is a great big mud puddle of libraries and helper functions. It would be nice if libraries could be imported at script run time (They could be sitting in memory waiting to be imported to negate speed issues) instead being available all the time. Ie If you want to use a function you must explicitly import the module containing the function. Why do I need MSSQL, Postges and MySQL connectivity all at the same time?
And I really hate prefixing all variables with '$'. Maybe they can do something about that...?
a ^= b; b ^= a; a ^= b;
While this isn't false, it did get me on the wrong foot. It appeared to me as if the PHP developers were just realizing that stuff like design patterns exist, and started writing their code accordingly. THe article however states:
It would've been helpful if that quote had been in the post, but it makes clear that PHP5 will have much better OO features than PHP4 currently has.
--
If code was hard to write, it should be hard to read
... and why I won't go back.
... and sometimes expose it on another machine. I'm talking about adding a blank line to a script. It seemed likely that there was a memory error of some kind in PHP.
... transferring to a 3rd-party session system that was incompatible with the 4.x sessions and completely untested by us was not possible by that time.
... I dumped PHP. I was in a situation where I could not trust the underlying technology.
... IIS 5.0 and Active Server Pages. Believe me ... if there had been any other viable option, I would have taken it. mod_python looked viable at first, but I didn't have time to go through the cycle of building a single-threaded python, and verifying the underlying technology. With ASP there was a fairly direct translation from PHP.
... which was acceptable since the users are trusted. Under IIS I eventually needed to create an administrator user which a single page uses - all other pages use a Guest user.
PHP 4.2.3. Windows 2000.
90% of the way into a decent-sized project, I started experiencing somewhat random crashes. Somewhat random in that there seemed to be no consistent way to provoke them, but once they started happening they happened in precisely the same way, consistently.
Simple changes, such as adding a single character to a script, would "fix" it on a particular machine
Downgrading to earlier versions of PHP 4.x didn't fix the problem. Downgrading to 3.x was not feasible
Of course, I attempted getting the source code and finding the problem myself. Unfortunately, none of the 4.x versions would compile. The 3.x versions would - but 4.x wouldn't. Obviously, some black magic was required. Sacrifices failed.
Time was running short. Faced with a very short deadline, I made the only decision I could
As an indication of what dire straits I was in, the technology I eventually recommended to replace PHP and Apache was
I hate that this application has been written in VBScript. The shenanigans I had to go through to get a particular COM control to load and be controlled by IIS - it's system of impersonation doesn't work very well if the COM object isn't specifically designed to be used with it. Under Apache it was able to run as LocalSystem
Obviously I was doing something outside the norm, since there are thousands of web sites which use PHP as the underlying technology. I suspect most of them are running 3.x. But the sheer number of issues that I found with PHP during the relatively short development cycle convinced me that it was in no way mature enough for us to trust our work to it.
...just stick with Zope.
It's by far the best dynamic content management system out there. And the underlying language, Python, is easily the best too.
"Times have not become more violent. They have just become more televised."
-Marilyn Manson
Oh, come off of it. Just because I'm disagreeing with the /. mainstream doesn't mean I'm trolling- my post was (relatively) well-formed and sensical discussing specific points that pertained to the matter at hand. A dissenting opinion, yes, a troll, no. If you don't agree with it, try replying to it with a similar level of intelligence (it's not hard), or is just easier to try to mark it a troll in a poor effort to get the pointage down so no one reads the truth?
(cranky early work day)
Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
I think the main thing PHP buys you is speed and sessions. In exchange you give up a decent, coherent database access mechanism and elegant syntax ($foo for all datatypes is just stupid).
;-)
Note that I'm talking about the as-is distributions here. You can get speed and sessions out of perl (mod_perl, Apache::Registry, Apache::DBI, and the various session modules off CPAN), and you can get a coherent (I've heard) DB access layer using the PEAR DB.php class. (I don't think you can do much about php being ugly code-wise. [by ugly i mean things like variable denotation and the gawd-awful looking preg_* function calls to get decent regexp behavior. what kind of web language puts regexps in the function-call ghetto anyway?]) But many people just don't take the time to get the full oomph out of their development environment, for better or worse. That's why people who do get paid well...
News for Geeks in Austin, TX
PHP rules. If it craps out on your machine, your computer sucks. It works fine on mine and it's incredibly easy to learn with only a little previous programming experience. It's like C, only easy. Perl sucks in terms of server-side scripting compared to PHP. Perl should just stick with processing text. PHP is t3h g00d.
Does anyone know how much rewriting there will have to be to migrate to PHP5? We're using OO in some applications now. Will the way we instantiate objects and reference properties remain the same?
...or why python is better on the backend and the front-end.
.NET as well-thought-out enterprise component frameworks.
Take namespaces for special-purpose library stuff. Or inline eval (include) of logic code (bad, bad, bad). Good analysis (mine) here, including comparitive code to demonstrate my point.
Like Java, Python already does assignment by reference, copy is optional. PHP is just figuring this out. PHP's language leaves much to be desired in team programming and code readability. Using 'Design Patterns' is only half the equation. You can do component oriented programming, but some languages are going to be better than others at facilitaing it in a manner that works in reality. PHP5, unfortunately, won't hold a candle to Zope 3, which is really going to compete at the level of J2EE and
PHP lacks object persistence, multiple inheritance, full-featured transaction machinery, a built-in security model, an interactive command-line interpreter, and it is too tied to web-scripting only. And becuase it doesn't have a security model that binds operations to roles/permissions, it can't easily put gateway methods with bound roles (like Zope's proxy roles) between web code and SQL code, leading to increased chance of SQL injection vulnerabilities.
On the other hand, Zope has object perisistence, transactional RDBMS integration and connection abstraction, templated, componentized SQL methods, a security framework, and Python, which is a much better language (explicit is better than implicit). And if you need to do any sort of content-management, Zope has a mature component-oriented framwork in the CMF, with a killer-app implementation in Plone. It also has XML-RPC, WebDAV, Caching managers, and all sorts of other goodies you won't find out of the box in PHP.
PHP is fast, and it is easy, but it is by no means scalable. PHP offers a gentle slope learning-curve, and quick easy hacks, but is somewhat like a crack addiction. What PHP as a framework needs to do is not reinvent the wheel in the language department, and use a pre-existing, scalable, enterprise-class OO scripting language, and utilize a templating technology that doesn't promote mixing logic and presentation - but what's the point, since it would look remarkably like Zope?
I guess there isn't always a good way to maintain backwards compatability, but it does stink to go back thru large chuncks of code fixing stuff :)
John McFarlane
thinkflat.com
Funny thing is from Yahoo's own slides it would have seemed that Perl would have been the best choice (assuming they had equal access to good PHP and Perl coders).
p hpcon 2002.htm
l ks/yahoo-phpcon 2002_files/slide0041.htm/ ~radwin/talks/yahoo-phpcon 2002_files/slide0002.htm/ ~radwin/talks/yahoo-phpcon 2002_files/slide0003.htm/ ~radwin/talks/yahoo-phpcon 2002_files/slide0004.htm/ ~radwin/talks/yahoo-phpcon 2002_files/slide0005.htm
Referring to:
http://public.yahoo.com/~radwin/talks/yahoo-
YSP = mod_perl.
From the slides, YSP beats PHP on performance. Just as manageable (PHP still requires discipline). Lots of existing Perl code doing other stuff. YSP uses more memory - but what's 900MB(YSP) vs 850MB (PHP)at 500 concurrent requests?
BTW: the page uses javascript where href would do (top 10 web design mistake). Doesn't give me a good impression of cluefulness.
References:
http://public.yahoo.com/~radwin/ta
http://public.yahoo.com
http://public.yahoo.com
http://public.yahoo.com
http://public.yahoo.com
So why did they really choose PHP over Perl?
The given 3 Perl cons, and the "Why PHP slide" are a bit weak IMO.
their website hints .NET, but I don't see anything about compatibility with .net! They could save alot of time by building it around the .net framework instead of interpretting at runtime. IL is faster than parsing the langage anyhow.