Google Cloud's number one best practice is to minimize dependencies in a project ("every dependency of a library is a liability for everyone using it.") So if this is true, then why shouldn't it be one of THE worst practices to blindly use go dependencies, especially ones without specific versions? Or what about using github libraries that don't have 100% unit testing? It has perplexed me ever since the log4j debacle that all devs in all languages -- but especially ones using go's built-in test coverage -- have not adopted this best practice. Seems like grammar school level CM to me. In fact I'd expect the Security folks would lose their frikkin minds if they knew this was not happening.

This video is the perfect example of how a bad presenter can spoil the best of contents ! Pls dont waste ur time.

seems communication is more important actual knowledge now a days.. LOL

Hey can we use the websocket of graphql subscription to send and receive data through

it's always the least viewed videos that contain the gold

This video is underrated.

You taught us different widgets used to make the size responsive. Which one is efficient? Means one that wont affect the processing time.

Do we really need this in the day and age of chat GPT 4.0 ?

10:26 whats the difference between "package..." and "option java_package = ..."? why cant we just only use package ...? 10:26 Thank you for the Tutorial. Great work!

This was amazing thank you Mr Bok!

Hello, Great Video. I have a question does Go template work on docx files out of the box . I saw some GO github projects using libraries but they did not look being used a lot.

why not providing Source code 👎👎👎👎

Thank for the video

Wonderful content with depth. Thanks a lot!!

I like her vibe a LOT! It's a shame I am 1 year late but better late than never I guess.

Was it really need to have Tasks and Pub/Sub? Would not it be better to have only one Message Broker?

Based

Github Repo link?

🤤 *promosm*

I love you and love flutter and love google and love google co ❤

The AutoComplete widget is called on every page. Each page calls for different purposes. How about storing any text written in each auto complete text field in the respective page (I could only change the design of each text field and use it).

If you can take a feedback: you could have made this more interesting by simplifying and improving voice quality

HI tita

Use mocks for unit testing. Use the real thing for integration testing.

Sir please share the source code will be helpful for our project

I was having nightmares about having to integrate my Go backend/ WebApp with some strange Electron wrapped conglomerate. This is much better. I can use a Go / Sveltekit desktop for my Go/Sveltekit PaaS

very precise overview, thank you

*Summary* *Introduction* - 0:04 The speaker introduces himself as Alpha and gives a brief about his profession. - 0:20 Talks about his professional experience and his love for learning and sharing knowledge. - 0:56 Shares his experience with various programming languages and his projects. *What is gRPC?* - 1:45 Explains what gRPC is, its origin and functionality. - 2:48 Discusses the advantages of gRPC which includes high performance, duplex streaming, first-class load balancing, and auto-generated client code. - 4:00 Highlights the disadvantages of gRPC. *Difference between REST API and gRPC* - 5:25 Compares gRPC with REST API in terms of designed HTTP, messaging format, code generation, and communication. - 6:01 Discusses the comparison of different serialization schemes. *Who uses gRPC?* - 8:08 Shares the names of major companies that use gRPC like Netflix, Medium, Slack, Microsoft, etc. *Demo of gRPC in Android* - 8:24 Starts demo of how to implement gRPC in Android. - 9:00 Discusses the dependencies needed to be added in Android Studio. - 9:50 Explains how to create a new proto package and what a protofile looks like. - 13:01 Discusses how the protofile is generated. - 13:19 Explains what happens after protofile is generated and the use of User Service. *Conclusion* - 20:39 Talks about how gRPC is different from REST and how to debug the response from the back-end in gRPC. - 21:04 Recommends using Bloom RPC for testing gRPC. - 22:41 Ends the talk with a piece of advice for aspiring developers to build their own startups, stating that they need to find and solve a problem. Disclaimer: I utilized gpt4-8k 0613 to condense the video transcript into a summary. I employed Prompt 1 to generate timestamped bullet list and organize it into sections with titles at a cost of $0.18. The summary was manually formatted using KZbin comment markup. Prompt 1: "Summarize as a bullet list. Keep starting timestamps. Also split the resulting bullet list into sections. Create section titles. Keep timestamps for the bullets. Use this format for titles: *title*." Cost breakdown: input tokens: 4985 @ 0.03 / 1k = $0.15 output tokens: 428 @ 0.06 / 1k = $0.03

i like you examples

thanks for the video, I was just fighting alot, it just did not wanted to render my variabled, and now I found the fields need to be public,... capitalized.

Really great overview video for layouts. Thanks!

Great course! btw is there any link to the slide? Thanks.

Great intro, thanks

Awesome video 🔥

That's great! Just what I need!

Great talk, thank you Silvia!

Hi Jonathan is there a way to create a debounce of a cloud function using a task? I was thinking to * delete task with id * create a task with an id in 60 seconds But this doesn't work because the taskId is still there (despite the deletion in the queue was successful)

I'm not a web dev, and so maybe I am just not used to frequent templating usage, but compared to other templating engines I've seen, something about this just feels bad. From the awkward seperate templates all existing on the same level going to one mega not component, it just feels very wrong and quick to be confusing as your complexity grows. Maybe its just the way this quick demo was setup, but it feels like n^2 comprehension complexity

I mean how can I understand what she is saying danmn

Thanks Martha for a nice tut! Now Postman supports gRPC.

at 4:49 the function name is not mention in handle request

When you're trying to learn how debuggers work in go... you know you're in way too deep and could probably use some sunlight. But jokes aside, this is awesome stuff dude!

Nice presentation. Applauses to the nice presenter he did great job

Very helpful, it’s seems like gorilla packages get a lot of love 🎉

This is amazing advice !! ❤! Wonder why there are not many views or comments ?😮