Live data from Hacker News

Scalable, Resilient Brainfuck

zserge.com

21–30 of 47 posts

Re: Scalable, Resilient Brainfuck

#21
post #13

This 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.

I came onto a team to support such an overengineered project. On the plus side it keeps me busy, and teaches me new skills. On the negative side my job is to keep the plates spinning on a rube goldberg machine.

Re: Scalable, Resilient Brainfuck

#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 actually importing a file), etc.

So our original runtime was actually Brainf#ck. So, at once point, if you had guessed that Google supported it, you could have written your (simple) webapp in Brainf#ck and Google would have scaled it up to hundreds of machines if needed ;-)

Re: Scalable, Resilient Brainfuck

#30
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?

How do you get anything done throughout your day, if you took that joke so seriously?
Post reply on HN