HN user
Great comment. I just read a book called Ten Kings. It's loosely based on a small portion of the Vedas that talks about the 'tribes' in the indus valley region and the constant wars that took place for control of the fertile lands there. I guess the region wasn't as peaceful as it's pointed out to be.
Slightly off topic, but is there a mobile friendly version of this site?
Was curious about this and checked with Netcraft. Looks like HN is using CloudFlare's CDN.
Not sure if the origin server is on FreeBSD.
Not open source, but you might want to check out PrinceXML. It is really good.
Yet another good book is Algorithm Design by Jon Kleinberg, Éva Tardos. What I like most about this book is that it contains tons of interesting, real-world examples and exercises that make the theory so much more fun.
The biggest gripe I have with single-letter variable names is that they invariably require mental translation to their full names before anyone can understand how they're being used. Even for those who wrote the code in question.
It's on Limelight's CDN
www2.nissan.co.jp is an alias for nissan.vo.llnwd.net.
I believe that'd be a non-issue since the "i" is always preceded by an "Esc".
All the best, Colin.
Uh? I just tried it and it works without blowing up.
Prelude> 2 == 2.0 True
Ditto on both counts!
Started out on an XT (I think) writing Basic. It's been 20 fascinating years.
Great project. I really hope Elixir takes off. I can try to convince my bosses that the transition from Ruby to Erlang isn't going to be syntactically hard :)
Fully agree. The rules have to be versioned and validated. In fact in our use case we have to go a step further and have another dimension to support validation - the notion of the phase/stage the rules are in: work-in-progress rules vs activated rules.
We are trying to build a system that describes pricing rules for a set of products. After thinking about it for a while we have decided to use a table driven approach for capturing business rules describing the pricng structure. The columns capture the various attributes of the products/order form such as the territory it's sold in, the currency of the order, etc. The results/actions for each rule capture the prices. We choose to implement it this way for precisely the reason mentioned in the article - we want our end users to maintain the rules.
I'm curious to know if this is because Haskell doesnt support nulls or is there something else that makes it better at catching type errors.
Some of the vendor facing systems I worked on definitely were not on AWS by the time I left in 2008. And there wasn't any plan on the map to migrate them at the time. But that was 3 years ago.
> The golden path involves preemptive multitasking with little-to-no shared state. Erlang (and probably some other languages) seems to have taken this approach.