81–90 of 163 posts
Who in their right mind would choose brainfuck for enterprise solutions, over befunge?
Befunge has real lofty ideals, not just a miser goal of being hard to parse by humans:
> Befunge, with the goal of being as difficult to compile as possible
Wow, would love to adopt this on our infra! Just one teensy problem - legal's a bit worried about the name. Would you consider renaming BF? Maybe Brainfriend?
Earlier quoted context omitted.
You can't discount the need to keep your hiring pipeline full to replace the people whose RSUs have cliffed. Befunge, like Rust, is impossible to hire for, so nobody uses it, which means nobody has experience, which means it's impossible to hire for, so it's a bad idea to use it. BrainFuck has been around for decades and its problems can be avoided by just hiring sufficiently-talented developers.
Being the only true 2-dimensional language, Befunge only needs the square root of the lines of code to build an equivalent program to puny 1-dimensional programs like Brainfuck or C++. Stop trying to hire 10X engineers. Befunge applications are built by true X² engineers.
Best sales slogan of the year.
++++++++++[>+++++++>++++++++++>+++>+ ++.>+.+++++++..+++. >-.------------. +++++. ----.++.>+++++++. -. --. -----.>+++++.---------.>++++++++.---------.>+++++.-------. --. --.+++.>++++.-------. ----.>+.>+++. -. >---.++++.-------. +++++++. +.>+++. >----. >++++. >+++++++. -. >-----. >+++. >----. >+++++. .<.
Somebody didn’t read the style guide, especially 1.1.2. https://github.com/bf-enterprise-solutions/bf.style
++++++++++[>+++++++>++++++++++>+++>+ ++.>+.+++++++..+++. >-.------------. +++++. ----.++.>+++++++. -. --. -----.>+++++.---------.>++++++++.---------.>+++++.-------. --. --.+++.>++++.-------. ----.>+.>+++. -. >---.++++.-------. +++++++. +.>+++. >----. >++++. >+++++++. -. >-----. >+++. >----. >+++++. .<.
Somebody didn’t read the style guide, especially 1.1.2. https://github.com/bf-enterprise-solutions/bf.style
++++++++++[>+++++++>++++++++++>+++>+ ++.>+.+++++++..+++. >-.------------. +++++. ----.++.>+++++++. -. --. -----.>+++++.---------.>++++++++.---------.>+++++.-------. --. --.+++.>++++.-------. ----.>+.>+++. -. >---.++++.-------. +++++++. +.>+++. >----. >++++. >+++++++. -. >-----. >+++. >----. >+++++. .<.
Somebody didn’t read the style guide, especially 1.1.2. https://github.com/bf-enterprise-solutions/bf.style
Earlier quoted context omitted.
Won't that be confused with B[1]? [1] https://en.wikipedia.org/wiki/B_(programming_language)
Sure, but the number of B code currently in circulation should be miniscule enough to reuse that extension. (And the confusion between Brainfuck and Befunge will be much higher anyway.)
Love this. Years ago I hand-wired a CPU that natively executes Brainfuck code: https://youtube.com/watch?v=q8G2fWprwyo Might have to test some of these :)
Earlier quoted context omitted.
Sure, but the number of B code currently in circulation should be miniscule enough to reuse that extension. (And the confusion between Brainfuck and Befunge will be much higher anyway.)
Also, confusion seems to be something of a design goal for brainfuck?