---
title: "Comment by Wei Lun on \"gRPC - the new REST!\" | Hashnode"
description: "gRPC is just too complex."
url: "https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60dbc11f7ad49f6471accac3"
---

[Discussion](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4)

Comment [gRPC - the new REST!](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4)

[Wei Lun](https://hashnode.com/@weilun)

[Jun 30, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60dbc11f7ad49f6471accac3)

gRPC is just too complex.

[Ankeet Maini](https://hashnode.com/@under-engineered)

[Jul 9, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60dbc11f7ad49f6471accac3#reply-60e8afa88aaa3f019846ce8f)

isn't it easier, as you have now auto-generated stubs for all the available service methods?

this will make the integration between backend and frontend super tight - same contract is used to generate the code on both ends, no more searching the correct payload or api endpoint :)

[Wei Lun](https://hashnode.com/@weilun)

[Jul 12, 2021](https://hashnode.com/posts/grpc-the-new-rest/60d96711703d372ea06c71e4/comment/60dbc11f7ad49f6471accac3#reply-60ebede0c551f16b0f85139d)

[Ankeet Maini](https://hashnode.com/@under-engineered) yeah it may sounds easy, but the complexity is on the generation of stubs. For examples:

-   Whether commit stubs to source code or not
-   When to regenerate when protobuf change
-   Dealing with protobuf import paths hell
-   How to version correctly

etc etc...