News for hackers. Stuff that matters.

A comment on The melting pot of JavaScript (2017). Parent comment

Re:The melting pot of JavaScript (2017) by pjmlp on Tuesday January 08, 2019 @03:14AM (#18854109)
It is already on its way out, thanks to gRPC and need for performance instead of parsing text all the time.

It is only a matter of browsers getting native support for gRPC.

[ Parent | on HN ]
Re:The melting pot of JavaScript (2017) by sonnyblarney on Tuesday January 08, 2019 @11:44PM (#18862340)
It's available now! Yay! [1]

With gPRC there's still a lot of binding code, and you need to map all of that in Java, but you do get some validation etc. out of it. It does make the 'data transfer' comparison a little less harsh.

[1] https://github.com/grpc/grpc-web

[ Parent | on HN ]
Re:The melting pot of JavaScript (2017) by pjmlp on Wednesday January 09, 2019 @01:58AM (#18862853)
Not really, I meant as browser builtin API, implemented in native code.
[ Parent | on HN ]
Re:The melting pot of JavaScript (2017) by sonnyblarney on Wednesday January 09, 2019 @08:38AM (#18864556)
No, that's not on the roadmap and I doubt it ever will be.

It's a very specific technology, and as long as it can be implemented fairly efficiently 'up the stack' in JS, then it mostly belongs there. Aside from HTTP2 (which is a roadblock now, but not soon) it'll be fine in JS.

[ Parent | on HN ]