I'd say it's even more than "a bit silly" because as one can see Vaadin, which is based on GWT, is not that insecure. It seems to me like the author just entirely omitted the fact that - of course - one can apply all security mechanisms current containers provide on the server side with GWT as well! Just look at what is written in the "evaluation" of Vaadin: "...by declaring security constraints in the deployment descriptor...". AFAIK, this has nothing to do with the applied (front end) framework.
2013/11/6 salk31 <[email protected]> > > http://zeroturnaround.com/rebellabs/the-2014-decision-makers-guide-to-java-web-frameworks/3/ > > Apparently GWT is insecure because it uses JavaScript. Am I reading this > wrong or is it a bit silly? > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
