News for hackers. Stuff that matters.
Re:GopherJS by alexchamberlain on Monday March 30, 2015 @02:20AM (#9287935)
Whilst I think projects like this are cool, it's a real shame that browser vendors don't make embedding other engines easier.
Re:GopherJS by tracker1 on Monday March 30, 2015 @03:46PM (#9292078)
It's plenty easy to embed another engine into a browser... see: VBScript, Dart, NaCl, etc...

The problem is that in the end, you won't see consensus on a secondary language from multiple browser vendors, in the end something that breaks down into JS/asm.js is probably more practical.

To me, getting webworkers to a better position of usability is a far better goal. As it stands, you have to write your worker completely detached from your main script/code... separate build target, separate calls, different model from node's IPC which reduces reusability. This is mainly in that I feel a bigger issue with JS performance for critical tasks in the browser will be alleviated by better channels with web-workers.