I haven't used zeromq in forever, but did they ever fix the problem with request/reply sockets where the server socket could get into an indeterminate state after a client socket drops at just the wrong time?
I feel like I've been seeing Racket come up more often recently. It's interesting to me that it seems to be winning the scheme wars when there are other excellent distros out there (such as Chicken and Gambit). Has anyone shipped any software with Racket? I'd be curious to hear about it in real world scenarios (e.g., long-running processes and deployment).
It's nice to see some content for modern OpenGL -- it's been a while since I've done any raw GL programming, and I understand the newest specs are finally deprecating the mess of APIs that have accumulate. Last I saw there were many different ways to render polygons (immediate mode, display lists, vertex arrays, vertex buffer objects...) and I can only imagine it's a nightmare for people just getting started.
A common pattern I've seen with companies sprinting head-first into a microservices architecture is something I call "femtoservices" -- when your system is new and doesn't do much, it's easy to split things up into components that are way too small. I've seen systems that essentially have a microservice per database table, effectively destroying any reasonable way to perform non-trivial queries. Fixing this is far harder than splitting out a monolith that has been designed well.