Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

General Discussion

PHP becoming obsolete?

I recently asked the Google Coder team if they planned on adding PHP and SQ support to Coder and thus far the only reply I've gotten is this.

"If you already know Javascript, then why not use Javascript on the backend. People already losing interest on PHP because NodeJS has so much more potential. And SQL databases are also becoming less and less populair. I think u can use Javascript based DB's like MongoDB or many other flavours. " I don't think this guy was part of the Coder team. But what are your thoughts on this statement?

2 Answers

Aaron Graham
Aaron Graham
18,033 Points

With NodeJS, Ruby on Rails, and some of the Python frameworks, PHP is certainly less popular than it used to be. To call it obsolete is probably a bit of an overstatement though. It is still ubiquitous and is a very powerful, object oriented language to boot. The architecture of the web seems to be moving away from content delivery through a tightly coupled front-end/backend web-server to a more loosely coupled REST style backend that provides content to any number of different clients. The biggest problem with PHP, at least in my opinion, has been the lack of a framework that easily supports this style of architecture. It looks like that is changing though. I think Laravel might make it easier to build this type of service (really looking forward to taking the new Laravel class!). NodeJS is really cool, but its event based architecture makes it really bad for anything that requires a lot of CPU intensive processing. As for SQL, noSQL databases like Mongo are great for storing data that doesn't easily fit into a schema or for doing things like MapReduce, but the best way to model relationships between different sets of data is still probably a relational database like MySQL. I think it boils down to this: It never hurts to know different languages and technologies. Most importantly, know where those technologies excel, and where they fail. Use the right tool for the job.

I can agree with this. PHP isn't the "all-around works for everything language" anymore. Python or Ruby might be more suited for an application than PHP is. I am not familiar with how intensive php is on the CPU though.

Yeah I mean I can see that it's not perfect for everything. I wish they would add more support for php and SQL in Coder. I could build better things that way.