comment on

Thanks chromatic for explaining that graph. (not to me, but to others).

Care to look at

http://www.google.com/trends/explore#q=%22PHP%20tutorial%22

and

http://www.google.com/trends/explore#q=%22Python%20tutorial%22&cmpt=q

These graphs are perfectly consistent with observations on TIOBE - see the respective graphs there (google trends of tutorial searches denote "future interest", while TIOBE denotes "present interest")

If Google trends fall (in absolute numbers - see below), the language popularity will fall. If they remain constant, language popularity will grow. There is a - thin - margin of fall up to which present popularity will remain at least more or less constant. C is a good example for that. If my calculations are correct a factor of 12 in Google trends decrease is the threshold for that situation.

Now to your questions: The normalized Google trends graphs show a decrease by a factor of 25. Which means that we're good if the absolute number of searches on Google has grown 25 times since February 2004. Right?

Well nothing easier than that. Enter Google annual search statistics. 1st try http://www.statisticbrain.com/google-searches/ 2007-2011 we have a growth from 1,200,000,000/day to 4,717,000,000/day. My head says that's a factor of 4, my pocket calculator says ~3.93

Surely you want now to present 2004-2013 Google annual search statistics that will suggest a factor of 25. Be my guest.

Bye
PetaMem All Perl: MT, NLP, NLU

In reply to Re^4: Improve Perl's marketing position by making Perlmonks more discoverable for automated "popularity contests" by PetaMem
in thread Improve Perl's marketing position by making Perlmonks more discoverable for automated "popularity contests" by mithaldu

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks