On Fri, Jan 7, 2011 at 11:54 AM, Joshua Kehn <josh.kehn@xxxxxxxxx> wrote: > On Jan 7, 2011, at 1:48 PM, Nathan Nobbe wrote: > > shrug, you must not be too familiar with php then. 9 times out of 10 it's > the natural, perfect choice for a cli program. there are situations where > you get past what php is ideal for on the cli, typically when you get into > heavy forking or require threading. > > >> It does completely depend on your mastery of the language. If you're very >> good with PHP and you don't often do non-web things it might not make sense >> to learn another language as well. > > > why bother learning 2 languages when 1 will suit most needs perfectly? for > most folks who work with the web and a typical deployment environment like a > linux server, the second language of choice most likely would be a client > side one like javascript. > > -nathan > > > You can't say that PHP is a more natural CLI choice then bash or Python. > Maybe I'm using PHP too much for web development. Perhaps I am unfamiliar > with it. > Um, I just did say it :P It's pretty simple, I already know PHP, I don't know Python or BASH well enough, obviously PHP is the best choice for a CLI program in this case. Yeah.., try writing a few scripts in PHP on the CLI, you'll find it solid for many applications. > Why bother learning other languages? Is this a joke? Why should someone > stop learning *ever?** *Having a mastery of multiple languages can only > enhance you. > No, it's not a joke. The idea is why bother learning an language that will score you little milage, in the context of the one you already know well. For example, if I'm a Web developer coding what CLI requirements I have in PHP, then I might venture to learn something like Javascript before ever touching Python. So yes, having mastery of multiple languages can help you, but it's best when these multiple languages don't overlap as much as PHP and Python. -nathan
