There are no trivial one-page TODO applications. Just real web application production. Go is considered to be great for web development, so why is it so difficult to make even a simple tweeter clone? Why no one can give me a specific example of how to hash and store user passwords? Or how to build the rest of the authentication system?


Why is it so difficult to share my database connection with my handlers or how to send email to users without slowing down each web request?
Can someone tell me how to organize my code? Why so many different opinions on this? Which one is right? Should I use MVC? What is this project? Ugh! I want to give it up!
You’ve heard that Go is great for web applications, but getting started leads to a lot of questions that can be overwhelming. But what if you can create a web app this week, starting today? What if you have someone who guides you through standard libraries and helps you understand how they all work together?
“All you need is a standard library” - all on the Internet
I can’t tell you how many times I’ve heard about this when learning to build web applications with Go. I began to learn Go, reading the standard library and every tutorial I could find, but I quickly ran into a problem.
Instead of creating HTML templates and rendering real dynamic content, we instead used fmt.Fprint () to print hard-coded HTML.
Or, when we need access to the database, I created a global connection and shared it with everyone. Hmm!
As a result, I could not figure out how to do this by creating the first few pages. It was unpleasant, if not more.
While I was stuck, I kept asking myself questions such as ...
“How can I share my database connection with my handlers?”
“How to safely use a user’s hash password?” What is the correct way to authenticate a user and access this resource? ”
“How do I organize my code? Where does the MVC pattern fit all this? Is my project RESTful? Will it be difficult to maintain it? ”
No matter how many textbooks I read, it always seemed to me that something was left. Some of the larger picture, which was not explained, left me unsure how to proceed.
The main problem was that in every single textbook I read simplified things, and I needed a full course to show me how all the parts work together.
Web applications are complex systems.
After I built my unfinished TODO application, a one-page wiki, or some other contrived example, I almost gave up.
My progress was very slow, and every time I solved one problem, I found myself faced with two new ones. I still did not know how to connect all the parts together.
It was as if someone handed me a toolkit, taught me how to use each tool, and then said: “Now you know how to build a house!” Damn it! Within a week my house would have exploded if it worked.
It is not enough just to find out how each tool works. Knowing how to use tables, nail saws and strength exercises does not allow me to build a house. You need to learn how each part of the house connects together. How the roof connects to the frame, how the frame is supported by the foundation, how much space is needed for the ventilation holes in the frame and countless other parts. In short, you need to know how everything works together.
So why do we keep thinking that this approach will work for web development? Why we continue to tell new ways: “All you need is a standard library for creating web applications!”
Technically, this is not inaccurate, but, of course, damn it, this is not the ideal way to learn, and this causes developers to break through countless tutorials, read endless documents and try hundreds of bad approaches before they finally get everything right . And even then they are not sure what they did right. They just know that this has not failed.


https://www.usegolang.com/