It seems that it interchanges "productive" with "writing clean code". PHP is ugly but can be productive. Haskell is beautiful, but well, I know a lot of people encharmed by it, but no-one productive (i.e. delivering products quickly; it's not the same as solving pure, mathematical problems).
Do you know alot of Haskell programmers? Because I'm enjoying my typesafe SQL queries, typesafe intra-application linking, typesafe templating, etc. Haskell is capable of far more than "pure, mathematical problems"—indeed, typed IO is a premier feature of the language. edit: sorry, this was pretty defensive; I shouldn't have written this comment so hastily.
Learning Curves for Different Programming Languages
61–70 of 221 posts
Re: Learning Curves for Different Programming Languages
#62For me it was simple to learn PHP and create something 'useful', basically every web server is capable of running it which makes my life a lot easier as well.
Surely the fact that someone can hack together code within a few minuets that doesn't profess to be a coder is a good thing, regardless of the language that there using?
There is no better programming language than the one you know.
Re: Learning Curves for Different Programming Languages
#63He wanted to make a cheap joke, but PHP should be the opposite: productivity is rather high, while self-assesment is low.
As a primarily PHP developer, we get told all the time at conferences and places like this how awful we are. I actually wrote a fairly popular post not too long ago about a Haskell speaker being actively hostile against PHP developers. Our mantra has become "I can't hear you over all this work I'm getting done" I've worked in many other languages and nothing really compares for how quick I can knock something out in…
Re: Learning Curves for Different Programming Languages
#64What about ruby ?
I think the fact that Ruby didn't even make the list tells a lot about how far it has fallen in terms of mindshare. I have nothing against Ruby, its people or its ecosystem, but it's beginning to seem like a bit of a flash in the pan.
Re: Learning Curves for Different Programming Languages
#65Few languages have that sheer "Survive" feel to it. For that alone I think PHP should be celebrated. Note: I'm not a PHP developer.
Re: Learning Curves for Different Programming Languages
#66Earlier quoted context omitted.
> Facebook uses PHP This is the common rebuttal of PHP jokes - but pointing to a sole outlier is rarely a solid defense. Especially when they have created Hack[1] and HHVM[2]. So it's not entirely accurate to say they "use PHP." [1] https://en.wikipedia.org/wiki/Hack_(programming_language) [2] https://en.wikipedia.org/wiki/HipHop_Virtual_Machine
Lol, Wikipedia which you linked to is PHP. Roughly half the web runs on Wordpress for crying out loud.
Re: Learning Curves for Different Programming Languages
#67Does anyone know how the graphs were drawn?
[1] https://github.com/Dobiasd/articles/blob/master/programming_...
Re: Learning Curves for Different Programming Languages
#68Really don't understand the pure hatred that people have for PHP, I'm at network engineer and I don't have any desire to become a programmer because I love my job, however I've wrote some very useful applications that myself and my team use on a daily basis to make networking easier for us. For me it was simple to learn PHP and create something 'useful', basically every web server is capable of running it which makes…
I don't understand why mechanics say some cars are better than others.
Re: Learning Curves for Different Programming Languages
#69Re: Learning Curves for Different Programming Languages
#70He wanted to make a cheap joke, but PHP should be the opposite: productivity is rather high, while self-assesment is low.
I think by "self-assessment" is meant something more like "self-regard", the whole being taken to mean that PHP programmers have a relatively high opinion of themselves, which is not justified by the code they generate. I gather the author is perhaps not a native speaker of English, so perhaps this is a subtlety which has simply passed him by. As such, I've opened an issue on Github to suggest the replacement of the…