Scalable, Resilient Brainfuck

Post by vangelis » Fri, Apr 09, 2021, 6:08 PM UTC

bquinlan wrote: post #24

Google 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…

Post by TruthWillHurt » Fri, Apr 09, 2021, 6:17 PM UTC

asadlionpk wrote: post #29

junon wrote: post #16

Quick nit - "for may years" -> "for many years". Had to stop reading, basically unreadable.

How do you get anything done thoughout your day, if this typo made you stop reading?

Post by asadlionpk » Fri, Apr 09, 2021, 6:29 PM UTC

TruthWillHurt wrote: post #34

asadlionpk wrote: post #29

Earlier quoted context omitted.

How do you get anything done thoughout your day, if this typo made you stop reading?

I'll just put this here... {

Post by vonwoodson » Fri, Apr 09, 2021, 6:57 PM UTC

shoo wrote: post #14

great news! the business is delighted by the scalability and resilience demonstrated by this proof-of-concept and alignment with cloud-native strategy. the business has decided to use this as the platform to deliver the new "hello $customer_firstname $customer_lastname" product to production. since we'll be executing brainfuck programs containing customer PII, the design may need a few standard technical enhancements…

Post by devoutsalsa » Fri, Apr 09, 2021, 7:33 PM UTC

conjectures wrote: post #28

zibzab wrote: post #6

So he is running clusters of brainf#ck machines in the cloud? I think this can be legitimately called a Clusterf#ck.

If this isn't a thing already it should be.