3 ms·
Having spent a few months at work attempting to build an application in NativeScript, my advice to others is don't touch it with a ten-foot pole. It is markete
by stewx 6y ago
Having spent a few months at work attempting to build an application in NativeScript, my advice to others is don't touch it with a ten-foot pole.
It is marketed as a holy grail for mobile development, but it is very, very immature. It should be considered an experimental technology.
Why do I say that? It has a severe lack of features and a high bug count.
It claims to support CSS but in fact it only supports about 10% of what CSS can do in the browser.
It also has an insanely huge backlog of bugs, which you can see for yourself on GitHub. I filed a bug report for what is a fatal flaw IMO: you can't write unit tests against async code. The dev team acknowledged it is a problem and yet it has collected dust for a year. No serious business should use a tool that doesn't allow you to write unit tests. https://github.com/NativeScript/nativescript-angular/issues/2122 https://github.com/NativeScript/nativescript-angular/issues/...
- dvfjsdhgfv 6y agoThis were exactly my points when I considered using it a few months ago. Much less mature than the alternatives yet offering no selling point that would make it up for me for using alpha-quality software. If they announced it 10 years ago, I would have used it for toy projects just for fun, but these days I just want to build stuff that works, and if it has bugs, I prefer them to be mine.