andrewducker: (Default)
[personal profile] andrewducker
[livejournal.com profile] robhu has a good point over here.

At the moment we write Javascript in web pages, which is then compiled down by the various JIT methods that Firefox/IE/Webkit use to make it super fast.

Seeing as what's run clearly isn't the actual JS itself, but bytecode, why not have a standardised bytecode that all browsers would support, which would then mean you could write your code in any language you liked, providing there was a compiler to convert it to the standardised bytecode?

At the moment Google uses GWT to convert Java into Javascript that then gets converted into the running code, (And MS used to have something similar) wouldn't it be handy if the intermediate step wasn't necessary?

Date: 2010-11-11 02:52 pm (UTC)
From: [identity profile] momentsmusicaux.livejournal.com
That would mean Apache etc having to know how to serve JS files...

Date: 2010-11-11 03:08 pm (UTC)
From: [identity profile] momentsmusicaux.livejournal.com
Yes, but who would do the compiling?

I'm not doing it, the browser isn't doing it, so it's got to be the server....

Date: 2010-11-11 03:26 pm (UTC)
From: [identity profile] momentsmusicaux.livejournal.com
Yeah, you've lost me. How is that different to what happens now? What's the benefit if it is -- the browser is still doing the work.

Date: 2010-11-11 03:52 pm (UTC)
From: [identity profile] momentsmusicaux.livejournal.com
Right, so we are on the same page. So my question was -- who's going to make the bytecode?

Date: 2010-11-12 01:49 am (UTC)
From: [identity profile] figg.livejournal.com
So,

people who write js can just write js

and people who write in something that compiles to js can compile to a different format instead

October 2025

S M T W T F S
    1 2 3 4
5 6 7 8 9 10 11
12 13 14 15161718
19202122232425
262728293031 

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 16th, 2025 01:24 am
Powered by Dreamwidth Studios