Hacker News Reader

There's a difference of category between your and parents example. Editors and IDEs will not make your code crash when it is deployed no matter how flaky or not they are. Databases on the other hand can.

I wouldn't imagine it being controversial to prefer well engineered code over less so for bits you will need to depend on.

View on HN

Yes but databases are not your normal application, library or tool. They require a fair degree of expert knowledge and I agree even more are a critical component.

I would much rather choose a battle tested database that has the features I want, performs well to my testing and profiling than "familiar" looking code. Because good looking code is really more often or not familiar looking code.

So unless the OP is an expert I believe basing the most critical aspect of your application just because the code isn't to your liking is sort of asinine.

Have you looked at MySQL's source code? Pretty tangled, and that's an excellent database.

Also vim is not flaky. The insides may be a nightmare, but it's very solid.

Reply on news.ycombinator.com