61–70 of 182 posts
Earlier quoted context omitted.
If this is the case, then maybe PHP's role is a rapid prototyping language which is replaced when the codebase gets to a certain size.
Generally that size is not more than about 5 files.
I think PHP (5.x/6x) is still applicable to any developer, new or old, experienced or not. Many of us cut our teeth on PHP's simple scripting concepts, and that shouldn't change. And from what I've seen from past history, it won't. There is a tremendous amount of backwards compatibility in current versions of PHP that allows one to follow the same approach to Web development that those did back 10-15 years ago with P…
I went Perl -> PHP and have been there ever since. Not because I'm too lazy to learn another language, but because it has done everything that I have needed it to do, and when I found something that it couldn't, I looked elsewhere for that one aspect of the project.
Isn't it our role as developers to push the boundaries of our chosen language? I'm pretty sure back when Javascript was being thrown around, they wouldn't have imagined what it is today.
Trying not to sing praises, and throwing fuel on a fire that should have died a long time ago... To each their own.
Earlier quoted context omitted.
Python has often been called an easy to learn language and a good first start because it tries to be easy to read. Does that mean that it is also a beginner's language that people eventually are supposed to move on from?
People who pickup Python will always stay and never move on completely. My programming carear startet with perl -> php -> python and i found one holy grail to solve most of my problems. Python had an easy entry point the same as PHP but when you jumped over the first learning curve and discovered the complete ecosystem it`s mindblowing. I never had that feeling with PHP you could do websites and thats it. And most of…
It's a nice language, but it's not for everyone.
I come from a C++ background, and early last year tried my hand at web development. After hearing about all the stuff about how PHP was an "old", kludgey language, I tried to learn python, and go the webpy. It was doable, but I kept running into issues all the time. I gave up and switched to PHP, and I have to say that it was a much easier experience. For the most part, everything just worked. Regardless of how kludg…
PHP works fine as long as you're never exposed to a better way. In a year or two start using rails. You'll come back to PHP and wonder why anyone would ever make a hammer with two claws.
A more apt comparison is rails with symfony2 or zend framework2.
Earlier quoted context omitted.
Generally that size is not more than about 5 files.
Yeah good one. Wordpress is a great example of a huge failure written in PHP over 5 files, right?
You want a vision? Here is one - make the mess we have at the moment work. I write in php for the better part of 4 years now and hate it every day. And I have written in c++ before that. Ask 20000 developers what are their main pain grievances sort them by "popularity" and just remove them one by one. For me it is the hard debugging, the include mess and the "extremely" creative ways parsing and runtime errors are co…
Thanks to namespaces, PSR-0 and Composer, I no longer have to worry about "include mess". Use an autoloader, that's what it's for. If you're finding you have to include a file to access information in it, that tells me you're not testing your code.
The only error I've run across that gave me pause, for a second, was the T PAAMAYIM NEKUDOTAYIM. A quick, 5 second Google search gave me the information I needed.
You want a vision? Here is one - make the mess we have at the moment work. I write in php for the better part of 4 years now and hate it every day. And I have written in c++ before that. Ask 20000 developers what are their main pain grievances sort them by "popularity" and just remove them one by one. For me it is the hard debugging, the include mess and the "extremely" creative ways parsing and runtime errors are co…
You want a vision? Here is one - make the mess we have at the moment work. I write in php for the better part of 4 years now and hate it every day. And I have written in c++ before that. Ask 20000 developers what are their main pain grievances sort them by "popularity" and just remove them one by one. For me it is the hard debugging, the include mess and the "extremely" creative ways parsing and runtime errors are co…
Earlier quoted context omitted.
It's not an "empty, non-contributing comment" to those of us who have had to use PHP, especially after years of using far better languages. It rings especially true to us who have seen the horror systems implemented in PHP can be.
I'm one of the "us" you mention, and in fact I'm still working with PHP. The comment added nothing to the discussion, and was still useless. I'm aware of the drawbacks of PHP. I look forward to a day when I'm no longer using it on a daily basis. But Tichy's comment added nothing to this discussion.
Worthwhile reading the email that preceded it: http://news.php.net/php.internals/64763 The response hardly seems warranted. The vision is pretty stated there.
Stuff like this: http://marc.info/?l=php-internals&m=135083835232016&...
Sometimes he contributes to discussions in a very positive manner. But too often he degrades the discussion into BS rhetoric and greatly demoralizes contributors (I know I am not the only one to voice disdain, I may just be the first publicly)...
I guess you can say I just had enough...