TinyGo and Raspberry Pi Pico: More on Interrupt Handling

A viewer asked me an interesting question about whether processing of interrupts is concurrent or parallel on the Pico and TinyGo. Rather than answer in a message, I figured I'd illustrate by means of an example.
Website: pragmatik.tech/
GitHub: github.com/pra...

[@tonygilkerson]

Very good, that helps clear up alot. Keep the videos comming!

[@tonygilkerson]

I am looking forward to seeing the Channels, I have been playing around with it a bit and it seems to be a good way to asynchronously pass messages around from one method to another.

[@tonygilkerson]

awesome! again, great content it is hard to find TinyGo examples, everyone uses C or Python and i am just not a fan.

[@muhammadfikririzalalamin6018]

can you explain how this code can read the encoder precisely,

[@tonygilkerson]

I have another unrelated question. I am interested communication between two Picos so I can break down my project into components. What is the simplest way to pass messages between two Picos that are physically close to each other? Then I would like to wrap that in some channel messages! I would love to hear your thoughts on this.

[@pragmatiktech]

I know some people use I2C or SPI for this. When TinyGo supports BLE or WiFi, we should be able to use regular TCP communication, I believe.