6 ms·

Thanks for the reply. Maybe it has changed over the time but what i have meant was mostly about the way an application is built with golang. Let me give you an

Thanks for the reply. Maybe it has changed over the time but what i have meant was mostly about the way an application is built with golang. Let me give you an example, it might be easier for me to explain it this way. Writing a web application that responds to a post request. I am guessing I can use net/http library to achieve that. But does it implement CSRF prevention automatically, or should I be already informed about including it as a developer? I would be grateful for letting me understand this part. I am not against the language, but just curious.

bpizzi 8y ago
> Writing a web application that responds to a post request. I am guessing I can use net/http library to achieve that. But does it implement CSRF prevention automatically, or should I be already informed about including it as a developer? I think I get where you may come from. Indeed, Golang (the language and its standard lib) is not a framework-language toolkit ala RoR. The standard lib is providing building blocks with really straightforwards and clear documentation (check https://golang.org/pkg/net/http/#pkg-overview https://golang.org/pkg/net/http/#pkg-overview). > or should I be already informed about including it as a developer? I guess you really should, whatever language/framework you're currently using. > what i have meant was mostly about the way an application is built with golang. Yes, clearly the confusion may be here, I took it as "the language is not opinionated", whereas you were in fact saying that the language and its standard library are not a universal web application toolkit/framework.