well what would someone use web workers for ? why did they make it into the standard ?
I think that a multithreaded model is needed for some html5 applications if we care about performance and utilizing multiple cores. I agree that for many applications especially where the business logic is on the backend, you can work with concurrency but as more logic gets added to the frontend the need for parallelism becomes more apparent. In my opinion it's hard to think for a valid usecase for web workers/multithreading in javascript because we got used to the single threaded model but if more libraries/frameworks adopted them and more abstractions were based on them their benefit will become clear. بتاريخ الأحد، 13 نوفمبر، 2016 4:06:19 ص UTC+2، كتب Robin Heggelund Hansen: > > What would you use it for? > > søndag 13. november 2016 00.53.05 UTC+1 skrev أحمد حبنكة følgende: >> >> according to this >> <http://stackoverflow.com/questions/29181960/is-there-parallelism-in-elm> >> question, >> Elm doesn't support parallelism yet. >> >> >> I know that right now the idiomatic way in JS (and in result Elm) is to >> do concurrency instead of parallelism but I think in the future web workers >> might become as idiomatic as AJAX or Promises. >> >> Given that JS does now support it via web workers, I was wondering what >> are the plans for adding Parallelism to Elm ? >> >> >> >> -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
