Domain: phplens.com
Stories and comments across the archive that link to phplens.com.
Comments · 12
-
Re:its not about 'like'
http://www.killerphp.com/articles/will-ruby-kill-php/ http://phplens.com/phpeverywhere/?q=node/view/222 well. in my eyes, ruby is just another fad pushed forward to make new money. its not only about the language itself, its the widespread usage.
there has been many languages which were touted to be 'better', rightly or wrongly, that faded away. -
Re:PHP.net is great.You can use the microtime() function. Additional details website posted below to check
http://phplens.com/lens/php-book/optimizing-debugging-php.php I think php necessitates the usage of php.net etc because the functions don't seem to follow any kind of sane design or pattern. I mean (hypothetically) array_search() vs search_array() etc.
-
Re:Java is great for learning
Non-scalable like Yahoo, the world's busiest web site, you mean? Yeah, thought so. Don't get me wrong, PHP has many problems[1]. The biggest of them is probably the ease with which an incompetent moron can create terrible code (a trait it shares with Perl).
I'll still maintain that PHP is not inherently scalable for applications without major hack type gyrations. The persist to DB method discussed here is something that works for low-volume high latency type applications. While PHP may be great at serving semi-stale or static content, high volume HA systems are not in its forte at this time. Even if you could work around those issues, why force a square peg in a round hole when standard relatively easy to use solutions exist? (Look at Weblogic or Resin to see high volume high performance HA capabilities, and you'll understand one reason why Java holds the sway it does in large enterprises)
PHP certainly does not have a monopoly on the ease with which an incompetent moron can create terrible code. Java, C++, C# all have their hats in that ring as well with the slavish devotion to bad patterns witnessed in all of those. I'll never figure out why someone wants to have 400 cookie cutter classes with massive overlap in code (read as cut N paste) for something that could easily be coded in a 100 lines or less in a single class, all for the sake of following a pattern with "type-safety", which is completely bogus as objects are serialized or marshalled across the wire via binary or XML streams. It merely creates 400 points for 400 errors, versus a single point with a single error. I know which system I'd rather work on. -
Tiny bit of troll food."Writing Portable SQL"
Wait.... it can be done? No Way! My point holds for anyone who uses MySQL-specific, Oracle-specific, or whatever "dialect" of SQL. Don't blame SQL when someone asks you if you can port to a different dB and you can't.
-
Re:Webservices gone mad
"Please tell me how this can be done in less than 10 lines of code in php."
PHP Lens, there are others.
I do find your santimony amusing though. You go on bragging about how ASP.NET is better then PHP as if that says something. Is it better then webobjects? Is it better then tapestry? is it better then ruby on rails? Is slapping gui controls in visual studio easier then using Java studio creator?
ASP.NET is just another freakin web application toolkit. To me it's in the middle to the bottom of the pack. There is nothing special about it, there are many products that are easier to use, create more cross browser applications, cost less, and make more scalable and easier to maintain code.
I just don't get you guys obsession with such a mediocre tool and programming paradigm. -
Re:Coldfusion still wins my heart
-
Re:It's a threading issue
According to this article php with fastcgi is an very performant option under IIS. Perhaps the same should be tested for apache2.
-
Re:Switch from asp - php(5)
Good summary for ASP to PHP switching here: http://phplens.com/phpeverywhere/node/view/30
-
A (forked?) PHP port to Parrot before Perl ships?
Parrot!!!
Forth is up. Is Python ready?
PHP real soon now? -
Would this do?
You'd expect the purveyors of PHP tools to answer developer requests, and they have.
There are several alternates around.
If you want to try something a bit different, there's this or this.
-
Re:what does this cover?
No, apache 1.3 sites are vulnerable, but you can protect yourself from the memory limit problem temporarily by disabling it as suggested above.
As people are going to be recompiling PHP it's probably timely to recommend the "--enable-inline-optimization" switch which should be passed to the configure script. More to be found here Oh, and get yourself an accelerator. I use PHP Accelerator although it's not open sourse unfortunately. -
Re:So many oss/fsf RDBMS...