Do 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.
Re:Laravel : A New PHP Framework
by rmATinnovafy on Sunday May 27, 2012 @01:24PM
(#4030511)
Why not PHP?
Imagine the conversation we would have if I hit the reply button and wrote:
Why PHP?
Seriously, it does not take the conversation forward.
Re:Laravel : A New PHP Framework
by rmATinnovafy on Sunday May 27, 2012 @06:17PM
(#4031189)
I 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.
Or ditch it already and write Python/Ruby.
Re:Laravel : A New PHP Framework
by rmATinnovafy on Sunday May 27, 2012 @09:30PM
(#4031594)
Why don't we ditch Python/Ruby and just go with CLISP?
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.