Obviously, the user doesn't care about the backend of a system. From a developer's point of view, though, is PHP still acceptable to use for new projects, even though "better" languages like Python and Ruby are way more available than they were years ago? Or is it no longer considered a good idea to use PHP if I'm starting with a clean slate?
Ask HN: Still acceptable to use PHP for new projects?
1–10 of 23 posts
Re: Ask HN: Still acceptable to use PHP for new projects?
#2Re: Ask HN: Still acceptable to use PHP for new projects?
#3Re: Ask HN: Still acceptable to use PHP for new projects?
#4On the other hand, putting the language itself aside, dev-tools and existing libraries are few-and-far in between (and they usually suck). And when I say libraries, I don't mean snippets on the internet.. true libraries with tests, etc. Besides the frameworks and a handful of active packages on PEAR- good luck.
There is a reason why Ruby and Node have awesome tools (gem, npm, webrick, jasmine, cucumber, etc. etc.) and a very active library sharing mentality.
Re: Ask HN: Still acceptable to use PHP for new projects?
#5Re: Ask HN: Still acceptable to use PHP for new projects?
#6The language you use doesnt determine whether you're a good developer or not. I have used other languages (node, python, ruby) and I still prefer php, because its quick and simple. Its syntax may not be as beautiful as a python or a ruby, but it php just works, and it powers hundreds of millions of sites.
Bottom line, use what your comfortable with, but be open to exploring other languages. Dont ever let someone tell you a language is better than x. Make those decisions yourself.
Re: Ask HN: Still acceptable to use PHP for new projects?
#7Just a few quick thoughts:
PHP is - in most cases - very tightly coupled to the HTTP request. This can be good or bad depending on what you're building. Doing a lot of offline processing? Probably bad. Serving up web pages? Probably good.
There's no (or little) state with PHP (you do have the session, which can be pushed to memcache), so - generally speaking - running your application across a bunch of web nodes isn't too hard to implement (even scaling the horrible legacy style code that helps give PHP a bad reputation shouldn't be too hard). This may or may not be important to you.
There's really no one true way with PHP - it can be used for a simple 10 line script, or for a large scale web application. If you like (or need) that kind of flexibility, it could be a good choice.
Bottom line is - it's certainly sill worth considering, just know why you picked it (or whatever other language/platform you use).
That said "it's what I know" or "I wanted to try something new" aren't necessarily bad reasons.
Re: Ask HN: Still acceptable to use PHP for new projects?
#81. Its easy to scale (horizontaly) because it has a "share nothing" archtecture.
2. like tjlyte states its centered on the HTTP protocol which is almost always your app protocol
3. its fast
4. its an "easy" language to program, but still supports OOP, namespaces, closures, anonymous funcs, etc.
5. Its highly portable
6. It has a very extensive developer base, tons of libraries and frameworks that are starting to reach enterprise Java level maturity (Flow3, Symfony2 for example )
Re: Ask HN: Still acceptable to use PHP for new projects?
#9On one hand, you should use the tool that you know best. On the other hand, putting the language itself aside, dev-tools and existing libraries are few-and-far in between (and they usually suck). And when I say libraries, I don't mean snippets on the internet.. true libraries with tests, etc. Besides the frameworks and a handful of active packages on PEAR- good luck. There is a reason why Ruby and Node have awesome t…
Re: Ask HN: Still acceptable to use PHP for new projects?
#10There are pros/cons to any language. If you're developing something web related, PHP is certainly worth considering (especially in your case, as you have experience with it). Just a few quick thoughts: PHP is - in most cases - very tightly coupled to the HTTP request. This can be good or bad depending on what you're building. Doing a lot of offline processing? Probably bad. Serving up web pages? Probably good. There'…