Why does Google prepend while(1); to their JSON responses?

Re:Why does Google prepend while(1); to their JSON responses? by amelius on Saturday May 06, 2017 @03:36PM (#14281856)

I can also see it happen that browsers will one day shut down plain JavaScript, only allowing WASM. Certainly if the security burden becomes too big.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by oblio on Saturday May 06, 2017 @04:23PM (#14282054)

That's awfully optimistic of you.

First of all browsers are committed to backwards compatibility.

Secondly, there's huge amounts of Javascript written right now, nobody's going to throw away billions of dollars worth of investments. People complain about Cobol written in the 60's, when the programmers counted in the thousands. Javacript today is written by millions of programmers.

And thirdly, Javascript evolves, as do browsers.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by sargun on Saturday May 06, 2017 @05:35PM (#14282389)

I can certainly see a world where WASM and JS execution pipelines in browsers converge -- where the form used for executing WASM and JS is the same.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by int_19h on Sunday May 07, 2017 @12:49AM (#14283917)

Once WASM becomes established, I would expect JS to become "yet another runtime" on it.

[ Parent | on HN ]