Comparing gRPC and REST: A Comparative Analysis

Features	gRPC	REST
HTTP 1.1 vs HTTP 2	Follows a client-response model of communication and is built on HTTP 2, which allows for: streaming communication and bidirectional support.	Follows a request-response model of communication and is typically built on HTTP 1.1.
Browser Support	Limited browser support. gRPC requires gRPC-web and a proxy layer to perform conversions between HTTP 1.1 and HTTP 2.	Universal browser support.
Payload Data Structure	gRPC uses Protocol Buffer by default to serialize payload data.	REST mainly relies on JSON or XML formats to send and receive data.
Code Generation Features	gRPC has native code generation features.	Developers must use a third-party tool like Swagger or Postman to produce code for API requests.

Five Hidden GitHub features that will make it much easier to contribute to open source

 1. Whitespace

Adding ?w=1 to a git diff URL will hide all changes in the whitespace, enabling you to see only the code that has changed.

2. The Github dev web-based editor GitHub's web-based editor allows you to navigate a repository's files and source code to make, and commit, code changes. You can open any repository, fork a repository, or open a pull request in the editor.

3. Octotree Octotree is a browser extension that enhances GitHub code review and exploration. It helps you navigate directories and open files with a familiar tree-like structure.

https://chrome.google.com/webstore/detail/octotree-github-code-tree/bkhaagjahfmjljalopjnoealnfndnagc

4. w & t Navigate your project quickly. On your repository’s home page, type ׳w׳ to quickly bring up a quick filter panel for your branches. Inside your repository, type ׳t׳ to jump into a quick file selector. Select your file and just hit 'Enter'.

5. Commit History by Author To view all the commits on a repo by author, `add ?author={user}` to the URL.