News for hackers. Stuff that matters.

A comment on Concurrent JavaScript: It can work. Parent comment

Re:Concurrent JavaScript: It can work by jensvdh on Wednesday August 30, 2017 @04:25PM (#15135682)
What's the point? Why not write your server directly in say Python or Java then?

I thought WASM is meant to get around the restriction that the browser only understands JS right now.

[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by pitaj on Wednesday August 30, 2017 @06:08PM (#15136514)
> why not use X

Because X doesn't run in a browser

[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by kornakiewicz on Wednesday August 30, 2017 @06:21PM (#15136605)
Do you need to run your server in a browser?
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by geldan on Wednesday August 30, 2017 @07:07PM (#15136877)
No, but it's very nice to be able to share code for things like view rendering or form validation between the server and client without jumping through hoops.
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by shurcooL on Wednesday August 30, 2017 @10:32PM (#15137764)
So you use language X. Compile it and run it natively on server, compile it to wasm and run that in the browser.
[ Parent | on HN ]
Re:Concurrent JavaScript: It can work by chr1 on Thursday August 31, 2017 @07:11AM (#15139494)
Why should i use language X that i don't like, instead of nice dynamic language, without compilation step that i like, and which only misses this tiny feature?
[ Parent | on HN ]