linkedin
Refocus readme to usage of goavro rather than 2.0 justification
I think the readme would be much more useful if some more key examples were added to the readme (I think the OCF reader should be on the front page). I think the 2.0 changes should be at the bottom.
As a side note, I think the library could be less confusing if the concept of "native go" was more defined more prominently, and perhaps actually toned down in the actual api. For me the largest use-case is to scan to a struct & visa versa. I don't see people using the go native map to access data.
Just some constructive criticism for you to use as you'd like
As a side note, I think the library could be less confusing if the concept of "native go" was more defined more prominently, and perhaps actually toned down in the actual api. For me the largest use-case is to scan to a struct & visa versa. I don't see people using the go native map to access data.
+1
