Hacker News new | comments | show | ask | jobs | submit login

One thing I keep seeing and feeling uncomfortable about, is this throwing layers ontop of layers ontop of layers until you are so far removed from what is actually happening, if one piece breaks down it's impossible to fix, and you have a ton of overhead. I want fast, simple, easy to hack, and something that just goes.

Isn't there a way to do this super slimmed down and light weight?

I've been keeping an eye on the ShipBuilder PAAS project - the minimalist Heroku clone written in Go. It is starting to look quite promising.

Quoting jaytaylor's comment [1] from below:

    > You may be interested in checking out ShipBuilder - it
    > is an open-source Heroku-clone PaaS.
    > ShipBuilder is written in Go, and uses Git, LXC and
    > HAProxy to deliver a complete solution for
    > an application platform-as-a-service.
    > http://shipbuilder.io [2]
    > https://github.com/sendhub/shipbuilder [3]
[1] https://news.ycombinator.com/item?id=6292463

[2] http://shipbuilder.io

[3] https://github.com/sendhub/shipbuilder

Oh, Thanks! I'll check it out!

I just, (seriously, just) read an interview with Ken Thompson arguing that this over-layering is killing him.

Edit: It was in the book Clean Code.

Could you provide page number or chapter name or (preferably) a quote? I searched for "Thompson" in the book and couldn't find anything.

Hey, sorry i had two books in front me and misreported the title. The book is Coders at Work.

I just saw that book on a coworker's desk of mine, now I've GOT to check it out, thanks!

Hey, it was Coders at Work not Clean Code. :) I have both and I guess I mixed the two.

Layers are completely optional (though thoroughly encouraged due to aggressive caching.) If it doesn't fit your model and you're not interested in using the features, that's completely fine.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact