5 ms·
I agree. If someone wants to launch a new PHP framework in 2012, they should at least talk about some of the leading PHP frameworks (Symfony, CodeIgniter, CakeP
by lkrubner 14y ago
I agree. If someone wants to launch a new PHP framework in 2012, they should at least talk about some of the leading PHP frameworks (Symfony, CodeIgniter, CakePHP, etc) and say why those frameworks are not adequate.
Optionally, one could include a discussion of why one should use PHP, but I realize there is convenience and brevity to be gained from simply assuming you are talking to an audience that is already sold on PHP, rather than Java or Ruby or Python or Clojure.
- ams6110 14y agoDo all Java, Ruby, and Python frameworks include a discussion of why one should use those languages? Seems to me that when you're evaluating frameworks, the language decision is probably already made.
- rmATinnovafy 14y agoWhy not PHP?
- __mark__ 14y agohttp://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/ http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-de...
- lkrubner 14y agoImagine the conversation we would have if I hit the reply button and wrote: Why PHP? Seriously, it does not take the conversation forward.
- rmATinnovafy 14y agoI know its not perfect, and has some little loved features. But for me a language is a tool. And tools are meant for specific jobs. Like I wouldn't use a phillips head screwdriver where a set of pliers is needed. If php is to advance we should welcome all tools that evolve it.
- antihero 14y agoOr ditch it already and write Python/Ruby.
- rmATinnovafy 14y agoWhy don't we ditch Python/Ruby and just go with CLISP?
- antihero 14y agoBecause Python/Ruby are decent languages, CLISP isn't objectively better, it's just different.