Thanks for the crash course! Note: I think there is a typo at 23:10, I was following along and the make function says it takes int32[] and I had an error until I swapped to []int32 like the variable definition
I'm only half way through this tutorial and it's currently the best tutorial I've seen so far about Go. I've also started reading 2 separate books, and this is absolutely way better. Thank you!
When the video ended I was like "damn, wow", never before have I seen a tutorial that was so concise yet covered not only the main topic but also explained all side topics with great examples and visualizations. That gave me a better understanding of the whole flow, not just the code itself (cookies, csrf, base64, hashing), I also understood not only "what" and "how" but also "why". It's clear that you really know what you're talking about and have a lot of experience. I've seen countless tutorials and this is the first time I wrote a comment and first time I really felt like I shouldn't get this much value for free.
i have to admit this is the best tutorial BY FAR that i have ever studied! straight to the point detail equipped with memes make it top tier !! Thank you for doing the Lords Work 😂😂
At first, thank you for this amazing tutorial. I have a question arised at around 39:40: in the function square(thing2 *[5]float64)..., the return statement "return *thing2" actually returns a copy of the modified thing1. Consequently the result var and thing1 have different memory addresses. Am I right? If I am, I am afraid by returning a [5]float64 cannot save memories. I am a beginner to go, so please kindly pardon my possible mistakes.
Good video. I like how, if you eschew any kind of Web framework and stick with the net/http package, applying one or more middleware on top of a handler is just plain function composition; no magic. But no mention of jub0bs/cors ("perhaps the best CORS middleware for Go") in a video about Go middleware?! Unacceptable! 😅
In my opinion, a better approach is to use JWTs. Access-JWTs are better for performance since they are client based and don't rely on the database for validation, and more secure if stored in memory. Refresh-JWTs for continuous login, stored in cookies but you don't really need CSRF tokens to protect them since modern browsers have "SameStite=strict" attribute, you can still add CSRF token if you don't wanna rely on the browser for token-protection and that won't add overhead since Refresh-JWTs are long-life tokens flipped once every week or so. Nice video. You gained a sub lol. 🤍
Just discovered your channel Alex and I am so glad I did. This was really well explained and super easy to folow. Thanks a lot! Keep the Go videos coming please, I'd love to see an updated API tutorial with all of the above using the new mux in the std library.
Thanks a lot for the content. Do you ever think of doing the 1 hour crash courses for other languages? They saved me a lot when working on projects that came out randomly.
Thanks for watching. The thing is they take a loooot of time to do, and they are therefore a bit of a risk as they may not do well (see my python tutorial :) ). But I might some day
keep going , don;t make subscribers and watch make you sad , its time to be viral , greeting from me to you and Thank you a lot , and i hope you read my words and i hope it supports you , and we need more videos like middle-ware and logging and rate limit in golang
