PHP Namespaces
PHP is getting namespaces finally (along with some other good stuff like closures and lambda functions). Unfortunately the devs decided that backslash would be a good character to use as the namespace separator.
Fredrik Holmström shows some issues with this idea. I also liked this summary, in a Slashdot comment. At least one person has already dumped PHP because of the choice.
a Padded Cell our articles site!
Abhishek Reddy posted this at 10:42 — 28th October 2008.
He has: 3,348 posts
Joined: Jul 2001
I\'d ask, what could possibly go wrong\?
As someone who began jumping the PHP failboat a couple of years ago, I must say, it's a long drop till you hit the water.
JeevesBond posted this at 14:46 — 30th October 2008.
He has: 3,956 posts
Joined: Jun 2002
Out of interest: what would you use in place of PHP for a Web application. Python + Pylons/Django?
Abhishek Reddy posted this at 01:52 — 31st October 2008.
He has: 3,348 posts
Joined: Jul 2001
I'm prepared to use a number of languages and systems. I'm not terribly fond of comprehensive frameworks (they work sometimes, not always). What I look for in a basic stack is: a dynamic language, a native HTTP server, a native DSL for markup output, and a data store module.
For example, a Ruby stack I'd use is Mongrel, Markaby and DataMapper or Sequel; or merb. With Python, I might use Twisted, Nevow (particularly Stan), and Dejavu. With Lisp, I use Hunchentoot, cl-who (customised), and Elephant. Recently, I've been experimenting with Compojure for Clojure.
My preference is to live inside one runtime per site – screened behind a proxy – each using internal DSLs for the various concerns. This isn't appropriate for all situations, however. It's best for the small-scale apps that I develop, with a small team – if any. So I'd happily use a big framework, external templates, or attach to Apache, if needed.
This is partly what makes it difficult to drop PHP. There's a big leap in initial complexity, especially in deployment configurations, and the diversity of modules and libraries to learn, test and maintain. PHP, in contrast, gives you a one-size-fits-all Plattenbau architecture.
The main constraints dictating the choice of system are: what the host provides, budgets or deadlines, and legacy applications. There are ways to deal with each of these, but invariably one or the other is a fixed condition in favour of PHP.
pr0gr4mm3r posted this at 13:57 — 28th October 2008.
He has: 1,502 posts
Joined: Sep 2006
Meh, there hasn't been anything I wanted in a web application that PHP couldn't handle. I don't see what everyone's problem is.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.