lørdag 21. november 2015 19.42.07 UTC+1 skrev Michael Haufe (TNO) følgende:
> On Friday, November 20, 2015 at 6:47:24 AM UTC-6, Øyvind Teig wrote:
> >
> > Very interesting. It might just be a Pythagoras tree?
>
> It doesn't look like it to me, but what difference does it make? With an L-System grammar you could describe any number of Plant-Like forms such as:
>
> <
https://en.wikipedia.org/wiki/L-system#Example_7:_Fractal_plant>
I wasn't studying the algorithm, just watching the looks of the trees. Ok, so with the L-System grammar it's always possible to do parallel rewriting. For any form.
>
>
> > When you say Web Workers, do you state that since it's parallelisable then you _know_ that Web Workers would do it.
>
> Yes
>
> > But could I ask; this probably does not imply that some of the other methodologies won't work (and in case, for which reason?)
>
> Concurrency != Parallelization
I did make a point of that in the blog that I was after concurrency not parallelism (as reflected in the heading). I was after a concurrent version of the tree. Not to make it faster or more elegant, just to learn JavScript and how JavaScripters think. I work with concurrency all day at work, it's 20+ years since I did true parallelism on a set of transputers in occam. By the way, the occam PAR did not differentiate between concurrent and parallel, as did the PLACE statement that placed CSP processes on the same machine or different machines (with a dynamic channel router available). We actually used this in some products as well.
>
> ECMAScript is not defined with parallel semantics and does not have any primitives to support it (nor does any draft version).
Ok
>
> Web Workers is specified separately as an API [1]
Thanks
>
> The other listed solutions are an abstraction over existing functionality:
>
> Events/Callback = Concurrency
> task.js = Concurrency
> Web Worker = Parallelization
> node-csp = Concurrency
> RxJS = Concurrency + Parallelization (Using Web Workers)
Great table. I'll take it into my blog note. I was aware of the contents, but it made it clearer. What functionality of JavaScript would you say that these are abstractions are on top of? A run-time system or operating system (making threads (with different kind of process model) available) written in C, I won't consider an abstraction over existing functionality. I'd like to know what you mean.
>
>
> [1] <
https://html.spec.whatwg.org/multipage/workers.html>
If I may ask, provided I do want a concurrent tree, which methodology would you have chosen? I then assume that Web Worker is out.
Thanks for keeping up with me, Michael.