Hello all, After 2.5 years of writing, countless weekends and evenings, I released a book about the Go programming language. The book is available for free on the website because I wanted to give something back to the developer's community :) It is composed of 700+ pages, 41 chapters, and approximately 405 drawings/screenshots. I tried to cover all the important topics that a new Go programmer should know. At the end…
Show HN: I wrote a book about Go
151–160 of 160 posts
Re: Show HN: I wrote a book about Go
#152How very generous of you. I know what I’ll be doing for the next few weekends at least... Thank you!
Re: Show HN: I wrote a book about Go
#153The website is unreachable
The only warning I got was a Free-Tier limit alert.
Re: Show HN: I wrote a book about Go
#154impressive amount of content
Re: Show HN: I wrote a book about Go
#155Earlier quoted context omitted.
Would you consider open sourcing the book? What systems are you using to create and maintain it?
Hello rijoja, I'm currently thinking about it. I'm writing the book with Lyx. Lyx documents are converted to LaTeX docs, then converted to HTML with pandoc. Then I have a homemade Go script that generates the VueJs components (one per chapter). This question is asked a lot so I will write something about the system because it can help other writers.
Thanks for your work anyhow :)
Re: Show HN: I wrote a book about Go
#156Earlier quoted context omitted.
On another note, you might want to consider converting the online copy of the book to MkDocs (using the Material theme), so that it's easier to read, navigate and search. I'd gladly lend a hand with this, if you like?
I like the current design, it is really clean and pleasant to read. I don't like Material Design, kind of makes everything look massive taking up too much space as if my desktop is a phone screen. for ex: http://angular-material.fusetheme.com/ui/forms Could be that it's just me though
Re: Show HN: I wrote a book about Go
#157Hello all, After 2.5 years of writing, countless weekends and evenings, I released a book about the Go programming language. The book is available for free on the website because I wanted to give something back to the developer's community :) It is composed of 700+ pages, 41 chapters, and approximately 405 drawings/screenshots. I tried to cover all the important topics that a new Go programmer should know. At the end…
In the code snippet provided at https://www.practical-go-lessons.com/chap-37-context#the-ser..., you made the channel unbuffered. The doWork goroutine would write to the channel and the "main" goroutine would read from it. But since the "main" goroutine could exit early because of context cancellation, they could get into the case of no one on the reading end any more, causing the doWork goroutine to be blocked forever (the writing to the channel is blocked when there's no one to read it).
Someone even published a paper about fixing this common mistake in open source projects a few days ago: https://www.reddit.com/r/golang/comments/m66djp/automaticall...
Re: Show HN: I wrote a book about Go
#158The website is unreachable
Hello andreagrandi, sorry to hear that, can you access the website now ? It's hosted on AWS with Amplify, I did not received any alerts regarding that. The only warning I got was a Free-Tier limit alert.
Re: Show HN: I wrote a book about Go
#159Hello all, After 2.5 years of writing, countless weekends and evenings, I released a book about the Go programming language. The book is available for free on the website because I wanted to give something back to the developer's community :) It is composed of 700+ pages, 41 chapters, and approximately 405 drawings/screenshots. I tried to cover all the important topics that a new Go programmer should know. At the end…
Re: Show HN: I wrote a book about Go
#160Always assume Go references are about the board game, always disappointed. Congrats on the book!
I thought this was a book on writing programs to play Go.
I feel at this point I should use this book to write a program to play Go using Go, and then in a way I wouldn't be so wrong.