Sunday, May 18. 2008PHP vs. JavaTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
I'm sorry but I could not disagree any more, PHP is the promised land for the "not invented here"-syndrome. How often do you see large libraries re-used? Just look at all the hundreds of ORM/db-layer implementations we have lying around.
And trying to make the fact that many php-devs don't have a formal CS background and "need to look at other peoples solution to figure it out themselves" as a good point is just beyond me.
IMHO you often do not benefit as much of reusing code in PHP as you would in other languages because:
- you don't want to go the whole way (ORM is a good example there) - the code you need is so small that you can write it yourself But then still the best practices make the solutions very similar again. Even if the code is different (if the developers are experienced ones). Therefore "not-invented-here" might not apply to the actual code but to the concept. Regarding developers without in-depth computer science background: I think this is one of PHP's assets and fundamental differences to other languages: PHP tries to make coding so simple that even inexperienced users can do it right. These guys show their solutions and look at other's. This gives you a lot of simple examples you can work with as a starting point. IMHO this is an important aspect and always has been a driving force for PHP's success...
Well yeah there are a lot of PHP Developers without a CS backgrounds and that produces a lot of un-reusable code. I know some people who are not able to code PHP but able to find solutions by copy and paste some scripts. But if you have to change them later it´s horroble.
Right. But IMHO this is still better then the same persons trying to code something from scratch...
Well, I have a degree in computer science (MSc conversion course) and trained in Eiffel, Java and Visual Basic. I now use PHP as my language of preference because it avoids all the fiddly bits about connecting up the programming language with the internet, all of which has nothing to do with any real programming I want to do, and similarly all that messing about with the join between HTML and Java which is servlets (yes, I've programmed with them). With regards to borrowing: yes, I do from time to time - and reusability is in the programmer's book of virtues - as well as making my own stuff. I do the former where the nature of the beast is well-established and the latter where it is either a specific function of a new application or I'm just adapting something well-known to meet particular needs.
So you're saying that its a good thing that php developers often poison you're code base with code they found on the net?
imho this is the kind of mentality php should be struggling to distance itself from.  Well i was referring to people with comparable skill-set.If you only have people who copy code without understanding it, you are of course right. This is what you don't want. But then it's the people, not the fact that they let themselves be inspired by code they find on the net. Smart developers will search for proven solutions and they will see very soon if a piece of code is good or bad. They will isolate the best ideas and code something new which is hopefully better.
This post is pure, unadulterated flamebait. A lot of theoretical yapping without a single real-world example.
You are right in the aspect that i did not give examples and used a word like "not invented here". Will never do it again.
However, have a look at Plat_Forms. Cheers, Gaylord
A litte quote from "How to become a Hacker" from Eric Steven Raymond:
"2. No problem should ever have to be solved twice. Creative brains are a valuable, limited resource. They shouldn't be wasted on re-inventing the wheel when there are so many fascinating new problems waiting out there. To behave like a hacker, you have to believe that the thinking time of other hackers is precious — so much so that it's almost a moral duty for you to share information, solve problems and then give the solutions away just so other hackers can solve new problems instead of having to perpetually re-address old ones." I think this quote fits to the article
... and in our case, the thinking time of the hacker who solved the actual problem once, is valued even more by hundreds of people takign this solution and building their code according to the precious hacker's ideas.
Problem solving is not only the code, it is the ideas behind it. And especially in the PHP wolrd, if the idea is great, the code might only be a few lines...
I think you must use PHP where you find it useful,
Java and C# can be also use where you need to write compile code. Happy coding.
ColdFusion takes half the time to code and is more scalable than PHP. The only benefits which PHP have are that it is free and that it is popular.
Furthermore, it is multi-threaded and can use any Java class as easily as if one were writing directly in Java.
Sorry, but i tend to disagree with allmost all statements in this post. I dont know cold fusion well, but i doubt that it is more productive than PHP if you take one of the frameworks (Zend Framework, Symphony). Second, i doubt that there was ever a site like Facebook or StudiVz or MyVideo built with cold fusion. So scalability of cold fusion can not be better than PHP scalability.
Regarding Multi-Threading and Java-Classes: Well, if you need this, why not code in Java? There has been a time when cold fusion was quite popular. But i guess there are good reasons why these times are over... |
Calendar
QuicksearchArchivesCategoriesSyndicate This BlogBlog AdministrationPowered by
ArchivesTop ReferrersChoose Language |
|||||||||||||||||||||||||||||||||||||||||||||||||
