Keean Schupke

Using HTML5, JavaScipt and IndexedDB you can already write software that runs across mobile, pad, laptop, desktop, and big-TVs. It works pretty well, except for annoying corner cases, like iOS...

Well you have to write your own "drivers" for each platform. On Android you have to write in Java to call all the native APIs, but you can call Java...

At the moment I am favouring error handling by exceptions using algebraic effects. For me the argument is about keeping code clean to read.

@shelby3 I think.we should think in terms of transactions with concurrent software. Transactions either complete successfully or roll-back (with an exception) Exceptions can be implemented as an additional return value...

@sighoya My point is that the language syntax is independent of the implementation. Using the Error monad the source language syntax looks like 'throw/catch' but we translate this into normal...

@sighoya you mean it incurs costs on the success path (checking for the error condition), whereas exceptions implemented by stack-unwinding do not? This is true, but due to branch prediction...

@shelby3 > Have you not read my recent post that argues that speculative pipelines are going away and besides they are not cost-free. They waste CPU power. Respectfully, I disagree....

@shelby3 > We can. That is one of the main points of the ACM article that I linked to. Have you read it? Yes, and I disagree with it. Only...

@shelby3 How so? exceptions have a huge cost on failure, it can take 100s of clock cycles to unwind the stack, just jumping to an exception vector in hardware takes...

> which is the only possible future of general purpose computing This is not true. Only a small subset of algorithms are parallelisable, others cannot be because they require the...