5 minutes into the video and you've made more sense than the last 10 videos I've watched around Go concepts. Incredible approach to teaching while covering real world scenarios. Amazong job. Subbed!
@@edwingarcia5043 That happens too, doesn't it. Great point (if not misplaced)! Most likely, it doesn't materially negate the effectiveness of Francesc's approach. It's a vector field and Rob seemed to clearly be using a short-hand to say, "damn, this vector has a magnitude and direction that helped me."
Very clear explanation, with mental leaps just at the right times. And also blending the real world use cases into the examples is very well thought of. Thank you!
Priceless, as always. What about an episode about how to create applications that work at the same time on multiple servers, as a cluster? The guides I have seen are ambiguous and do not share the good practices they proclaim. That, or an episode about when it is recommendable to create gorutines and when not. Thank you, Francesc!
JustForFunc yeah, a cluster database, a load balancer, a proxy to redirect http traffic, or a massive scanner which distributes traffic between available servers (my original idea was something pretty similar to this) and when it finalizes, joins results. Thank you!
Thanks Frances, was a clear explanation. Can you please do the next episode about package initialization, sharing variables (like db / session) around between packages?
Great video. A very important concept for setting up and handling things like timeouts and even exceptions in Go. I don't see this being addressed in other Go overview sites/videos. Really happy to come accross this. However, perhaps its just me but I don't think the last point/topic on sending value between "client.go" and "server.go" had appropriate phrasing from @justforfunc. I get his explanation for "foo" id to properly show up, the client has to include it as a header/body/uri-id as they are purely HTTP request data/communication. But that has nothing to do with inherently Go or even "context". I sort of interpreted this context as some internal "Go" communication between the client.go and server.go processes. And really the context in both client.go and server.go are between the those process' and operating system, but something like an HTTP client and server are really good examples to show where "context" is very applicable. Really good video but slightly misleading.
Hi, I would love to hear from you, as someone with a lot of experience in Golang, do you think SOLID Principles important in practice, and in interviews? Would I be asked a lot of questions, and how would I go about that, considering that SOLID Principles are mostly OOP concepts, and Golang is not a real OOP language. I am also curious about the same for design patterns like Builder, Factory pattern etc
Regarding the ability for the HTTP client to "cancel" the request via the context which notifies the HTTP server, I assume this would only work with such a golang client and a golang server, correct? I.e. this is impossible with say a Java client and golang server, correct?
Francesc, I know this is an old Just for Func but I went back and watched it today and wanted to say Thanks! Great episode. As others have said, the explanation is perfect! Just what I needed. Thanks again and keep up the great work!
I really, really, really would like to see complete series about how to create IDIOMATIC Client Server WEB application with most common CRUD operations using gRPC and MySQL. Client and Server should be just simple Go programs. Would like to see: IDIOMATIC Directory/File organization in context of github.com/myusername/. gRPC service interface, and message/+field idiomatic naming and organizing into packages. Package +nested package importing. Compiling nested .proto's. TLS secured gRPC communication. Idiomatic endpoint URL constructions. Context. Displaying in browser - single record, list of records, single record + list. Submitting form, updating record, creating nested records - like, when customer is created, also some log record in the same DB is created pointing to the same customer (tx). And so on so on. Basically, EVERY beginner want to see complete IDIOMATIC example of writing production ready basic DD web-page. Nobody is teaching this. 98% of tutorials and books teaching the easiest way - Just mess everything into main.go and use mock data! This is total BS! This is not how good things should be teached. It is much better when you see, how great foundation looks like and then starting to tweak, and to learn all those used patterns in details. When you have no context in head, it is impossible to learn right way. Iterating thru the trial & fail is way to learn for sure, but it is not the most effective! It just wastes too much human time. YES - this kind of tutorial will take time to record. But this will be the SINGLE PERFECT TUTORIAL in the whole f*g WEB.
Who's here from the Aug 20th Go Time podcast? BTW at 21:00 - since go1.13 - you can now do this in one call with: golang.org/pkg/net/http/#NewRequestWithContext
Learned Context in one go, without even pausing a single sec. :) btw which editor you are using and i saw you have some template like hand -> f(w http.Responsewrite, r *http.Request), how to do it?
useing a function (sllepAndTalk) you created for half of the video ,and not showing how that function worked was a waste of my time. thank you for frustrating me back to the doc.
I keep coming back to this video over time. It has a lot of value. Thanks for taking time and doing that. Where are you by the way, get back here and produce some more please.
Hi, looks like using context.WithTimeout somehow tears down TCP half-connection from client to server, that's why you got context closed on the server side. I didn't get how it closes the half-connection. But the question is why context.WithCancel does not tear down TCP half-connection after invoking cancel() ?
I kept trying sending value with a context over the http to another machine, I stopped after I watched this video. Very detailed! I love your videos :D
T-h-a-n-k y-o-u. ------------------------- I was really going to send you a message requesting exactly this :) Love your channel so far. Keep it up!!!!
Hi.. I really love to watch your videos. First video of you that I watched was "Go Tooling in Action", and That Was Awesome. That night I watched five of your videos, despite that I had to go to office next morning. They were really great. Now that I know, you review codes and even I can suggest one, I would really appreciate if you take a look at github.com/a4abhishek/CITF. It has created just a few days ago, so it is not yet ready to be reviewed by someone like you, but still I wanted to share this with you, so maybe after couple of weeks or in a month, you can actually review this. I will be waiting for that. Thanks. Keep teaching us.
Thank you for this, this is amazing. I have read about context package, but couldn't really understand. But this 36 mins have been priceless. Very well done.
Thanks for the great video. This video was just the right speed and amount of explanation that I needed, very to the point. Watching you code through the examples, I learned things other than the context package too.
Hi, amazing stuff! I was still struggling on how to use context skimming the official docs. However this is simply awesome. Especially thanks for showing that you can't send context values across network.That would be stupid idea anyway :-)
I love the preaching of good practices like not using the context to pass values unless absolutely necessary. This aligns with how I like to write code, even though I've seen other developers use context to pass non-request scoped data. This channel seems to be a hidden gem!
5 minutes into the video and you've made more sense than the last 10 videos I've watched around Go concepts. Incredible approach to teaching while covering real world scenarios. Amazong job. Subbed!
What makes you think that the other videos didn't help you to get ready for watching this one video? 🤔
@@edwingarcia5043 That happens too, doesn't it. Great point (if not misplaced)!
Most likely, it doesn't materially negate the effectiveness of Francesc's approach. It's a vector field and Rob seemed to clearly be using a short-hand to say, "damn, this vector has a magnitude and direction that helped me."
I’ve been learning go for less than a week, and just encountered your channel. Sad to see you no longer upload, these videos are really good.
Very clear explanation, with mental leaps just at the right times. And also blending the real world use cases into the examples is very well thought of. Thank you!
Wow, that's such a nice thing to say!
Thanks 😊
Priceless, as always.
What about an episode about how to create applications that work at the same time on multiple servers, as a cluster? The guides I have seen are ambiguous and do not share the good practices they proclaim.
That, or an episode about when it is recommendable to create gorutines and when not.
Thank you, Francesc!
+Miguel Ángel Jimeno Arce can you give an example? Do you mean something like a cluster database?
JustForFunc yeah, a cluster database, a load balancer, a proxy to redirect http traffic, or a massive scanner which distributes traffic between available servers (my original idea was something pretty similar to this) and when it finalizes, joins results.
Thank you!
Thanks Frances, was a clear explanation.
Can you please do the next episode about package initialization, sharing variables (like db / session) around between packages?
thanks Frances, the quality of this video and its contents is exceptional :-)
I wonder how many developers would recognise "modern bear" t-shirt. Thanks for fueling up my desire to learn Go! Woof 😋
I have no idea about how the function sleepAndTalk know we cancelled
I had the same question. So, I googled this: gist.github.com/astenmies/2f180213d310aa16b4b8c4e637be9441
@@KotBinary thanks :)
Amazing explanations with examples. One of the most talent instructors.
Thanks you and keep doing it.
Thank you! I don't understand why no one starts by giving simple example like you do
where is the sleepAndTalk fn ?
Best video on the topic. Thanks
I really enjoyed this episode - thank you! I've seen context used a lot and never really understood it until now. ❤️
Great video. A very important concept for setting up and handling things like timeouts and even exceptions in Go. I don't see this being addressed in other Go overview sites/videos. Really happy to come accross this.
However, perhaps its just me but I don't think the last point/topic on sending value between "client.go" and "server.go" had appropriate phrasing from @justforfunc. I get his explanation for "foo" id to properly show up, the client has to include it as a header/body/uri-id as they are purely HTTP request data/communication. But that has nothing to do with inherently Go or even "context". I sort of interpreted this context as some internal "Go" communication between the client.go and server.go processes. And really the context in both client.go and server.go are between the those process' and operating system, but something like an HTTP client and server are really good examples to show where "context" is very applicable.
Really good video but slightly misleading.
Thank you, you're REALLY doing well. Thank you one more time!!!
This video is my go to reference material on go's contexts. Thank you very much
Great video! I watched 2 talkes before and was more confused about contexts after watching them.
this video explained everything!
Hi, I would love to hear from you, as someone with a lot of experience in Golang, do you think SOLID Principles important in practice, and in interviews? Would I be asked a lot of questions, and how would I go about that, considering that SOLID Principles are mostly OOP concepts, and Golang is not a real OOP language. I am also curious about the same for design patterns like Builder, Factory pattern etc
Do you have any other example for context with value other than request id? It would be better to understand this concept if you can. Thanks!
Regarding the ability for the HTTP client to "cancel" the request via the context which notifies the HTTP server, I assume this would only work with such a golang client and a golang server, correct? I.e. this is impossible with say a Java client and golang server, correct?
lets say about following the trace-id and span-id, both are probably good values for contexts right?
Learning Golang from Bayer Mayfield. The best
From time to time I come back here and watch a random video. It inspires me so much. Thank you.
Francesc, I know this is an old Just for Func but I went back and watched it today and wanted to say Thanks! Great episode. As others have said, the explanation is perfect! Just what I needed. Thanks again and keep up the great work!
I am big fan from China who watch your video every day before sleep! 😀
What's the != symbol at @15:46? Shouldn't it be !=?
Nice vscode setup. Can you describe the exact set up somewhere in a post or video?
I really, really, really would like to see complete series about how to create IDIOMATIC Client Server WEB application with most common CRUD operations using gRPC and MySQL. Client and Server should be just simple Go programs. Would like to see: IDIOMATIC Directory/File organization in context of github.com/myusername/. gRPC service interface, and message/+field idiomatic naming and organizing into packages. Package +nested package importing. Compiling nested .proto's. TLS secured gRPC communication. Idiomatic endpoint URL constructions. Context. Displaying in browser - single record, list of records, single record + list. Submitting form, updating record, creating nested records - like, when customer is created, also some log record in the same DB is created pointing to the same customer (tx). And so on so on.
Basically, EVERY beginner want to see complete IDIOMATIC example of writing production ready basic DD web-page.
Nobody is teaching this. 98% of tutorials and books teaching the easiest way - Just mess everything into main.go and use mock data! This is total BS! This is not how good things should be teached.
It is much better when you see, how great foundation looks like and then starting to tweak, and to learn all those used patterns in details. When you have no context in head, it is impossible to learn right way. Iterating thru the trial & fail is way to learn for sure, but it is not the most effective! It just wastes too much human time.
YES - this kind of tutorial will take time to record. But this will be the SINGLE PERFECT TUTORIAL in the whole f*g WEB.
Thanks Very clear explanation.
That poor plant in the background needs water
Very nice explanation! Thanks
Who's here from the Aug 20th Go Time podcast?
BTW at 21:00 - since go1.13 - you can now do this in one call with: golang.org/pkg/net/http/#NewRequestWithContext
Learned Context in one go, without even pausing a single sec. :) btw which editor you are using and i saw you have some template like hand -> f(w http.Responsewrite, r *http.Request), how to do it?
This is some good quality content!
useing a function (sllepAndTalk) you created for half of the video ,and not showing how that function worked was a waste of my time.
thank you for frustrating me back to the doc.
how to model go projects ...id be happy
Disclaimer: kinda new to golang XD
What do you mean by "defining a request without using tags?"
Excellent explanation. This is very helpful. Thank you!
I keep coming back to this video over time. It has a lot of value. Thanks for taking time and doing that. Where are you by the way, get back here and produce some more please.
Hi, looks like using context.WithTimeout somehow tears down TCP half-connection from client to server, that's why you got context closed on the server side. I didn't get how it closes the half-connection. But the question is why context.WithCancel does not tear down TCP half-connection after invoking cancel() ?
Thank you for this video.
Loved this video. Watched a few that didnt quite get through, but this really brought into the right “context” xD
Very helpful, thank you.
with cancel is not working for me
phenomenal explanation, thanks!
I kept trying sending value with a context over the http to another machine, I stopped after I watched this video. Very detailed! I love your videos :D
where can I find the codes which are written here?
Deep dive in context ...id be glad
Amazing explanation with real world examples. Thank you so much!
T-h-a-n-k y-o-u.
-------------------------
I was really going to send you a message requesting exactly this :)
Love your channel so far. Keep it up!!!!
Beautiful, Excellent, Mind Blowing, Priceless
Hi.. I really love to watch your videos. First video of you that I watched was "Go Tooling in Action", and That Was Awesome. That night I watched five of your videos, despite that I had to go to office next morning. They were really great.
Now that I know, you review codes and even I can suggest one, I would really appreciate if you take a look at github.com/a4abhishek/CITF. It has created just a few days ago, so it is not yet ready to be reviewed by someone like you, but still I wanted to share this with you, so maybe after couple of weeks or in a month, you can actually review this. I will be waiting for that. Thanks. Keep teaching us.
That's what i needed.
BIG THANK YOU
Incredible talk.
Nice, learnt allot. PS can you also give the reason behind values not propagating like cancel please?
Great video. I'd been reading about context this afternoon and this very much tied up some mental loose ends I still had.
What vscode theme is this?
Thank you for the great videos. This is really helpful.
Thank you for this, this is amazing. I have read about context package, but couldn't really understand. But this 36 mins have been priceless. Very well done.
Thanks for the great video. This video was just the right speed and amount of explanation that I needed, very to the point. Watching you code through the examples, I learned things other than the context package too.
i read a lot of posts on medium and the GO blog about context and i was completely lost... with this video it was very easy to understand. Amazing job
Thanks so much! 7 minutes in and I now understand what the code does that I was trying to decipher.
how do I set up visual studio to add the package library while I writting code? I always need to do it for myself and is anoying
Hey, very nice video! Could you make an episode about you vscode setup and the extensions you are using? Thanks!
gooooooooooood shit
like your tee!
Really nice, clear my head lots on this package
Hi, amazing stuff! I was still struggling on how to use context skimming the official docs. However this is simply awesome. Especially thanks for showing that you can't send context values across network.That would be stupid idea anyway :-)
I was following along typing in another window and 13:51 scared the xxxx out of me... :)
f awesome.
Amazing explanation! thank you so much
I love the preaching of good practices like not using the context to pass values unless absolutely necessary. This aligns with how I like to write code, even though I've seen other developers use context to pass non-request scoped data. This channel seems to be a hidden gem!
Kind of got scared by the video length at first though, glad I watched it anyways.
Thank you Frances, it’s really help me to understand context package.
very helpful, thanks very much
Thanks.
Great experience! Thank you so much
I got a doubt. When u write a handler with select case, context will be cancel only because your time.After are holding execution and than
I got it!! It will be able to run on a different goroutine returning value and catch it into select statement
thanks Thor.I now understand Go better
I'm so glad I found your TH-cam channel ! This video is perfect to understand how to use the Context package, thx !
One of the best explanation!!! Thanks.
Really enjoyed the explanation, very clear 👍🏽
I've been learning so much watching your videos! Thank you very much.
Really helpful video, thank you dude, keep up the great work!
That was very useful, thanks!
Really informative video. Thanks Francesc.
TH-cam give us a love reaction, pls: D
This helped me understand the context package much better, thank you!
thanks! really helped (at work)
Please keep the good work up. So good.
Subtitles on: 'Hi! I am Franciscan boy!' :p
Exceptional work!
Does any one else hear "just for fuck" in the beginning?
I think it's just you ... and maybe the automated TH-cam subtitles
Very Nice! Thatk you Francesc!
Hey Francesco, huge thanks for your series of videos. was wondering if you can post the code repo on github
+Anh Nguyen it's on GitHub.com/campoy/justforfunc
Francesc, Did you do the episode on the internals of the context package?
Yup, literally the episode after this one
This was super helpful, thank you.
Couldnt figure out what you did in the Decorate. I think I need some sleep..
it was basically a middle ware which adds in a request id into the context and returns the next function as a call
Amazing... Short and sweet!
damn, is there any chance you are a Thor?
Awesome!!!