Skip to content

Comment on Goodbye Tokyo Cabinet, hello PostgreSQL

Comments

That guy has no clue how to use a non-relational DB (he even admits it) and he uses a DB that is wrong for his task and wonders why it's so hard.

The only point he makes is that the APIs for non-relational DBs are much too simple and limited, so you end up building lots of code on top to do the most trivial things.

What we really need is a way to generate indexes or materialized views on these DBs in a standardized way (see CouchDB, for an example).

He has no clue how to use a relational DB either (he even admits it). How and why is this on the homepage?

I have a (bit of a) clue how to use a relational DB. But not from Clojure two years ago, when the only interface was a very thin layer over JDBC.

As for why it's on the homepage, I don't think it belongs here either. The intended audience was rather more narrow than HN.

I wasn't sure I was reading it right, but you said MySQL was too slow to run your personal blog? Is that right?

I ran on MySQL for a few months without issues, but my code was disgusting. My choice was clean code + slow, or ugly code + fast. Today I have clean code + fast, thanks partly to better library support in Clojure, so I'm happier. I'll be the first to admit that I didn't have much of a clue a year and a half ago. I think I have a bit more of one today, but I could be wrong.

Again, not sure why any of this is important enough to talk about on HN. I'm hoping this thread dies before my server bursts into flames.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.