For those who were at my session at @golab 2 days ago, I've published my slides: https://github.com/dolanor/talks/tree/main/rip (they are in the present format, ask if you need help)

I also managed to add the protobuf encoding during my train misadventure. So that's 1 less thing to do. : https://github.com/dolanor/rip/commit/fbed4c0620c7a075e8493936759c696384c84037

I'm working in improving the error handling right now.

#golab2023 #golang

talks/rip at main · dolanor/talks

Contribute to dolanor/talks development by creating an account on GitHub.

GitHub

@golab BTW, to the person who asked if the project was production ready. I saw you were disappointed after.
I hope you play with the project and see if it already helps you in its current state.

I want to achieve high standard. So for me, it feels it's far from done.

But based on many projects I worked on, most of the HTTP part I saw were sub par and inconsistent. So maybe it's already better?

After all, it's just a router with some encoding logic and some already baked in HTTP error handling

@dolanor You promised me a link to the "do bad generic things" competition as well :)

@Merovius Indeed, I did.

I updated my slides to include those links plus the whole Genericronomicon.
https://github.com/dolanor/talks/commit/1e610998d37e05914b24b94dbc25e250cc852848

add links to bad use of generics · dolanor/talks@1e61099

Contribute to dolanor/talks development by creating an account on GitHub.

GitHub