Stuff like this is a breath of fresh air: real hacker vibes. The best memes (like all the best hacker stuff) are high-effort, somewhere between kinda funny and outright satire, technically nontrivial, and delivered deadpan.
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?
Of course this post is written in jest but fck-nat is useful enough that adult organizations adopt it despite the name, as an actual example of “profane but useful software that jumps over the wall of corporate use”. It helps that the specific use case it’s built for is something you usually only run into when you have corporate level spend on AWS
Reminds me of how theres a Buttplug project that has what is considered the fastest bluetooth open source library. Problem is people cannot use it because importing “Buttplug IO” or whatever raises some eyebrows. Theres even been attempts at using it in DoD projects.
Far be it from programmargamers to name things, just to annoy legal and other cruft layers. Now onwards to the new Bloat meeting (its the new scrum), where we produce spam-tickets and increase productivity by sacrificing hours to nil-meetings.
> In this paper we take a step towards understanding how self-replicators arise by studying several computational substrates based on various simple programming languages and machine instruction sets.
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.
I've had much success integrating Brainfuck in a legacy C++ codebase. As the team adopts modern idiomatic C++ patterns and practices, we found Brainfuck via https://github.com/tfc/cpp_template_meta_brainfuck_interpret... to be a natural and seamless fit for C++ template metaprogramming.
Buyer beware – as a a legacy mainframe user of INTERCAL (IBM VM/370), steer cleer of mainframe migration services that promise migration from INTERCAL to BF on commodity cloud on a fixed time scale – they use AI tools but don't do robust testing. Much better to stay on IBM but write new modules in enterprise z/INTERCAL, even if it's not the best developer environment.
Thanks to the "write once run anywhere" philosophy of the language, and the design choices in the OS (e.g. containerization), it is easely porable to any CPU.
One of obvious hindsights here is to use the extension `.bf` instead of `.b`, which was previously suggested by daniel b cristofani, a prolific Brainfuck programmer [1]. `.bf` is also used for Befunge and `.b` removes any such confusion.
Never been much into BF nor esoteric languages in general, but I love this attitude!
Regarding the comments at the top of https://github.com/bf-enterprise-solutions/ed.bf : I believe a modern-day developer comparable to Ken Thompson might be Fabrice Bellard, WDYT? Any other names that pop to mind?
[+] [-] jfktrey|1 year ago|reply
Might have to test some of these :)
[+] [-] benreesman|1 year ago|reply
Top kek.
[+] [-] davedx|1 year ago|reply
[+] [-] samsk|1 year ago|reply
IMHO any solid enteprise should use Ook! or similar substitution - power of Perl, with verbosity of COBOL !
https://esolangs.org/wiki/Ook!
[+] [-] brian-armstrong|1 year ago|reply
[+] [-] debugnik|1 year ago|reply
[+] [-] SOLAR_FIELDS|1 year ago|reply
[+] [-] paulmooreparks|1 year ago|reply
https://parkscomputing.com/page/pbrain
In hindsight, I think it's aptly named.
(EDIT: Gosh, I really need to update the .NET compiler to .NET 8.)
[+] [-] master_crab|1 year ago|reply
Also, do you have a PowerPoint explaining how to setup a Center of Excellence?
[+] [-] tpoacher|1 year ago|reply
you'll find lots of "brainfudge" interpreters on github
[+] [-] giancarlostoro|1 year ago|reply
[+] [-] InDubioProRubio|1 year ago|reply
[+] [-] righthand|1 year ago|reply
[+] [-] avodonosov|1 year ago|reply
[+] [-] Exoristos|1 year ago|reply
[+] [-] Duwensatzaj|1 year ago|reply
[+] [-] rguiscard|1 year ago|reply
[+] [-] wiz21c|1 year ago|reply
[+] [-] Pannoniae|1 year ago|reply
[+] [-] karlzt|1 year ago|reply
[+] [-] bob1029|1 year ago|reply
I think this is probably the most interesting paper involving it:
https://arxiv.org/abs/2406.19108
> In this paper we take a step towards understanding how self-replicators arise by studying several computational substrates based on various simple programming languages and machine instruction sets.
[+] [-] Vegenoid|1 year ago|reply
https://www.preposterousuniverse.com/podcast/2024/08/19/286-...
[+] [-] IncreasePosts|1 year ago|reply
[+] [-] thenewwazoo|1 year ago|reply
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.
[+] [-] ur-whale|1 year ago|reply
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
[+] [-] LorenDB|1 year ago|reply
[+] [-] Duanemclemore|1 year ago|reply
[+] [-] basementcat|1 year ago|reply
[+] [-] int_19h|1 year ago|reply
[+] [-] nxobject|1 year ago|reply
[+] [-] emersonrsantos|1 year ago|reply
[+] [-] trentnix|1 year ago|reply
[+] [-] UnpossibleJim|1 year ago|reply
[+] [-] spacebacon|1 year ago|reply
[+] [-] mikestew|1 year ago|reply
https://github.com/bf-enterprise-solutions/bf.style
[+] [-] cdchn|1 year ago|reply
[+] [-] Retr0id|1 year ago|reply
[+] [-] declan_roberts|1 year ago|reply
[+] [-] arethuza|1 year ago|reply
[+] [-] anta40|1 year ago|reply
An entire OS in 252 lines. I wonder how many CPU architectures supported by this OS
:D
[+] [-] avodonosov|1 year ago|reply
Safe bet for enterprise users.
[+] [-] lifthrasiir|1 year ago|reply
[1] https://brainfuck.org/brainfuck.html
[+] [-] Jerrrrrrry|1 year ago|reply
[+] [-] ur-whale|1 year ago|reply
This shortcoming is clearly a non-starter for any serious enterprise BF implementation.
[+] [-] fermigier|1 year ago|reply
Regarding the comments at the top of https://github.com/bf-enterprise-solutions/ed.bf : I believe a modern-day developer comparable to Ken Thompson might be Fabrice Bellard, WDYT? Any other names that pop to mind?
[+] [-] beretguy|1 year ago|reply
[+] [-] coobird|1 year ago|reply
[1] https://github.com/coobird/brainfuccuccino
[+] [-] xyst|1 year ago|reply
[+] [-] Jerrrrrrry|1 year ago|reply
i was zen
[+] [-] pragma_x|1 year ago|reply