News for hackers. Stuff that matters.
Re:Fay -- A proper subset of Haskell that compiles to Javasc... by double051 on Sunday July 22, 2012 @04:01AM (#4276753)
Bytecode for the web always fails. Remember Java applets and Flash? The great thing about javascript is that it can be hand-written and compiled-to.
Re:Fay -- A proper subset of Haskell that compiles to Javasc... by adrianN on Sunday July 22, 2012 @04:42AM (#4276821)
I think the problem with Java applets and Flash was not the bytecode but the slow startup (Java) and the closed source software (Flash) as well as the poor integration with HTML. There is no reason why browsers couldn't implement the same functionality we have now with Javascript using a bytecode based VM.
Re:Fay -- A proper subset of Haskell that compiles to Javasc... by jballanc on Sunday July 22, 2012 @04:46AM (#4276826)
Browsers do implement Javascript using a bytecode based VM - https://github.com/WebKit/webkit/tree/master/Source/JavaScri...

It just isn't standardized, or made available to website authors directly (there would likely need to be significant extra security audits before you could contemplate something like that...).

Re:Fay -- A proper subset of Haskell that compiles to Javasc... by doublec on Sunday July 22, 2012 @06:34AM (#4276999)
Not all browsers do this. At least one compiles directly to native machine code. Chrome's V8 does this according to http://stackoverflow.com/a/8819921
Re:Fay -- A proper subset of Haskell that compiles to Javasc... by tomjen3 on Sunday July 22, 2012 @06:01AM (#4276930)
Since you would need backwards compatability, just make an argument to script elementa that specify the byte code to use instead of the javascript. Then older browsers could continue to function and the rest of us don't have to wait.
Re:Fay -- A proper subset of Haskell that compiles to Javasc... by wingless on Monday July 23, 2012 @08:31AM (#4280588)
Flash was extremely successful, and it was a really great abstraction. What failed was Adobe's implementation, not the idea.

Same with Java. JVM had (and AFAIK still has) a horrible cold startup time which locked the entire browser up, causing the user to curse profanely.