TypeScript vs GopherJS?

Question

JavaScript

Goodnight!
I thought about rewriting some of my libraries to typed JS sugar, now I'm faced with a choice:
TypeScript :
+ Angular 2
+ Serious guys use
+- `C` like
- Microsoft
GopherJS :
+ `Go` like
+ Possibility to pull up GO
- No really big projects on It
Both options are statically typed (as I understand it), which is very nice. Does anyone use GopherJS in production? And which option is better?

Answer 1

TypeScript is ES6 / ES7 stage1, tobish is the same babel, but you can still write information about types in detail from above, which improves the quality of static analysis (needed on large-scale projects, for example, for angular2 code). Well, yes, the fact that Microsoft saws it is not at all a minus. This is your stereotypical thinking.
gopherjs is a go to javascript translator and nothing more. Actually, because of this, we get the need to have bindings for each sneeze. my IMHO - it's more suitable for server side development.