TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

What do you dislike about React Native?

110 点作者 daanavitch超过 6 年前

11 条评论

throwaway66666超过 6 年前
I will probably be heavily downvoted but here goes nothing. I have not used React Native yet, but I followed and was heavily invested in the &quot;write once deploy anywhere&quot; trend between 2009 - 2014.<p>From phonegap (before it became cordova), to Adobe Air with it&#x27;s bad performance and &quot;native extensions&quot;, to Appcelerator Titanium that put a nodejs server in your phone and even had Windows Phone 7 support, to cordova, to Haxe, to sencha and others. Appcelerator Titanium was the only ones that did real native for some cases like scrollviews, Haxe used custom C++ apis, the rest used webviews, and adobe air was basically flash emulated that ran like shit.<p>Write once deploy anywhere, meant write once, deploy somewhat anywhere, spend double the time to make that promise true. Kinda like having to do IE6 support in the past. I was deep in that madness up until mid-2014. At that point I decided to buy a macbook and give native development a try (obj-c for ios and java for android -- When I say native I mean real native and not React Native).<p>What a magical experience! Things that are tough to do in web even today, like real never-ending scroll lists, are a breeze in native with their reusable cells. Things like standard headers and modals, are already built in and a few lines away. And I actually prefer the touch event handlers on both ios and android to the web&#x27;s &quot;mouse&#x2F;touch&#x2F;PointerEvents&quot; ones.<p>I do not understand why web developers have such a knee jerk reaction to native development. ObjectiveC&#x2F;Swift and Java are actually easy to write. Tooling (especially for ios) is fantastic. In my experience, it is much faster to write UI interfaces in Objective C and Swift (I never use xcode&#x27;s UI builder) than html+JS. But the real joy is being able to harness the real power of your phone. I run some C++ algorithms on both ios and android (I guess C&#x2F;C++ is the original cross platform) that on android are faster than the built-in Java apis themselves! And of course, true multithreading!<p>But here we are, non-stop chasing the &quot;no! I want javascript in my frontend, and in my servers, and javascript in my ios apps and android too!&quot; dream.<p>Perhaps React Native accomplishes that. I hope it really does and solves that decade-long promise of &quot;write once deploy anywhere&quot;. I guess all what I &#x27;m trying to say is, don&#x27;t be afraid of native people! Web devs are willing to go through insane hoops and loops instead of just... giving the real thing a go. So weird.
评论 #18622018 未加载
评论 #18622408 未加载
评论 #18623270 未加载
评论 #18624643 未加载
评论 #18628119 未加载
评论 #18622151 未加载
评论 #18624438 未加载
评论 #18621786 未加载
评论 #18623859 未加载
评论 #18622025 未加载
JoeCortopassi超过 6 年前
Companies and teams don’t usually pick non-native solutions because they&#x27;re better tech. Non-native solutions are picked so that teams can be more efficient with their time&#x2F;resources. For some teams, that means delivering an app cheaper. For other teams, that means being able to spread resources thinner and stretch budgets. This doesn&#x27;t have to be a bad thing per se, it&#x27;s just a business decision.<p>As a former iOS engineer, I for one really enjoy React Native. But I feel like it&#x27;s focus is trying to maintain&#x2F;supersede native development, where it&#x27;s time and attention would be better served focusing on the efficiency of average developers on average tasks
评论 #18623731 未加载
pauliusj超过 6 年前
For me it feels like RN is still not ready for an enjoyable development experience (it feels more around alpha&#x2F;beta version), which maybe it is because the version is 0.57 or somewhere around that. The main problems I have with RN are:<p>* Cryptic error messages. Out of maybe hundreds of errors&#x2F;crashes I had while developing a medium sized app, only a few of them provided useful info about what&#x2F;where happened.<p>* Lot&#x27;s of outdated&#x2F;abandonware&#x2F;low-quality libs in the ecosystem. You really have to be careful when picking the dependencies.<p>* Fragile and complex builds. You&#x27;ll have to use dependencies to make anything more than a basic app (unless you want to DIY), so get ready for some &quot;fun&quot; when upgrading the project because not all of the dependencies will be upgraded at the same time, might also often have the APK&#x2F;IPA or development builds fail because of dependencies not properly installing or not playing nicely with one another.<p>* Lots of little stuff. For example, I had the ios simulator logs not work out of the box when launching with &quot;react-native log-ios&quot;, so had to use a third-party solution for that. Metro bundler sometimes just breaks. I still have a problem of the app randomly closing down after some time on iOS, which I did not look deeply into yet but will have to solve before release. Constant issues with nesting scroll views on android. Hard to predict cross-platform inconsistencies in layout behaviour in some places. Can&#x27;t name everything right now but they played on the nerves throughout the development.<p>I hope it gets better some day, but until then I&#x27;ll probably look for alternatives for my next project as I wasn&#x27;t very happy with RN.
评论 #18622869 未加载
评论 #18623129 未加载
pier25超过 6 年前
I tried RN in early 2016 but Android support and documentation were not great.<p>Honestly, I&#x27;ve always thought that RN (and similar approaches) is kinda a hack. Yes, it solves a problem of reducing developer time across platforms, but it introduces other more obscure problems. A JavaScript engine with it&#x27;s own set of problems giving orders through some bridge to the native part... I don&#x27;t know, it&#x27;s a lot of moving pieces.<p>I feel Flutter is so much more solid in this respect. The approach has been used countless times by game engines such as Unity, UE, etc. The part where Google has to replicate the UI elements of each platform is not amazing, but otherwise I feel it&#x27;s a much more solid approach than RN.
评论 #18623049 未加载
dep_b超过 6 年前
* Javascript<p>* NPM<p>* It&#x27;s still 0.59 or something and things are constantly breaking<p>* Because of that every piece of information older than 1 month should be distrusted<p>* App size<p>* It doesn&#x27;t play well when you try to gradually replace or add RN screens to an existing application.<p>* There are multiple ways to do the same thing<p>* It adds another layer on top of the iOS and Android builds
评论 #18621083 未加载
malvosenior超过 6 年前
You can develop native apps in languages that range from ok, to really good (Java -&gt; Swift). Javascript is a terrible language for many reasons (lack of a decent standard lib, weak typing, foot guns galore, psychotic build pipeline and tooling...). React Native encourages more JS development so I dislike it for that reason.
评论 #18630227 未加载
vmarsy超过 6 年前
it&#x27;d be cool if there was a simple way to create typescript react-native app, similar to create-react-native-app[1] without a dependency on Babel[2]<p>[1] <a href="https:&#x2F;&#x2F;facebook.github.io&#x2F;react-native&#x2F;blog&#x2F;2017&#x2F;03&#x2F;13&#x2F;introducing-create-react-native-app" rel="nofollow">https:&#x2F;&#x2F;facebook.github.io&#x2F;react-native&#x2F;blog&#x2F;2017&#x2F;03&#x2F;13&#x2F;intr...</a><p>[2] <a href="https:&#x2F;&#x2F;facebook.github.io&#x2F;react-native&#x2F;blog&#x2F;2018&#x2F;05&#x2F;07&#x2F;using-typescript-with-react-native" rel="nofollow">https:&#x2F;&#x2F;facebook.github.io&#x2F;react-native&#x2F;blog&#x2F;2018&#x2F;05&#x2F;07&#x2F;usin...</a>
debt超过 6 年前
It would be tight if we could purge from the web all posts and threads related to unsupported and outdated ReactNative versions.<p>It&#x27;s actually quite interesting to see the almost in real-time development of ReactNative through the lens of hobbled and broke-ass solutions to problems associated with deprecated RN versions posted on StackOverflow or Medium.
评论 #18620850 未加载
评论 #18620973 未加载
评论 #18620890 未加载
评论 #18620804 未加载
reverite超过 6 年前
A few friends and I have noticed that applications that are using React Native, even in the best of situations in optimizing, it still drains battery life faster (sometimes far faster) than something written in Java&#x2F;Kotlin or ObjC&#x2F;Swift.
评论 #18623457 未加载
评论 #18623446 未加载
shujito超过 6 年前
app bloat, the app size is too big for a simple example
alsothrownaway超过 6 年前
I think it&#x27;s constructive to point out that maybe the entire project, being a &quot;hack&quot; of sorts that tends to breed more hacks and more debt, ultimately isn&#x27;t useful or valuable. The idea is wonderful, but in practice I still have to maintain cross-platform code that has nothing to do with wireup, and honestly think everyone should seriously consider writing portable code and plugging it into truly native projects.<p>React Native multiplies the complexity of a project so much that IMHO it completely negates its own usefulness.