Don't laugh: this is the next big step in cloud computing infrastructure. Imagine Linux compiled to the BrainFuck ISA running a Docker container running a BrainFuck web application. Of course, we will clearly need a solid BrainFuck-to-JS transpiler to make things web scale.
". A large amount of research is focusing on what kind of wimpy machines are best fit for important workloads. In this paper, we present a rather extreme example of a wimpy processor, using the BrainFuck [22] esoteric programming language as its ISA."
Seems legitimate to me. Seriously, why not explore the extremes? Thats where we often learn the most.
I suspect many here think this is a joke, but although does have it's funny side this definitely warrants the research IMHO
Why is the author consistently mixing up "
"instructions per cycle" with "instructions per second"?
Surely, phrases such as "We observed the following Instructions per Second (IPC)" and "assuming a perfect 1 instruction per second on the general purpose processor" should have activated some neurons in some brain, even assuming it got distorted by doing this research?
That's my guess. It's one of the few projects that I thought actually would damage my brain. I avoided it. Unlambda language is another one like that. Although I have considered trying to implement that one, esp in hardware.
This greatly annoyed me too. It's IPC not IPS after all. I'm surprised this didn't get caught by literally anyone who reviewed this paper before hitting submit.
Ah. MIT, never change. Mind, this kind of stuff could come out of other institutions as well. They shouldn't change either.
Anyways, can we have a version of TIS-100 where you write brainfuck with added message sending primitives instead of the TIS-100 asm? Of course, each BF interpreter would be working with only, say, 2 or 3 cells of RAM.
I want to see either that, or a TIS-100 asm compiler for GreenArray chips. Or both.
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!
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.
LOL. I work in the same building as Urban. I'll be sure to point it out to him on Monday, I'm sure he'll be amused (or annoyed at my position in the queue of people that have already informed him of this). :D
Love it.
Could it get better than that?
http://copy.sh/brainfuck/
We're ready for the revolution!
Seems legitimate to me. Seriously, why not explore the extremes? Thats where we often learn the most.
I suspect many here think this is a joke, but although does have it's funny side this definitely warrants the research IMHO
Surely, phrases such as "We observed the following Instructions per Second (IPC)" and "assuming a perfect 1 instruction per second on the general purpose processor" should have activated some neurons in some brain, even assuming it got distorted by doing this research?
Anyways, can we have a version of TIS-100 where you write brainfuck with added message sending primitives instead of the TIS-100 asm? Of course, each BF interpreter would be working with only, say, 2 or 3 cells of RAM.
I want to see either that, or a TIS-100 asm compiler for GreenArray chips. Or both.
Moore and your GreenArray chips: be afraid! Something even more incomprehensible is coming after your market share!
http://www.hugi.scene.org/compo/compoold.htm#compo6