From: "Ulf Wiger (TN/EAB)" <ulf.wiger@ericsson.com>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Google trends
Date: Thu, 01 Nov 2007 10:31:11 +0100 [thread overview]
Message-ID: <47299CDF.5090608@ericsson.com> (raw)
In-Reply-To: <1193906249.472990499bcc0@webmail.in-berlin.de>
Oliver Bandel wrote:
> Zitat von Jon Harrop <jon@ffconsultancy.com>:
>
>> The number of people searching for OCaml on Google has sky-rocketed since
>> Microsoft's announcement that they are productizing F#:
>>
>> http://www.google.com/trends?q=f%23%2Cocaml&ctab=0&geo=all&date=all&sort=0
>
>
> Well, I can't see any sky-rocketing there.
> Also I found no absolute numbers of requests on that page.
Google Trends only shows relative trends, but you can
try find different references, in order to find your
bearings:
http://www.google.com/trends?q=f%23%2Cocaml%2Cerlang&ctab=0&geo=all&date=all&sort=0
http://www.google.com/trends?q=f%23%2Cocaml%2Chaskell&ctab=0&geo=all&date=all&sort=0
http://www.google.com/trends?q=f%23%2Cocaml%2CC%23&ctab=0&geo=all&date=all&sort=0
(So, F# has climbed up to about the level of Erlang, which is
also on a rise, but there's some way to go before catching up
with Haskell, and compared to C#, interest is relatively zero).
Of course, you have to think about alternative meanings of
your search terms (e.g. Haskell County, the Erlang-B formula,
the musical chord F#, ...), but I've assumed these to be
insignificant, at least for Haskell and Erlang trends.
But still, working with the tool for a while can help you
build some intuition:
http://www.google.com/trends?q=C%2B%2B%2CJava%2CC%23&ctab=0&geo=all&date=all&sort=0
Playing around with it a while back, I got the distinct
feeling that interest in functional languages is stirring
somewhat, while C++, Java, UML are on a slow but steady
decline (by this measure).
When you start finding blog entries claiming that F# sucks
because someone picked it up and tried some solution that
works really well in C++, python or ruby, then you are
really starting to find a new audience. ;-)
BR,
Ulf W
next prev parent reply other threads:[~2007-11-01 9:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 1:02 Jon Harrop
2007-11-01 2:20 ` [Caml-list] " skaller
2007-11-01 8:37 ` Oliver Bandel
2007-11-01 9:31 ` Ulf Wiger (TN/EAB) [this message]
2007-11-01 10:55 ` Oliver Bandel
2007-11-01 9:46 ` Richard Jones
2007-11-01 12:00 ` skaller
2007-11-01 12:46 ` Richard Jones
2007-11-01 15:45 ` skaller
2007-11-01 16:31 ` Jon Harrop
2007-11-01 18:12 ` Richard Jones
2007-11-01 19:47 ` Peng Zang
2007-11-02 3:11 ` Jon Harrop
2007-11-02 13:48 ` Lars Nilsson
2007-11-02 15:54 ` Oliver Bandel
2007-11-01 13:01 ` Brian Hurt
2007-11-01 16:10 ` skaller
2007-11-01 18:05 ` Richard Jones
2007-11-02 3:01 ` skaller
2007-11-02 15:50 ` Jon Harrop
2007-11-02 16:26 ` Ulf Wiger (TN/EAB)
2007-11-02 16:07 ` Language trends / Caml popularity (Re: [Caml-list] Google trends) Oliver Bandel
2007-11-01 21:00 ` [Caml-list] Google trends Dario Teixeira
2007-11-03 0:02 ` Florian Weimer
2007-11-02 22:45 ` Florian Weimer
2007-11-03 1:32 ` Jon Harrop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47299CDF.5090608@ericsson.com \
--to=ulf.wiger@ericsson.com \
--cc=caml-list@yquem.inria.fr \
--cc=oliver@first.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox