>>I think we talked about Go a while ago. Just refreshed my memory by reading this: https://golang.org/doc/articles/wiki/#tmp_11
>>It seems to me that the Go architecture for web sites is essentially similar to that of ASP.NET MVC - i.e. pages are generated on the server.
>>I still prefer the Angular type approach where the only requirement on the server is to deliver static html and data.
>
>Saying Go's architecture for web sites is similar to ASP.Net MVC is not fair I think but I don't care on theory as well.

My point was fair - both depend on building HTML on the server. I'm not arguing that ASP.NET is better than GO (I can see advantages in the latter)

>All I was saying, if he would learn C# to do that, then learning Go is a better alternative. You can build web applications in Go much easier and faster (also perform much better, cross platform etc, too many advantages to list). I code in both and that is my perception.

Again you're comparing Go to ASP.NET. But, at the end of the day, if all a server has to do is serve up static HTML and some data that's about as cross-platform and performant as it gets.....