Go w/ templates is more an analog to JSP tech than JSF tech, I think that's the key differentiator. I'm guessing JSP is significantly faster and Go would be mor

Go w/ templates is more an analog to JSP tech than JSF tech, I think that's the key differentiator. I'm guessing JSP is significantly faster and Go would be more memory efficient, but I hardly doubt any of that matters at the scale these two would be used. JSF OTTH is a component framework and is much higher level than JSP|go/template. JSF performance probably falls below both JSP and Go templates. But, at a much lower cognitive load that both by an order of magnitude. For instance, to put a street map on a page with PrimeFaces, you simply type: <p:gm ::tab-space:: and let the autocomplete in your Java IDE fill in the rest of the characters to form: <p:gmap id="googleMap" apiKey="xyz" />. Ultimate it's a tradeoff between getting exact control over the HTML (which you often don't need) and developer productivity.