Reactive Programming paradigm for Go for event-driven applications

[hoppp]

I rolled my own event driven solution when building a desktop app with go.

I can see this as useful for that.

[Peteragain]

I build robots, and Go looks just so much better than c/c++. Am I missing something? And this just bumps that to a "just so, so, so much better". Cool

[queenkjuul]

I've started learning Go as my next language. I really like it. I'm a JS dev by trade that knows Python and I've done some hobby work in C/C++. Go just really seems like a perfect middle ground--garbage collected, but static types; easy to read, performant, none of the Java inheritance and verbosity headaches. It took adjustment but i like assigning functions to structs and working with pointers.

And frankly having been working exclusively with reactive frameworks the last 3 years, this looks pretty exciting to me.

I have some low-level systems dev friends that have complaints about Go but they don't resonate with me. Coming from higher level languages, it's been fun. So like we're both missing something, but if you're like me, it's nothing worth worrying about. Single static binaries basically win me over on their own lol.

[liampulles]

Please don't Java my Go

[wizhi]

Generics opened the floodgates for this stuff, unfortunately.