All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Julia language
Date: Sat, 18 Nov 2017 11:19:13 -0800	[thread overview]
Message-ID: <20171118191913.GJ3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <31ffe8fa-8787-7554-ce37-285cb0961a26@gmail.com>

On Fri, Nov 17, 2017 at 12:43:19AM +0900, Akira Yokosawa wrote:
> Hi Paul,
> 
> Have you heard of "Julia" language?
> 
> JFYI,
> As can be seen in its official page at https://julialang.org/ and a Wikipedia
> article at https://en.wikipedia.org/wiki/Julia_(programming_language),
> it looks like one of promising answers to perfbook's Section 2.2 "Parallel
> Programming Goals".
> 
> As long as high-performance number crunching is concerned, it claims to have
> comparable performance to C, with a programming productivity much better
> than C + MPI.
> 
> Note: I'm not a user of the language at the moment. I just heard of it at
> a twitter hashtag #julialang.
> 
> I'd like you to check it up and (hopefully) update the above mentioned
> section in perfbook.

I had heard of it, but I had not heard of it being seriously proposed
as the answer to Section 2.2.  I have added it to todo.txt with your
Reported-by.

Have you or has someone you know used this for a large parallel-programming
project?  (Just looking for some real-world confirmation.)

							Thanx, Paul


  reply	other threads:[~2017-11-18 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 15:43 Julia language Akira Yokosawa
2017-11-18 19:19 ` Paul E. McKenney [this message]
2017-11-19  0:30   ` Akira Yokosawa
2017-11-20 17:43     ` Paul E. McKenney
2017-11-20 22:39       ` Akira Yokosawa
2017-11-27 18:05         ` Paul E. McKenney
2017-11-28  2:07           ` Yubin Ruan

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=20171118191913.GJ3624@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akiyks@gmail.com \
    --cc=perfbook@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.