From efa34d53f82e2cbebe92fd7a21da13815c04ee8c Mon Sep 17 00:00:00 2001 From: Dave Yost Date: Fri, 21 Jun 2019 07:27:10 -0700 Subject: [PATCH] more about leveraging TypeScript TypeScript handles compatibility --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 36dee44..602b2b0 100644 --- a/README.md +++ b/README.md @@ -123,7 +123,7 @@ Because I am not happy with the JavaScript generated by current solutions. The best solutions currently generate a lot of code in an attempt to maintain all the finer points of .NET semantics. The philosophy of Netjs is that .NET and JavaScript's semanantics are *close enough* that idiomatic JavaScript can be generated from any .NET library. Sure we have to work around some of .NET's features, but the majority of code should be clean JavaScript. -Well, that's almost true - JavaScript's idioms don't exactly match .NET's. However, TypeScript's come a lot closer. For this reason, Netjs leverages the TypeScript compiler. This also performs a great "first unit test" on the generated code because the TypeScript compiler is very strict and is good at catching errors. +Well, that's almost true - JavaScript's idioms don't exactly match .NET's. However, TypeScript's come a lot closer. For this reason, Netjs leverages the TypeScript transpompiler. This also performs a great "first unit test" on the generated code because the TypeScript compiler is very strict and is good at catching errors. And the Typescript transpiler generates JavaScript that runs on older JavaScript interpreters. When I declare a class with properties in C#,