| > Feels like you've just read grugbrain.dev and decided to shoot your golden tips at everybody without actually trying to understand the situation. This feels like you've taken this personally or are projecting. I'm not sure if you posted this to Hacker News as some sort of marketing exercise, but this is _Hacker_ News, there should be an expectation that some people are going to take a critical view at your post. > Because those prices change 24/7/365, million times a day, and so refreshing happens pretty much all the time in the background, eating CPU time. What's more, calculating prices is much more complicated than a hashmap lookup - hotels can have dynamic number of discounts, taxes etc., and they can't all be precomputed (too many combinations). I get that you have to recalculate things, I'm still not entirely sure how you ended up with 10% of your overhead being in malloc while doing it. That's pretty unusual, and almost everywhere, would be considered a code smell. > a little trust in others won't hurt. That's not why I'm here and I'm very sure that's not why you've posted this here either. |