Heavy snowstorm outside but you made the sun shine :) Thank you for videos on interesting topics on Go and not just the bare basics. Seems like I'll be spending some coffee on you...
Would have been nice if you showed the size of the protobuff version of person for comparison to JSON and XML, otherwise nice vid : ) I guess we could find it for ourselves by counting the bytes in your marshalled output? I'm just lazy tbh
Hi Elliot, I followed your tutorial and generated person.pb.go successfully but when trying to execute the code in main.go file like you, getting the error like "./main.go:14:12: undefined: Person'. Please help me in this same as i am a beginner in golang. Thanks in advance.
What is this line exactly doing? newElliot = &Person{} It points to address of Person struct? It seems to be unreasonable. Is there other use of & at the beginning of type?
I know this is beyond the scope of this lecture, but anyone know about grpc/protobuf schema stitching? Sort of like Apollo Federation or Google's Rejoiner. I'm kind of a newb working on a project, and one of my services is essentially a client to about 15-20 different api's. I'd love to only have a single unified layer expose that service to the rest of the services. Hopefully that makes sense!
You forgot to circle back around to the final size of your serialized object using protobufs rather than XML or JSON. Looks like the final size of the original object that includes your name and age came out to 10 bytes. Compared to 35 bytes for JSON and 56 bytes for XML.
Just 1 recommendation, if anyone has been getting package as __ in person.pb.go. I encountered the same problem and the way to resolve that is to put option go_package = "./;main"; in person.proto file Happy learning...
depending on the number stored, it may encode to just one byte because it's a varint under the hood(not including the "tag" of the field) developers.google.com/protocol-buffers/docs/encoding
Great info. Always find the tutorials you make really cleanly structured.
Thank you, that was a lot easier than I thought it was going to be.
Heavy snowstorm outside but you made the sun shine :) Thank you for videos on interesting topics on Go and not just the bare basics. Seems like I'll be spending some coffee on you...
Great. Please continue on gRPC path!
Would have been nice if you showed the size of the protobuff version of person for comparison to JSON and XML, otherwise nice vid : )
I guess we could find it for ourselves by counting the bytes in your marshalled output? I'm just lazy tbh
Great tutorial and I love your accent! I keep hearing "egg smell" when you say XML. :)
Or "Geogl" :))
Hey man, really nice video. Sweet and simple. Easy to understand.
Cool. I've never heard of it. I was searching how to use the X protocol on mysql, and then it was mentioned there. Got curious and ended up here :D
Thank you for the video!! Keep it up!!
Works like a charm
Nice video. Are you from Scotland? :)
A lot of help, thanks!
Please can you make a video on how and why we set up the paths?
:c
Hi Elliot, I followed your tutorial and generated person.pb.go successfully but when trying to execute the code in main.go file like you, getting the error like "./main.go:14:12: undefined: Person'.
Please help me in this same as i am a beginner in golang. Thanks in advance.
very useful thanx
i have 1 query while unmarshalling we are using getAge and GetName method but we didn't define it and how it is working ?
i got it, thanks
Very useful thank you!
what' your IDE tool?
Visual Studio code! :)
What is this line exactly doing?
newElliot = &Person{}
It points to address of Person struct? It seems to be unreasonable. Is there other use of & at the beginning of type?
@Ed Tix It is creating object alternative code can be obj :=new(Person)
I know this is beyond the scope of this lecture, but anyone know about grpc/protobuf schema stitching? Sort of like Apollo Federation or Google's Rejoiner. I'm kind of a newb working on a project, and one of my services is essentially a client to about 15-20 different api's. I'd love to only have a single unified layer expose that service to the rest of the services. Hopefully that makes sense!
You forgot to circle back around to the final size of your serialized object using protobufs rather than XML or JSON. Looks like the final size of the original object that includes your name and age came out to 10 bytes. Compared to 35 bytes for JSON and 56 bytes for XML.
Good catch!, Thanks for doing the math and highlighting this!
@@Tutorialedge Forgot to add that it is a great tutorial!
How do you made coloured ()?
The Bracket Pair Colorizer extension for visual studio code handles this for me! A very handy tool when trying to quickly scan over code! :D
I am so thankful you asked this question and thank you @TutorialEdge for bringing this extension to my attention
Most of the cli steps don't work anymore as far as I can tell. This video is 5 years old I didn't really expect it to still work.
is there a tutorial with Python?
Just 1 recommendation, if anyone has been getting package as __ in person.pb.go.
I encountered the same problem and the way to resolve that is to put
option go_package = "./;main";
in person.proto file
Happy learning...
Thanks but please increase the fontsize
Thank you for the feedback, I will try to improve font size in my future videos!
Good thing we used a 32 bit integer for the persons age. As we all know it's not uncommon for humans to reach billions of years old.
You might be calculating age in seconds? ¯\_(ツ)_/¯
depending on the number stored, it may encode to just one byte because it's a varint under the hood(not including the "tag" of the field) developers.google.com/protocol-buffers/docs/encoding