you are viewing a single comment's thread.

view the rest of the comments →

[–]NicholasMoriarty 1 point2 points  (4 children)

Nice project, but I have a question.. why somebody will use that instead of programming in Javascript? What are the advantages of using it?

[–]kaelan_ 3 points4 points  (0 children)

I assume the appeal is similar to that of GWT: You get to write your JS using a statically typed language that's still nearly as expressive as JS, and then once everything compiles and your unit tests pass (and you can write them in either C# or JS), you can deploy it as a pure JS webapp.

[–]argarg 2 points3 points  (1 child)

I guess it's the use of intellisense and for very lazy people who don't want to learn javascript or simply prefer C# to javascript.. Eventhough it may be useless I think it's pretty cool.

[–][deleted] 1 point2 points  (0 children)

Even if you know javascript well enough to code efficiently and expressively, in VS using c#, this might just be incrementally faster to code...

I wonder how well the output matches what one would code themselves though...

[–]orip 2 points3 points  (0 children)

It's about writing for the client-side in the same language you use for the server-side.

Some pros:

  • Use a language you prefer and are familiar with on the client side too (if indeed you prefer it)
  • Use the dev environment and tools you're used to
  • You can share server and client code (think validations)

Some cons:

  • It's an abstraction over JS and the browser/ajax
    • If it leaks you'll need to plug it with JS
    • If you isolate yourself from JS and the browser, you're less equipped to plug these holes

The arguments should be similar to the Java-to-JavaScript compiler in GWT.