aartaka

Well, who said that scripting language cannot be compiled? And yeah, Clang-REPL is another way to make it REPL-friendly.

> I was expecting a post about how far the different implementations have diverged from the standard. Perhaps some of them have begun to create their own language.

That would be a boring one, actually. Most implementations stick to the standard (and for good), only adding features clearly missing from the standard. And these features are also quite community-approved, with something like Trivial Gray Streams, Bordeaux Threads and other portability libraries being de-facto standard libraries working on almost all implementations.

One exception to this would be Allegro CL. It has such a huge ecosystem that one can easily lock themselves in there and write the kind of Allegro Lisp dialect. But that's rather and exception than the rule.

Unfortunately, ChatGPT is too weak of an AI to work with Brainfuck code due to Brainfuck having too high-level of a semantics for an AI to grasp it. So yes, we have dedicated human coders in our company, and they are happy not to use hip AI do replace themselves!

Thanks, we're glad you liked it! We don't hate anyone, though—we're commited to making good software with effective tools!

You can always call it Brainf* or BF—we do that when communicating with outside clients. Works alright, especially after they see how much power it adds to our programs.

Glad to see you find it! We're commited to making Brainfuck community better, and our documentation and code style is part of this effort!

Yes, there's always space for optimization in Brainfuck programs. We haven't used some of the optimization opportunities for readability, as you've said. But we might have missed some optimization spots too, so feel free to open an issue or pull request if you know how to fix that!

Also note that 430 lines is the code compliant with our bd.style: heavily commented, unambiguous, modifyable. You can always minify the code and it'll be some 1K commands, which is pretty small for a text editor.

We're committed to the values of Open Source, so you can use and repurpose our code as long as you are acting with accordance to the license

Luckily, you don't need Unicode, and we've endorsed the no-Unicode move in Brainfuck Enterprise Solutions. If one needs non-ASCII text, there always are ASCII encodings, like ArmASCII and romaji.

There is also https://brainfuck.org/epistle.html, so we're pretty safe about the set of features that Brainfuck needs. At Brainfuck Enterprise Solutions, we're relying on a safe set of features any modern Brainfuck implementation provides, so we're safe and happy.

Indeed, Brainfuck is extremely powerful and portable! We're going to release our (Brainfuck Enterprise Solutions) "Why Brainfuck" manifesto soon, so stay tuned!

Yes, it's neither a UNIX ed, nor a POSIX one, but that's a declared thing: it's an opinionated editor that purposefully diverges from ed.

Living a plaintext-only life is tempting. But the further one goes with plaintext, the more they re-invent Markdown or HTML. Let's just give up and live hypertext life instead.

Oh, right, it's on the blog now: https://www.aartaka.me/blog/write-hypertext-not-plaintext

Living a plaintext-only life is tempting. But the further one goes with plaintext, the more they re-invent Markdown or HTML. Let's just give up and live hypertext life instead.