<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>stewx</author><text>Having spent a few months at work attempting to build an application in NativeScript, my advice to others is don&amp;#x27;t touch it with a ten-foot pole.&lt;p&gt;It is marketed as a holy grail for mobile development, but it is very, very immature. It should be considered an experimental technology.&lt;p&gt;Why do I say that? It has a severe lack of features and a high bug count.&lt;p&gt;It claims to support CSS but in fact it only supports about 10% of what CSS can do in the browser.&lt;p&gt;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&amp;#x27;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&amp;#x27;t allow you to write unit tests. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;NativeScript&amp;#x2F;nativescript-angular&amp;#x2F;issues&amp;#x2F;2122&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;NativeScript&amp;#x2F;nativescript-angular&amp;#x2F;issues&amp;#x2F;...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Why you should NOT use NativeScript</title><url>https://csimpi.medium.com/why-you-should-not-use-nativescript-76e1348a7cb4</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>natenthe</author><text>This post is on point. I spent a good amount of time working on multiple NativeScript apps (NS with Angular and NS with Vue) and can attest that the documentation is not good enough and that there are serious bugs that are pointed out and never fixed or addressed.&lt;p&gt;I will say that open-source is a good thing to do and that they are not solving an easy problem - developing native mobile apps with multiple JS frameworks like Angular and Vue. Good on them for the effort. On top of that, there is definitely a market need for an Angular &amp;#x2F; Vue &amp;#x2F; JS to native app library for people that don&amp;#x27;t want to use React-Native for whatever reason.&lt;p&gt;However, with that said...marketing their software as production ready, easy-to-use, and &lt;i&gt;working&lt;/i&gt; out of the box while it being the exact opposite is harmful to the companies and developers that sink serious time and effort into building with NS. There needs to be more awareness like this blog post about how people should stay away from NS because of the issues mentioned. That is not being negative - it is being ethical and doing the right thing for the companies and developers that would end up having broken apps and serious sunken costs into platform that doesn&amp;#x27;t live up to what it says it does.&lt;p&gt;I have many Github issues that were acknowledged as bugs but never addressed or fixed. I even offered a workaround that people are probably still using to this day because they never fixed certain bugs and docs. I haven&amp;#x27;t really interacted with the NS people too much besides on a few issues that weren&amp;#x27;t answered, so I can&amp;#x27;t comment on their attitude, but I can attest that everything else the OP is saying is true about NS not being a good solution.&lt;p&gt;NS isn&amp;#x27;t &lt;i&gt;soo&lt;/i&gt; terrible where nothing ever works. I believe the apps I worked on are still running in production. But, I&amp;#x27;ll put it this way - everyone learned from the experience that using NS is definitely not a good idea to use for developing mobile apps.</text><parent_chain></parent_chain></comment><story><title>Why you should NOT use NativeScript</title><url>https://csimpi.medium.com/why-you-should-not-use-nativescript-76e1348a7cb4</url></story>