How PHP became the web's King Ruby's bottleneck where _php tutorial

　　 Help the Home (www.Bkjia.com) NewsThis article is not a big battle between Ruby and PHP. It's just that the problem with Ruby in this article is that the lack of library support, the ease of expansion, the ease of crashing, and so on, are all things that the Web programming language needs to improve.

This article is from Killerphp.com's webmaster Stefan Mischook, and was pushed to the famous PHP developer community after release: Phpdeveloper.org, which caused a lot of controversy. Whatever the purpose of Stefan's writing, the problem with Ruby in it: lack of library support, ease of expansion, easy crashes, and so on, is what the Web programming language needs to improve.

In 2006, I created killerphp.com to make it easier for web designers to learn PHP. At the time I thought PHP was the dominant language, and it should be one of the core programming techniques of every web designer:

html

css

Php

JavaScript

Ruby turned out, but it didn't last long, and soon disappeared again.

　　what happened to Ruby and Ruby on Rails?

498) this.style.width=498; "border=" 0 "src=" http://www.bkjia.com/uploads/allimg/131023/09311131A-0.jpg "/>

Once upon a time, Ruby was the best language ever, and all other languages were nothing compared. Now it's time to look back and it's a joke.

Ruby's condition is far less dramatic than it was before. The track car (rails train) has actually slipped from orbit-and now the Ruby Camp has a web framework merb that can replace rails. Strictly speaking, merb and rails are just merging, so it's a bit strongly worded to derail.

　　So what has happened that has constrained Ruby's development?

The reason for limiting Ruby expansion is the same as when I went online 2006-2007 years ago: Ruby's heart is broken.

Yes, Ruby has great grammatical rules.

Yes, it's interesting to write a ruby program.

Yes, it is indeed purely object-oriented, the largest object-oriented!

However, Ruby has many drawbacks: Many of the important libraries and functions seem to be taken for granted by PHP programmers , but only to the point where Ruby programmers envy them, because Ruby doesn't offer them. If you really need to, you can write a patch in C, but it's too painful.

In addition, Ruby has some hidden secrets: crash-o-matic. That's true, Ruby-based web programs often crash . It's not a good combination with a Web server, which makes Ruby always like a mans back.

Evidence here: Ruby has caused Twitter to have performance issues for three consecutive weeks

...... Of course, I've heard that some improvements have been made in this area.

　　What does this have to do with PHP?

498) this.style.width=498; "border=" 0 "src=" http://www.bkjia.com/uploads/allimg/131023/0931112E9-1.jpg "/>

As I said in a it about Ruby a few years ago (Bkjia Editor's note: That article was written in the early days of Ruby's rise, when a common view was that Ruby might replace PHP): PHP just made up for Ruby's shortcomings. Admittedly, some aspects of PHP are really not as beautiful as Ruby. But as vain, if a language is flashy, who would like it?

...... Well, maybe you can try each of these two languages separately! But in any case, don't be blinders by any language.

I still think PHP is, at least so far, the best starting language for learning Web programming. The reasons are as follows:

Powerful features

Easy to learn

Have a big market = you have more work to do

If you say so much, is PHP flawless, and does it all dominate? That's not true. Each language has its advantages and disadvantages-especially at the structural level, where PHP is lacking. My opinion has always been to choose the language to use according to the needs of the project. At first I was a Java programmer, and I've used over 7 programming languages over the years. So I insist that choosing the right language for the project is the most important thing.

Original: What happened to Ruby? And why PHP is KING of the Web.

Author: Stefan Mischook

http://www.bkjia.com/PHPjc/364278.html www.bkjia.com true http://www.bkjia.com/PHPjc/364278.html techarticle Fire Network (liehuo.net) This article is not an article about Ruby and PHP. It's just that the problem with Ruby in this article: lack of library support, easy expansion, easy crashes, etc. ..

