>The cool part is the "what" which is bridging the gap between the client and the server. This is what loses me- how is that cool or good? I would much rather

>The cool part is the "what" which is bridging the gap between the client and the server. This is what loses me- how is that cool or good? I would much rather write a static html/css/angular frontend and have it talk to a Go webservice on my server. I want to use the best language for the client and server side, why do I care if they are the same? I want them to be basically completely independent apps where I could replace one or the other with a new implementation.