NativeScript vs TypeScript: What are the differences?
NativeScript and TypeScript are primarily classified as "Cross-Platform Mobile Development" and "Templating Languages & Extensions" tools respectively.
NativeScript and TypeScript are both open source tools. It seems that TypeScript with 51.1K GitHub stars and 7.06K forks on GitHub has more adoption than NativeScript with 17.2K GitHub stars and 1.27K GitHub forks.
According to the StackShare community, TypeScript has a broader approval, being mentioned in 982 company stacks & 1447 developers stacks; compared to NativeScript, which is listed in 9 company stacks and 26 developer stacks.
What is NativeScript?
What is TypeScript?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using NativeScript?
What are the cons of using TypeScript?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
So, i am preparing to adopt NativeScript.
For years my hybrid projects used Apache Cordova.
"Let's avoid to maintain two teams and double the deliver velocity".
It was good for a few years, we had those september issues, (i.e. apple broke some backward compatibility) , but for the last years, things seems to be losing the grip faster.
Last breaking changes, for instance, seems to have a workaround, however that growing feeling that simple things can not rely on so fragile webviews keeps growing faster and faster.
I've tested nativescript not only on it's "helloworld", but also on how do they respond on issues.
I got tweed support. I opened an github issue and got answers on less than 10 hours (yes i did it on another timezone and very close to a weekend). I saw the faulty docs get corrected in two days.
The bad news is i only can adopt nativescript on newer projects, since there is no budget to revamp the current solutions.
The good news is i can keep coding on Vue.js , without vou router, but that's ok. I've already exchanged vanilla html for real native app with background magic enabled, the router can be easily reproduced.
Choosing to add TypeScript has given us one more layer to rely on to help enforce code quality, good standards, and best practices within our engineering organization. One of the biggest benefits for us as an engineering team has been how well our IDEs and editors (e.g., Visual Studio Code ) integrate with and understand TypeScript . This allows developers to catch many more errors at development time instead of relying on run time. The end result is safer (from a type perspective) code and a more efficient coding experience that helps to catch and remove errors with less developer effort.
I use TypeScript for Web Applications and for both frontend and backend because it has a lot of tooling around it and they really got the types and type safety right. Flow (JS) on the other hand lacks tooling and most of the times I scramble to find the right way of building my contracts in which TypeScript is very intuitive and natural. Additionally TypeScript is very similar to Java so your backend engineers and full stack engineers can work with it without much of context switch.
The only time I think Flow shines is (based on probably my outdated knowledge) Flow is/was the only option if you want/wanted to build a React Native application mainly because React Native transpiler at the time I was working with it would only work with flow.