Geek Answers Handbook

TypeScript VS ScriptSharp - What are the trade-offs?

I am going to create a large-scale Javascript application, and I want to build it in a more structured way.
JQuery will be used for css effects.
Server side will be in C #.
Can you share your knowledge and experience which is better?

  • Which one is richer?
  • Which is better documented?
  • Is a script type really a strong type?

Also, in the long run, ScriptSharp is a one-man show (as I understand it), and Typescript was created by Microsoft.
Thanks

+8
typescript script #
source share
4 answers

Which one is richer?

Neither one nor the other - compiled JavaScript makes all JavaScript available.

Which is better documented?

The documentation is probably not the right question. Who has more info / a strong community to help you when you get stuck? There are currently 141 ScriptSharp questions (with 48 followers) in questions and 623 TypeScript (with 328 followers).

TypeScript has a very clear language specification . I was looking for ScriptSharp documentation - someone needs to point out where it is ... I assume there is a subset of C # that you can use, and I would be interested to know what that subset is.

Is TypeScript Really Strongly Typed?

TypeScript is statically typed. It will check types at compile time (and the IDE will check development time). Errors will be generated for type violations, although you can also choose dynamic typing if you want.

Which should i use?

If you cannot think about writing code in anything other than C #, you should use ScriptSharp. In all other cases, I recommend TypeScript. Understanding JavaScript is useful, given how the language is so ubiquitous and TypeScript gives you quick access to ECMAScript 6 language features, so if you decide to use and use pure JavaScript, your TypeScript coding experience will be more valuable.

I am biased, in some way. I like TypeScript so much that I wrote a book on it. However, this project was preceded by TypeScript enthusiasm (not Dart, CoffeeScript, ScriptSharp).

+16
source share

ScriptSharp is under constant development, although this is a one-man show. We have been using ScriptSharp for a large-scale web application for about 3 years, and it serves us well. The ability to write code in C # helped us move fast, and we had less training costs.

ScriptSharp has a clear flaw that there are many changes to the release of new versions in some versions. But we like it so much that we are ready to accept the change and make the corresponding changes.

If you have a dedicated infrastructure team to handle such architectural changes, you can use them to keep up with ScriptSharp and write wrappers for javascript libraries, I highly recommend ScriptSharp based on our experience. Please rate the simple prototype as before you decide which technology to go with. You can also try Sharpkit for an interesting alternative. Link-> http://sharpkit.net/

+7
source share

I also study this, and from my research it turned out that Microsoft used Script # to create an interface for all its large web applications, such as Office Web Apps, Hotmail, Office 365, SharePoint 2013 and they use older versions than the latest version of Script #, because people say that it is stable enough as it is. The problem is that Microsoft seems to be holding this performance tool away from us by not releasing the Script # definition files (import libraries) to the public for things like SharePoint, CRM, and Office, so it seems like most people are moving to TypeScript instead . However, I tend to use Script # and build the definitions that I need when I need them.

Literature:

http://weblogs.asp.net/soever/archive/2009/10/20/sharepoint-2010-client-side-javascript-object-model-library-written-in-script.aspx

Getting started: HTTP --- scriptsharpcontrib.codeplex.com/wikipage?title=Getting%20started%20with%20ScriptSharp

Oh, and there is a CRM definition for Codeplex, but I'm not in the link :)

+2
source share

If you are a .net developer, then definitely you should at least check script #. Yes, this is a one person show. Yes, it's not as advertised as TypeScript, but can many developers compete with the MS logo?

I have hands-on experience with script # but not with TypeScript. And the only reason you don’t want to touch it later is because the script # is applicable to people already familiar with C # + JS, and TypeScript is a completely new story and a new value for your project.

+1
source share

More articles:


All Articles