Maven (famous) to Programmer [email protected] • 6 months agoSTOP WRITING Clemmy.worldimagemessage-square154fedilinkarrow-up1824arrow-down160
arrow-up1764arrow-down1imageSTOP WRITING Clemmy.worldMaven (famous) to Programmer [email protected] • 6 months agomessage-square154fedilink
minus-square@[email protected]linkfedilink13•edit-25 months agoFor the programmer? Very no. For saving space if run via interperter? No. For running compiled for conventional CPUs? No. Compared to CISC instruction sets? Absolutely no. BF might be highly efficient if crunched down to a bit-packed representation (3 bits per instruction) and run on an FPGA that understands it.
minus-square@[email protected]linkfedilink6•5 months agoFor demonstrating to CS freshmen that Turing Completeness isn’t that remarkable of a language feature: very highly efficient.
minus-squareMeanEYElinkfedilink6•5 months agoCan be compressed very efficiently. I do dread the thought of writing a driver in brainfuck.
minus-square@[email protected]linkfedilink5•edit-25 months ago Can be compressed very efficiently. Which basically means: “You have to write more code than actually needed”. It’s more a con than a pro in my eyes.
minus-square@[email protected]linkfedilink2•5 months agoHot take: As a VM with only eight instructions, it’s very easy to code and securely sandbox. Maybe BF has utility as a compilation target?
minus-squareMeanEYElinkfedilink5•5 months agoHardware is complex and mysterious enough without added complexity of an esoteric language.
Is brainfuck efficient ?
For the programmer? Very no.
For saving space if run via interperter? No.
For running compiled for conventional CPUs? No.
Compared to CISC instruction sets? Absolutely no.
BF might be highly efficient if crunched down to a bit-packed representation (3 bits per instruction) and run on an FPGA that understands it.
For demonstrating to CS freshmen that Turing Completeness isn’t that remarkable of a language feature: very highly efficient.
Can be compressed very efficiently. I do dread the thought of writing a driver in brainfuck.
Which basically means: “You have to write more code than actually needed”. It’s more a con than a pro in my eyes.
Hot take: As a VM with only eight instructions, it’s very easy to code and securely sandbox. Maybe BF has utility as a compilation target?
Why specifically a driver ?
Hardware is complex and mysterious enough without added complexity of an esoteric language.