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

I've written a bunch of PHP, Perl, SQL stuff, but always down-shift into C or C++ (mostly C though) when performance or command-line tools need to be efficient. I wrote a multi-threadded crawler in C because using perl or shell scripts wrapped with xargs is not very efficient. I love working with C mainly because I grew up writing C code and I find it very convenient. I have a favorite debugger. I love using linked lists. I think that constructing a complex in-memory data structure to make a program run efficiently is an art form. Also, I believe that using BerkeleyDB is also a much better option for a database from a programming aspect. BerkeleyDB (like C) has been around for ever, it's fast, it has low-overhead, and it does things just as good as any other key/value database (if not better because it's so mature). Using older, more proven technologies is slowly becoming my overall programming philosophy. I'm not a new graduate, but I still feel that these methodologies are much better in many circumstances than the newer tools that are all the rage when performance and reliability are an issue. Sometimes, I even re-code regexps using pcre in C to make them fast if they're a bottleneck so I can squeeze some more performance out of my code. When I'm prototyping something, I still revert back to perl or php though - they're great for quick and dirty tasks still.



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

Search: