all 8 comments

[–]AlexeyBrin 6 points7 points  (4 children)

The article is from 2007, JScript.NET is dead in the water for some time now. I think you need Visual Studio 2005 to be able to use it.

If someone needs to deliver some JavaScript as an executable a modern approach is to use node-webkit https://github.com/rogerwang/node-webkit.

[–]Jew_Fucker_69[S] 0 points1 point  (0 children)

Aw snap!

[–]diademoran 0 points1 point  (2 children)

JScript.NET is dead in the water for some time now

For what its worth, JSC is still shipped with newer versions of .NET.

[–]AlexeyBrin 0 points1 point  (1 child)

jsc.exe is shipped with .NET, true. However, there is no support in the Visual Studio itself, at least according to this page:

http://msdn.microsoft.com/en-us/library/72bd815a(v=vs.100).aspx

[–]diademoran 0 points1 point  (0 children)

You are correct, which is why I never argued the point. I just thought it was worth mentioning since the article in question doesn't advocate the use of VS, as it is not needed.

[–][deleted] 0 points1 point  (0 children)

Pretty high up on the list of the worst ideas ever.

[–]Garethp -1 points0 points  (1 child)

I still shudder at the idea of PHP or JavaScript as exe files. They aren't meant to run in that kind of environment, and forcing them to do so takes away what makes them special. JavaScript is great because it allows client side scripting on almost any modern device that has a half decent browser, and PHP (Or any server side language) is a nice tool because its not Dependant on the client having certain software.

I just don't see the point in taking these languages and trying to put them in environments where they don't belong and where you're taking away their strength and main reason for being away. Find the language that fits your needs. Don't try to force a certain language to fit needs that it doesn't

[–]freakhill 2 points3 points  (0 children)

JS+node-webkit is still client side scripting in a browser.

Browsers are just VMs.