Introduction to gRPC: A general RPC framework that puts mobile and HTTP/2 first (M.Atamel, R.Tsang)

[@MegaMurcelago]

gosh im in love with that turbofan laptop picture

[@90hijacked]

These guys are so passive aggressive towards each other this clip could pass as standup comedy, love it

[@venkataabhiramsrivatsavape229]

Energetic Seminar for gRPC.

[@truthseepeaking]

These guys were having too much fun on the stage

[@prakharbansal1]

Really awesome video on this subject.

[@patriciasquared]

congrats on the live demo!

[@nooruddinraotiwala490]

hey amazing work explaining so simplifiedly and funny way😃🙌....!!!!

[@chunjie0515]

要说用得最舒服的grpc server构建,还得是微软的一套东西

[@cppdev2729]

don't see how this was more simpler than cobra

[@javadborhani7838]

it's quite funny how well java programmers typing confidently and c# developers just copy and paste or watch and type. it even happens in Microsoft build or their events. anyway I'm a c# developer

[@obinnaokafor6252]

Funny comment

[@joshuam6013]

this was so cool!

[@patle8229]

could you share the demo code ? 😁

[@sirAvdul]

One thing, does the client needs the protoc file too? If yes, does the server and the client share/use the same protoc file?

[@madhudson1]

They share the same protobuff file, yes

[@abhishekdk5040]

It's an API contract which both client and server abide by

[@pwilll]

40k views and 15 comments? Who says developers aren't social? Because they're correct lmao

[@MaestroCipher]

Putting RPC over HTTP is inefficient and ugly. HTTP is an application level and RPC should travel via transport level, that would be the good design. Why do we require the HTTP in this case? We can easily define multiple streams inside single TCP or TLS connection if needed, other protocols also could be an option, SCTP for ex. You talk a lot about efficiency here, but using HTTP as a transport is really an inefficient part. A also wonder why people forget and do not use good things invented and developed, like SCTP.

[@utkarshdixit9675]

did you get raise, after demo ?

[@vishvajeet7625]

lol

[@markcuello5]

HELP

[@sidekick3rida]

Java is so verbose and ugly and disgusting.

[@kartikchauhan5498]

If gRPC is this much fast then use it in damn chrome. It consumes up my system's whole memory.

[@amelemara4615]

grpc is a messaging protocol over the network between a website (client) and its servers.Chrome just renders what a website tells it to. The use of gPRC depends on what websites you use and if they use it. So like going to netflix you might be using grpc but going to facebook they might be talking over a different protocol like REST.

[@mehmetesen9385]

grpc has no bussiness with your chrome, also chrome is very good at memory handling, you should buy ram.