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

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

On the other hand, if you thought modern browsers are bloated, just wait for everyone to compile their runtimes on top of WASM.

It's not very hard to imagine, especially in an enteprise environment, running a browser 15-20 years from now and that browser loading the equivalent of the JVM, .NET CLR, Ruby VM, etc., on top of WASM :)

[ Parent | on HN ]

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

15-20 years from now, it's likely that "browser" will just be the operating system.

[ Parent | on HN ]

Re:Why does Google prepend while(1); to their JSON responses? by missblit on Sunday May 07, 2017 @11:28AM (#14285898)

This actually reminds me of "es-operating-system"; an experimental operating system copyrighted by Nintendo (yes, Nintendo!), where "every system API is defined in Web IDL".

AFAIK it never went anywhere, but maybe building an entirely new OS/Browser based around WebIDL seemed less insane 10 years ago.

https://code.google.com/archive/p/es-operating-system/

[ Parent | on HN ]

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

We'll all have gigabit connections by then. So even though it'll be 100 mb of bloat, it will still load the same as today ;)

[ Parent | on HN ]

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

Yes but they'll be pwned by the FCC (and friends). Don't count on it.

[ Parent | on HN ]