News for hackers. Stuff that matters.
Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by bsdetector on Saturday May 02, 2015 @11:59AM (#9477493)
The author has a "lack of equal experience in the three evaluated languages", especially C, but is comparing them for development time and SLOC based on a sample size of one developer and one very small program.

He rewrites a distributed program as a threaded one, because Rust and Go didn't have a distributed computing library, but says Go and Rust have "similar performance" in HPC.

He says he was surprised at the C performance, but there's no investigation of a cause. Maybe just because C is slow...

I don't mean to be overly critical, but these results in the paper mean absolutely nothing. It's a waste of time.

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by pnathan on Saturday May 02, 2015 @12:14PM (#9477543)
pretty sure all programs were multithreaded.

I do agree that the advisor should have pushed back lots harder on the methods; it's a weak paper, even as an experience report.

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by hurin on Saturday May 02, 2015 @01:33PM (#9477812)
> I do agree that the advisor should have pushed back lots harder on the methods; it's a weak paper, even as an experience report.

I agree - this seems to be mostly the advisors fault, by the looks of it it's not that the student didn't put a lot of work into it but methodological problems are what advisors are supposed to be there to address; I saw a lot of this back in college, at least with technical papers it's easy to tell what's wrong, with the humanities it's just a complete disaster.

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by istvan__ on Saturday May 02, 2015 @01:57PM (#9477904)
I agree with your assessment only thing I did not understand is the Erlang integration with other languages. I am not sure if he is saying that NIFs are bad or he is saying there are is not support for other languages. I think non of these are true...

http://www.erlang.org/doc/tutorial/introduction.html http://www.erlang.org/doc/tutorial/nif.html#id64792

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by panic on Saturday May 02, 2015 @04:03PM (#9478362)
I agree that the paper isn't very convincing. One conclusion you might draw is that learning to write performant code in C is harder than learning to write performant code in Rust. That could just be a side-effect of Rust's much stronger standard library, though.
Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by Dewie3 on Saturday May 02, 2015 @02:01PM (#9477919)
It's a bachelor thesis... probably doesn't aspire to be the new authority on HPC. :)
Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by hurin on Saturday May 02, 2015 @02:20PM (#9477983)
Yes, because the point is being able to write (on a resume): successfully presented thesis on "Evaluation of C, Go, and Rust in the HPC environment".

The advisors should have encouraged a smaller and more manageable scope with a more thorough methodology where the results would actually be worth something.

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by acadien on Sunday May 03, 2015 @01:45AM (#9480147)
The goal is for the student to get some experience with performing their own research wherever that may lead them. This is actually a pretty impressive piece of independent work for an undergrad.
Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by hurin on Sunday May 03, 2015 @05:46AM (#9480660)
> The goal is for the student to get some experience with performing their own research wherever that may lead them.

You mean it has nothing to do with learning correct methodology or actually doing real research?

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by seanmcdirmid on Sunday May 03, 2015 @06:55AM (#9480831)
"Correct methodology" and "real research" are very subjective things. We often judge too harshly, and as long as the paper is not misleading, you can judge it's merits directly without resorting to non-science.
Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by hurin on Sunday May 03, 2015 @07:21AM (#9480891)
> "Correct methodology" and "real research" are very subjective things.

That's exactly the attitude emblematic of the portion of academics producing worthless output.

Here is a recent reference: http://www.nature.com/news/psychology-journal-bans-p-values-...

Not a methodological problem?

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by seanmcdirmid on Sunday May 03, 2015 @07:42AM (#9480937)
Peer review should sort out the bad science from the good. The above link is just laziness: they have correlated P values with low quality research, and have decided to use it as a crap filter in leu of better, but more expensive, peer review.

The article submitted was not peer reviewed, and could very well be bad science, but I think accusations of non-science are not very productive and do not provide feedback in how to do better.

Re:Evaluation of C, Go, and Rust in the HPC environment [pdf] by hurin on Sunday May 03, 2015 @08:03AM (#9480968)
> The above link is just laziness: they have correlated P values with low quality research,

My point was rather that there was so much low quality research they decided to try to filter it by banning a statistical tool. Are you saying the reasons for so much low quality research had nothing to do with methodological problems? Maybe it's not low-quality, since you know it's "subjective"...

> The article submitted was not peer reviewed, and could very well be bad science, but I think accusations of non-science are not very productive and do not provide feedback in how to do better.

You are addressing a point I never made. What I said was(quote): The advisors should have encouraged a smaller and more manageable scope with a more thorough methodology

Because an important part of undergraduate education is in fact learning to be able to tell what good research is. The advisor's aren't really benefiting them by not pointing out methodological problems and letting them do research ">>>>> wherever that may lead them" - because that only encourages methodologically sloppy work in the future.