> Let's look at people who know how to program, you know, the guys who participate and win awards at ACM ICPC and TopCoder.
Is goalpost moving. He's not suggesting that PHP is a great language to start with if you aim to become a great algorithmic programmer, rather that it's a great language to start with if you aim to become a competent web developer.
> Saying "but Facebook and Wikipedia use PHP!" doesn't count :-)
But why not? Surely "X and Y outrageously successful projects use Z" is a valid argument for Z's power as a programming language?
- technical environment: the Facebook/Wikipedia/generally-any-web-startup architects get to choose their technical environment 100%; in most corporates you need to integrate with legacy applications and databases in a specific environment, often enforced by IT policy, and this imposes significant constraints on which languages will be feasible options
- interoperability: for large, modular systems developed by disparate teams over decades with little or no standards or co-ordination, a statically typed language can be absolutely invaluable for ensuring interoperability and discovering usage (documentation is typically non-existent in these environments, as are tests, and the latter is seldom - often impossible - to retrofit); even for new systems, static typing can save a lot of time when developing and integrating new work across large teams, in my opinion
- resistance: business and technical knowledge lives in developers who are part of an ancient stack, e.g. Microsoft or Oracle or Borland; switching to PHP or Python or Ruby etc. means convincing these people to learn very different new technologies (good luck - won't happen), figuring out how to interface with legacy stuff using a language outside of the stack, introducing new tool chains, etc.j
- time & budget: even if the existing developers are keen to learn, it's tough convincing the project manager you need an extra month to go through the upskilling process and that you need to spend time researching interoperability options, and that inevitably you will run into future issues, etc.; the problem is most projects are run and budgeted for on a local cost benefit analysis and very rarely would the benefit of switching languages for one project be worth it (even though, in the big picture across multiple projects, it may very well be)
An observation: whenever this debate comes up on the HN, the proponents of modern, dynamic languages are invariably people working in closed environments where they have the freedom to set standards, do things right from the beginning (coding standards & reviews, tests, documentation) and the ability to make technology selections across the board. Often this freedom is not a characteristic of other environments, and consequently the language used in a one environment may be unsuitable in another.
Any language is a good language to start programming.
Explain how learning PHP first somehow cripples your advancement as an engineer. You can't just say "my friends didn't do it". Otherwise you're really just being elitist.
Everyone I know who was a kid in the mid-80's and who is still programming today learned programming from this crappy language called BASIC.
When you start out learning to program all you need to learn is about variables, functions, basic constructs such as loops and if's etc. and maybe a bit about data types. PHP let people do exactly that and guess what, today people don't write command line apps anymore. Their context of learning to program is by making a website.
Most people who are serious about programming and learn to program with PHP are smart enough to learn other languages as well just like me and my friends did after we first learned BASIC.
I want to warn people against it, because I think I lost a lot of time along the way doing stupid irrelevant things.
You see, instead of learning the basic stuff like algorithms and data structures, I was writing visitor counters and guestbooks. As a result, in a few years, those who started with Pascal or even plain old BASIC, were already coding circles around me :)
Maybe it's not as much about the language as about having a wise teacher who can push you in the right direction. I didn't have one, unfortunately.
P.S.: on the other hand, I was able to sell my skills much earlier than my peers: I made my first money on php. But I don't think it's important: it's about being a good programmer, not selling you code as early as possible.
PHP has all the usual programming constructs and is easy enough to get into that I think it's a great language to start out in.
And discounting web apps as not real programming is just wrong. Some of the most challenging programming problems today are in the web field. Some people write low level software algorithms, and some write higher level ones that scale to billions of people using them concurrently. They are all 'real programming'. Not all web programming is request.getParameter("foo") and form processing.
Yes it does, so what? Programming is not just fors and ifs and classes you know. There is more to it. You won't learn it if you limit yourself to the PHP cage forever.
> And discounting web apps as not real programming is just wrong
Did I say anywhere that web applications are not "real programs"?
On a side note, why the hate on Pascal? It's a lot better than PHP as a starter language, it teaches structured programming from the ground up.
Start out in pascal these days and try getting a job!
PHP is only a cage if you let it be. PHP has all the tools you need to build anything. I prefer python any day, but I don't like to see people who never got beyond the newbie level criticize something just because they couldn't make it work for them. As the old phrase goes, a bad workman always blames his tools. The criticisms you have leveled at php are all the usual newbie ones, not understanding how stings and numbers are equated etc, it's like a python programmer not getting is vs ==, or a JavaScript programmer not understanding undefined, or a SQL programmer not understanding why null = null for purposes if group by, but not in equality testing. You have to undertake the language in hand properly before you can use it properly.
And yes you did make that assertion at the beginning of your thread. Go back to the first comment you made here on this thread.
I don't think we understand each other. PHP has all the tools available to allow you to build anything within a certain problem domain, i.e. web programming. If you start with it, your focus will be shifted towards that domain. I think a better idea is to start with something more general-purpose, more consistent, get a good foundation, and then look at all the available options and say "ok, now I want to work in this field".
> I don't like to see people who never got beyond the newbie level criticize something
It is true that I don't have 10 years of experience in php, but I don't see why I should have continued investing valuable time into learning this platform when there were clearly better options available.
> not understanding how stings and numbers are equated etc
I understand it. I just think it's a bad decision to do it that way. Also note how all of your examples with other languages have reasonable logical explanations. The particular type conversion rule we were talking about does not have such an explanation.
> And yes you did make that assertion at the beginning of your thread
I only said "..slapping together websites (which is not really programming, let's be honest)" Web sites are web applications are different things in my book :)
Serious questions.
I've been using PHP professionally for 5 years now, haven't once needed either of these "deeper issues" to be solved, so I'd appreciate it if people would stop bitching about the language and actually explain why PHP is bad (with examples).
Does that convince you?
2) because processing some HTTP requests can be a tad bit more complicated than "do a select from a database and substitute the values into a template"
2) Explain - seriously. To me this level of thing isn't the realm of PHP but rather the web server in front of it. If someone is doing something that requires multi-threaded programming, they clearly don't know what PHP is used for and they chose the wrong tool. Their choice doesn't invalidate PHP for it's intended use case.
2) I'm not sure what this statement has to do with anything.
Well then use ===, but when a string contains numbers then php will do the type conversion for you. It's a convenience.
It may not work correctly by your definition but it's pretty intuitive and useful the way it is.
To not write cron jobs that get triggered every n minutes to do some potentially time-consuming tasks, for example.
Basically, the "facebook argument" is widely used to prove that php is good for solving real-world problems, but the truth is, facebook is a complex system and it is not written entirely in php, like some people seem to think.
> PHP is a great language to start programming!
No. PHP is not a good language to start programming. And I mean programming in a broad sense, not slapping together websites (which is not really programming, let's be honest). Let's look at people who know how to program, you know, the guys who participate and win awards at ACM ICPC and TopCoder. There are several such people among my friends. Exactly zero of them have started with PHP. Some have started with Pascal, some with Java, some with C++. None with PHP, even though it was available and widely used when they started. I wonder why.
> Once you started, PHP is also good for “real” programming (you know, object orientation and stuff).
First of all, "object-orientation and stuff" is not a measure of how good a programming language is. So you'll have to bring a better argument to explain why PHP is good for "real" programming (whatever that term means). Saying "but Facebook and Wikipedia use PHP!" doesn't count :-)
> PHP is not as bad as they say. There are issues, like with every language, but they rarely cause problems in practice.
Actually, it is. It has some deeper issues that lack of consistency in function arguments. Some of them really do cause problems in practice, like its retarded type system and lack of sane support for multithreading. But I'm not going to name them here because there are tons of articles on the internet explaining those issues. You have probably read some of them. If they did not change your opinion about the language, then I surely won't be able to do it.