News for hackers. Stuff that matters.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by nickpsecurity on Saturday October 15, 2016 @03:11PM (#12715253)
This is some bullshit. They didnt even port the standard benchmarks to Brainfuck to compare performance against reference implementations. I want to see ZIP, raytracing, web servers, map reduce... actual apps with associated BrainFuck performance. Scratch the whole Future Work section in favor of that given you might accidentally find evidence for using it in production somewhere.

Moore and your GreenArray chips: be afraid! Something even more incomprehensible is coming after your market share!

Re:Design and Implementation of a 256-Core BrainFuck Compute... by TazeTSchnitzel on Saturday October 15, 2016 @04:11PM (#12715478)
I wonder if you're joking, but these sorts of things have been implemented in Brainfuck.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by nickpsecurity on Saturday October 15, 2016 @07:24PM (#12716090)
I wasn't. I'm simply too sane to follow BrainFuck developments unless it's something wild and accidentally useful like a 256-core CPU on HN front page. ;) If they've been implemented, authors should've run some of them on the processor to include benchmarks in the paper. It's standard thing to do in CompSci papers on CPU's, compilers, optimizations, interpreters, anything. They usually include something like that.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by TazeTSchnitzel on Saturday October 15, 2016 @08:05PM (#12716199)
Right, okay. It stood out to me too, because there are compilers and larger applications targeting Brainfuck, so it seems strange to only choose “hello world”-style programs.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by sitkack on Saturday October 15, 2016 @04:00PM (#12715450)
ColorBrainFuck would be in shades of gray.