The link is 404. And I had to say this in a sentence because “404.” on a line by itself was interpreted as a Markdown list, and rendered as “1.”. That took me a moment. :)
The architecture they describe is interesting - an explicit representation of the control flow for each response, as a DAG. I imagine most small-scale sites won’t care, but it has potential for the rarer companies that have really tight latency requirements.
The link is 404. And I had to say this in a sentence because “404.” on a line by itself was interpreted as a Markdown list, and rendered as “1.”. That took me a moment. :)
Cute naming scheme though.
Link is fixed.
Thanks :)
The architecture they describe is interesting - an explicit representation of the control flow for each response, as a DAG. I imagine most small-scale sites won’t care, but it has potential for the rarer companies that have really tight latency requirements.
Wonder if this mean’s there’ll be a Haskell SDK released at some point.
What extra benefits would an SDK provide?
I should have clarified: a Helium Haskell SDK.