Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why you should NOT use NativeScript

csimpi.medium.com

Post reply on HN
Print view View original

11–20 of 81 posts

Re: Why you should NOT use NativeScript

#11

Post by reggieband »

I can't comment on NativeScript as a technology. However, I would like to comment on the issue of his treatment in support channels.

He surrounded in quotes: "We are working on NS for 6 years, how dare you tell something is wrong?" and that seems suspiciously like a paraphrase on his part. I doubt it is a direct quote but rather a way the author wants to describe how he felt over the course of several exchanges.

One of the other supposed quotes, "You are too negative, I can’t help", is a bit more telling.

His other criticisms aside, I actually have no problem with open source support channels (or any support channels really) excluding toxic negativity. Some people seem to assume that complaining is the same as contributing. If the only thing you bring to the table are your complaints then don't be surprised if you get excluded.

Re: Why you should NOT use NativeScript

#12

Post by mkrishnan »

biggest advantage of flutter is the amount of time/energy spent in marketing flutter itself. dart is given up by google engineers long time ago. There were time where small amount of ads front end written in angular dart (like 10 pages across 4 applications) and those pages replaced with angular/typescript.

Probably you should go with java/kotlin instead of flutter/dart.

Re: Why you should NOT use NativeScript

#13

Post by pjmlp »

JamesSwift wrote: post #8
isaiahg wrote: post #7

Earlier quoted context omitted.

The message I'm getting from Google is that flutter is the future and will get more support eventually. You can also see it in their fuchsia os which is heavily focused on the ecosystem.

There is absolutely no way flutter unseats java/kotlin unless it abandons dart and adopts kotlin as its language. Its much more likely that flutter gets absorbed in some way by the android ecosystem.

Jetpack Compose was definitely a counter attack from Android team, with Ads being a big Flutter sponsor and the only reason Dart did not die when Chrome withdraw their support.

So if Ads, Pay and Search keep their support, Dart and Flutter are here to stay.

Re: Why you should NOT use NativeScript

#14

Post by chairhairair »

JamesSwift wrote: post #8
isaiahg wrote: post #7

Earlier quoted context omitted.

The message I'm getting from Google is that flutter is the future and will get more support eventually. You can also see it in their fuchsia os which is heavily focused on the ecosystem.

There is absolutely no way flutter unseats java/kotlin unless it abandons dart and adopts kotlin as its language. Its much more likely that flutter gets absorbed in some way by the android ecosystem.

I don't see how it would make any sense whatsoever for Flutter to be "absorbed" by Android, it is entirely independent.

Also, I'd be curious to hear what major advantages Kotlin would have for Flutter. The Flutter team has commented heavily on Dart's useful properties for Flutter's goals (small comment here, there are well written full articles as well: flutter.dev/docs/resources/faq#why-did-flutter-choose-to-use-dart).

The internal investment in Flutter is well beyond the average tech project at Google. I don't expect it to be abandoned any time soon.

Re: Why you should NOT use NativeScript

#15

Post by chairhairair »

mkrishnan wrote: post #12

biggest advantage of flutter is the amount of time/energy spent in marketing flutter itself. dart is given up by google engineers long time ago. There were time where small amount of ads front end written in angular dart (like 10 pages across 4 applications) and those pages replaced with angular/typescript. Probably you should go with java/kotlin instead of flutter/dart.

This is simply false. Dart/Flutter is very actively being used at Google by dozens of teams.

Re: Why you should NOT use NativeScript

#16

Post by dvfjsdhgfv »

stewx wrote: post #6

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…

This 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.

Re: Why you should NOT use NativeScript

#17

Post by okareaman »

mkrishnan wrote: post #12

biggest advantage of flutter is the amount of time/energy spent in marketing flutter itself. dart is given up by google engineers long time ago. There were time where small amount of ads front end written in angular dart (like 10 pages across 4 applications) and those pages replaced with angular/typescript. Probably you should go with java/kotlin instead of flutter/dart.

> dart is given up by google engineers long time ago

2013 called. It wants it's opinion back.

Re: Why you should NOT use NativeScript

#18

Post by michaelpb »

reggieband wrote: post #11

I can't comment on NativeScript as a technology. However, I would like to comment on the issue of his treatment in support channels. He surrounded in quotes: "We are working on NS for 6 years, how dare you tell something is wrong?" and that seems suspiciously like a paraphrase on his part. I doubt it is a direct quote but rather a way the author wants to describe how he felt over the course of several exchanges. One…

IMHO the most important thing that a framework can have is complete documentation and SLOW, deliberate release cycles, while this sounds like it's the opposite on both counts. Anyone can make a framework, the real value is in the documentation and release cycle.

That said, I got the exact same impression from his paraphrased statements. His paraphrases did seem revealing, like he had approached this with a bad and demanding attitude, and it went about as well as you'd expect. So, maybe room for improvement on all sides lol

Re: Why you should NOT use NativeScript

#19

Post by coldtea »

isaiahg wrote: post #7
mouldysammich wrote: post #2

> We are about to rebuild our Android app in Flutter from scratch now… Why not use Java/Kotlin if its just on android? Flutter has its advantages sure, but from my experience developing with flutter is the apps end up a bit slower than native, and often you end up interacting with the Java ecosystem on android anyway so the experience doesn't end up being that much better.

The message I'm getting from Google is that flutter is the future and will get more support eventually. You can also see it in their fuchsia os which is heavily focused on the ecosystem.

>The message I'm getting from Google is that flutter is the future and will get more support eventually.

Google has said the same thing for tons of things, and then stop caring for them and supporting them.

Including Dart as a JS alternative, the very same technology now relegated to Flutter backend.

Re: Why you should NOT use NativeScript

#20

Post by aaronbrethorst »

2021: Why you should NOT use NativeScript

It’s been two years since our company decided we’ll pick NativeScript to create and maintain our Android App. This was the biggest mistake our rapidly growing company made in the last 4 years. We are about to rebuild our Android app in Flutter from scratch now…

2023: Why you should NOT use Flutter

It’s been two years since our company decided we’ll pick Flutter to create and maintain our Android App. This was the second-biggest mistake our rapidly growing company made in the last 6 years. We are about to rebuild our Android app in Kotlin from scratch now…

Post reply on HN