This just makes it even more frustrating to me. Everything good about go is more about the tooling and ecosystem but the language itself is not very good. I wish this effort had been put into a better language.

▲

iTokio 3 days ago | parent | next [-]

Go has transparent async io and a very nice M:N threading model that makes writing http servers using epoll very simple and efficient.

The ergonomics for this use case are better than in any language I ever used.

▲

layer8 3 days ago | parent [-]

Implementing HTTP servers isn’t exactly a common use case in software development, though.

	▲	iTokio 2 days ago \| parent [-]
		Sorry I didn’t mean implementing a raw http server like nginx, but just writing a backend.

▲

p2detar 3 days ago | parent | prev [-]

> I wish this effort had been put into a better language.

But it is being put. Read newsletters like "The Go Blog", "Go Weekly". It's been improving constantly. Language-changes require lots of time to be done right, but the language is evolving.