Unlike the author, I think they are still a bad idea when added to the PHP language itself. ![]() when you update the Symfony2 source or vendor libraries) when debugging, one will need to place break points inside the bootstrap file.”Īnnotations added into the comments. As in: “Note that there are two disadvantages when using a bootstrap file: the file needs to be regenerated whenever any of the original sources change (i.e. People are adding pthreads yet PHP lacks the tools to manage concurrency ( for a point of contrast, check out Clojure).Ĭomplicated code cache systems in Symfony. What is cutting edge in the world of PHP nowadays? If you build a CMS, and you have traffic that needs 100 webservers, then you need to deploy the whole CMS to each of the 100 webservers. I can tell you what advantages PHP offered in 2000, but what does it offer today? It is slow, it is cumbersome, the systems have become very complex, the uncompiled nature of PHP has become a problem as people try to do more ambitious projects with it. I feel that the people who nowadays use PHP in corporate environments have forgotten why PHP first appealed to anyone. I have already written my criticisms of some the systems that I had to work with. These last few years I was hired by several corporations ( Wine Spectator, Timeout) to work with their systems, most of which was PHP, and most using the Symfony framework. From personal experience, I was able to access 5K lines of C code using about 150 lines of Julia - and no extra glue code in C. Unlike with native interfaces in other languages, you can call C code without writing a single line of C, and so I anticipate that Julia’s libraries will catch up quickly. Julia’s only drawback at this point is the relative dearth of libraries - but the language makes it unusually easy to interface with existing C libraries. But other languages make this even easier nowadays: For those of us who were frightened of C, it gave us nice wrappers around C functions. It was optimized for the web, but that hardly makes it unique nowadays. But now that we have a wealth of great package managing tools, PHP’s greatest strength is rendered obsolete. PHP’s all-in-one philosophy solved the package management problem that existed at that time. And even the Linux package managers have gotten better since 2000. “Package managers” at that time would have been a reference to Linux distros, which sort of introduced the idea. Nowadays we are spoiled with awesome tools like Bundler for Ruby and (my favorite) Leiningen for Clojure. At that time, there was nothing like modern package managers. That was probably the key thing about PHP, at least for me. Managing dependencies was a very complicated situation.Ĥ.) ASP - as good as PHP is most ways, except it was a Microsoft tool, and using it would have sucked me into the expensive world of Microsoft.įor 3 of these, I’ve written “Managing dependencies was a very complicated situation”. There were modules in CPAN that could do almost anything, but you had to download and install them. ![]() Managing dependencies was a very complicated situation.ģ.) Perl - as good as PHP in most ways, except that it lack any kind of package manager. ![]() Managing dependencies was a very complicated situation.Ģ.) Java - better than C, but still too verbose, and compiling took time, which made development slow when you were dealing with a rapidly evolving website. Compiling an app took time, compiling was slower back then, there were fewer Open Source tools, and proprietary tools were outside of my budget. ![]() My criticism of those 4 were:ġ.) C - too complicated for a fast changing website. At that time, if you wanted to build a website, the main alternatives were C, Java, Perl and ASP. I started using it right before the official release of 4.0 in April of that year. I was a huge fan of PHP back in the year 2000. You can contact lawrence at: or follow me on Twitter. (written by lawrence krubner, however indented passages are often quotes).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |