Earlier quoted context omitted.
Drumrol... Wait for the release of Brain#
Wouldn't it be BrainFuck# ? or BF# ?
Yes, but I was going for a sharp brain :)
Scalable, Resilient Brainfuck
41–47 of 47 posts
Re: Scalable, Resilient Brainfuck
#42Google App Engine originally used a custom containment strategy. Back in the day, I was on the team that added Python 2.7 support to App Engine and we were experimenting with a different containment approach. But Python is a complex language to support - you need to support WSGI, to support dynamic loading (for C extensions), a reasonably performant file system (Python calls `stat` about a billion times before actual…
[deleted]
Re: Scalable, Resilient Brainfuck
#43This is gold. It reflects too many real engineering projects so well. Sometimes I'm the guy to point this out, but too often I catch myself arguing for adding unnecessary complexity (unfortunately usually in hindsight). There should always be one engineer playing devil's advocate and at least try arguing why a new system/service isn't necessary.
The 10th man rule
Re: Scalable, Resilient Brainfuck
#44So he is running clusters of brainf#ck machines in the cloud? I think this can be legitimately called a Clusterf#ck.
Ideally Clusterf#ck should use f#ckf#ck.
>B**b!!!!!!!!!!!! A R S E feck kn*b c* ksh ag t*ts butt
>The above example will echo the first twelve characters from a file/stdin.
https://web.archive.org/web/20050207213934/http://chilliwill...
Re: Scalable, Resilient Brainfuck
#45Google App Engine originally used a custom containment strategy. Back in the day, I was on the team that added Python 2.7 support to App Engine and we were experimenting with a different containment approach. But Python is a complex language to support - you need to support WSGI, to support dynamic loading (for C extensions), a reasonably performant file system (Python calls `stat` about a billion times before actual…
What?
I was also really confused by this comment until I re-read it later.
At first I thought OP meant “we wrote out container runtime in Brainfuck,” but what I think they meant was “we first deployed Brainfuck support in order to test our new runtime on something simpler than Python.”
Re: Scalable, Resilient Brainfuck
#46Re: Scalable, Resilient Brainfuck
#47Earlier quoted context omitted.
I assume he is writing in https://fsharp.org/
Drumrol... Wait for the release of Brain#
I did write a .NET compiler a few years ago for a procedural variant of Brainf*ck: https://www.parkscomputing.com/applications/pbrain/