Thank you for the read and trying it out. Yes this particular article does not use gRPC. However, it uses the Protocol Buffers, which is an ingredient of gRPC. So the device uses the protobuf wire format to exchange info directly with the server.
I dont know any implementation of grpc framework that would generate (c) code that would run on the esp8266. Not to say it’s impossible.
Using Go plugins as a way of code sharing is one of several ways of building Go programs. Plugins are designed to be dynamically loaded and linked as are done in other programming environments. However, when building statically compiled/linked programs the compiler does everything.
Benjamin Maisano thank for the feedback. Yes, it’s been a while since I have written about this subject. The new module concept introduced in version 1.11 of Go is all about source code modularity for the purpose of dependency management and source reproducibility at buildtime.
Hi Lukas Lukac , thanks for reaching out. Yes it is possible and it depends on the Reader implementation. For instance you may have reader that streams from a network source. A Read() call may return zero byte and a nil error (specially if it’s from a buffered source, it may mean that data has not been buffered yet, to come back with subsequent…
Joseph Heck good point you made about the progression of API versions which may require client code to change. This is a big issue and should be discussed. That sound like good future topic for the publication!
Thanks for the feedback.
Degas Shi, thank you for feedback.
However, the quote you have is an incomplete and taken out of context. The full definition from the text is:
> Given bit
x, in Go
^x = 1 ^ x
If we are talking about a single bit
x (which is the text does), the definition stands.