davej Posted August 21, 2013 Share Posted August 21, 2013 Who uses it and why? Link to comment Share on other sites More sharing options...
justsomeguy Posted August 21, 2013 Share Posted August 21, 2013 I don't know how common it is, but one appeal is that people can write client-side and server-side code in the same language and even reuse many of the functions. Link to comment Share on other sites More sharing options...
thescientist Posted August 21, 2013 Share Posted August 21, 2013 Since it is relatively new on the scene it probably hasn't been widely adopted/deplyoed yet, at least probably not on an enterprise level for production environments. Our company has started using it as part of our local development stack for things like routing (similar to using a PHP proxy for reaching our dev env) and dependency management. I think it's biggest appeal is that is a paradigm shift from how current web servers handle requests/responses; favoring an event-loop rather than a a queue. Link to comment Share on other sites More sharing options...
davej Posted August 21, 2013 Author Share Posted August 21, 2013 Well, what got me thinking about it are the various warnings about eval() being a "security risk." That makes no sense for the client, so I guess they must be talking about the server-side. Link to comment Share on other sites More sharing options...
justsomeguy Posted August 21, 2013 Share Posted August 21, 2013 Eval on the client is only a risk to your users if your site is compromised in another way. If an attacker can inject code that you eval, then that's a problem, but it's only a problem if the attacker can already inject code. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now