3 ms·

I find the whole concept of the case to be off. The author is concerned that applications can’t take advantage of the increasing parallelism of computers becaus

I find the whole concept of the case to be off. The author is concerned that applications can’t take advantage of the increasing parallelism of computers because of the difficulty in writing fine grained parallel tasks, but misses that 1) the paucity of programs that end up CPU bound and 2) Http requests already provide an excellent threading container within which imperative code runs, meaning that the system takes advantage of parallel computing even if the program author doesn’t (so long as they don’t explicitly write themselves into a problem) Edit: others on SO already pointed this out. Also, IMO imperative programming generally maps better to the way business requirements are- First do this, then that, unless you see Y then do that. It’s harder to walk a BA or non technical manager through functional code and stand a chance of them tracking what’s going on.

mrkeen 6y ago
> Http requests already provide an excellent threading container Yes, modelling code around receiving requests and returning responses was a good idea. > It’s harder to walk a BA or non technical manager through functional code and stand a chance of them tracking what’s going on. Jane Street adopted OCaml as its main programming language early on because the language's functional programming style and clear expressiveness made it possible for code reviews to be performed by traders who were not programmers, to verify that high-performance code would do what it was intended to do.
nojito 6y ago
>It’s harder to walk a BA or non technical manager through functional code and stand a chance of them tracking what’s going on. Not really. Check out fsharp code and you use domain words to actually model the business case. This is really old code, but it communicates Fsharp's effectiveness quite well. https://github.com/swlaschin/NDC_London_2013/blob/master/ddd.fsx https://github.com/swlaschin/NDC_London_2013/blob/master/ddd...

mrkeen 6y ago

> Http requests already provide an excellent threading container Yes, modelling code around receiving requests and returning responses was a good idea. > It’s harder to walk a BA or non technical manager through functional code and stand a chance of them tracking what’s going on. Jane Street adopted OCaml as its main programming language early on because the language's functional programming style and clear expressiveness made it possible for code reviews to be performed by traders who were not programmers, to verify that high-performance code would do what it was intended to do.

nojito 6y ago

>It’s harder to walk a BA or non technical manager through functional code and stand a chance of them tracking what’s going on. Not really. Check out fsharp code and you use domain words to actually model the business case. This is really old code, but it communicates Fsharp's effectiveness quite well. https://github.com/swlaschin/NDC_London_2013/blob/master/ddd.fsx https://github.com/swlaschin/NDC_London_2013/blob/master/ddd...