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

Seriously, this is a rather typical old-economy response to a well understood concept at this point: Simple works.

Coming from the inside of the enterprise web publishing world I'd suggest it's not 37signals that is missing something.

Of course the author (of the review) did found a chain of restaurants...




"Simple works". Which is why they created everything with Forth on Rails. Oh wait... it's Tcl on Rails. No... Ruby? Ruby is not simple. It's actually a nice mix of elegance, simplicity and, where called for, fancy ways of handling complexity.

And they host everything on DOS. Because it's simple! No?

I think this stuff goes both ways... you can't just wave "simple!" around.

If you really wanted simple, you'd use a pencil and paper.


Uhm… How about trying to see the difference the product and implementation details? Cars are simple you know: turn a key, step on the gas and you ar going. Does anyone claim that those dozens of CPU hidden under bonnet and AT gearbox is simple?


Some stuff is simple, some isn't. Trying to make it simpler is a good goal in many cases, except for when it isn't.

What I disagree with is "business by platitude".


Did you read his conclusion? The book is rescued by a thread of ideas that focus on one theme - that less ambitious, more straightforward products can often beat 'better' products. And, this time, they give good examples - of the recent uptake of simple fixed-gear bikes, and the popularity of the flip phone




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

Search: