4 ms·

With the issues I've had with React Native, I'm keeping my eye on Flutter, great dev experience backed by a well resourced team, hope to see its ecosystem catch

by mythz 8y ago

With the issues I've had with React Native, I'm keeping my eye on Flutter, great dev experience backed by a well resourced team, hope to see its ecosystem catch up. A couple of projects to watch out for: [1]: https://feather-apps.com/ https://feather-apps.com/ [2]: https://github.com/google/flutter-desktop-embedding https://github.com/google/flutter-desktop-embedding

rglover 8y ago
Curious, what are some of the issues you've had with React Native? Any big pitfalls to watch out for?
- village-idiot 8y ago
  Me too. I’ve been having a good experience with it so far.
- mythz 8y ago
  All experiences I've had with submitting issues with repro's were all closed, basically they've closed 100's of issues indiscriminately without any attempt to investigate or resolve them. I also believe Flutter's Skia approach is superior to React Native's [1]. [1] https://news.ycombinator.com/item?id=14433292 https://news.ycombinator.com/item?id=14433292
  - resters 8y ago
    There's one guy on the team who aggressively closes issues. It's extremely irritating to read an issue and see that progress was being made only to have that guy make a terse comment and close the issue for no apparent reason. Each of those issues likely wasted hours, days or weeks of time for many, many people.
- tspike 8y ago
  Just a few: - As another commenter mentioned, they ignore and close legitimate issues on a regular basis - Breaking changes are a way of life and extremely frequent - They ignore native warnings: our project had zero before introducing RN, now has hundreds - Navigation is a mess - Integration with existing native apps works for tiny features but falls apart in larger teams - Debugging issues that cross the JS <> Native boundary is a nightmare - Keeping pace with native updates is made much more difficult by the API churn- want to update to Xcode 10? First you have to update RN, which will break all your features - Poor maintenance of views meant to mimic native views - If you have a hybrid native/RN app, instead of reducing the platforms you have to support from 2 to 1, you've effectively increased it from 2 to 3
  - resters 8y ago
    I agree with some of these. It's really annoying that Facebook can't figure out how to hire a dozen or so talented developers to focus on the open source side of react and try to minimize the number of warts that people in the community end up having to deal with. While React Native is open source, Facebook does not prioritize needs that are outside of its core use cases. So many frustrating aspects of RN go unfixed by FB, and issues and PRs about them get ignored by the arrogant guy who closes issues without any explanation. Not sure how he thinks he's helping anyone by doing that.
    - nathan_f77 8y ago
      > It's really annoying that Facebook can't figure out how to hire a dozen or so talented developers to focus on the open source side of react Now that I think about it, I think I would actually enjoy being employed to help maintain the React Native project. I really had a lot of fun building a React Native app, but there were so many issues that didn't get any attention. It would be quite fun to spend all day helping people with issues, fixing bugs, writing tests, and merging PRs. That probably sounds like a terrible job to some other developers, but I really enjoy it, and it would be great to get paid for it.
rickdg 8y ago
Google project dependant on another Google project. Which one will go puff first after the people involved get their promotion, Dart or Flutter?
- UlisesAC4 8y ago
  That is my biggest grip, Google is known to do great experiments and then closing them. Better wait to more info and maturity.
dreamer_soul 8y ago
What issues did you encounter with react native? I was going to start a project with it soon but can't decide to be honest
solarkraft 8y ago
Desktop compatibility is very important for Flutter adoption in my eyes. Even if only for rapid development, it is of tremendous value. Web runnability is quasi standard nowadays, too. Even if it's only for previews.

by mythz 8y ago

rglover 8y ago

Curious, what are some of the issues you've had with React Native? Any big pitfalls to watch out for?

village-idiot 8y ago
Me too. I’ve been having a good experience with it so far.
mythz 8y ago
All experiences I've had with submitting issues with repro's were all closed, basically they've closed 100's of issues indiscriminately without any attempt to investigate or resolve them. I also believe Flutter's Skia approach is superior to React Native's [1]. [1] https://news.ycombinator.com/item?id=14433292 https://news.ycombinator.com/item?id=14433292
- resters 8y ago
  There's one guy on the team who aggressively closes issues. It's extremely irritating to read an issue and see that progress was being made only to have that guy make a terse comment and close the issue for no apparent reason. Each of those issues likely wasted hours, days or weeks of time for many, many people.
tspike 8y ago
Just a few: - As another commenter mentioned, they ignore and close legitimate issues on a regular basis - Breaking changes are a way of life and extremely frequent - They ignore native warnings: our project had zero before introducing RN, now has hundreds - Navigation is a mess - Integration with existing native apps works for tiny features but falls apart in larger teams - Debugging issues that cross the JS <> Native boundary is a nightmare - Keeping pace with native updates is made much more difficult by the API churn- want to update to Xcode 10? First you have to update RN, which will break all your features - Poor maintenance of views meant to mimic native views - If you have a hybrid native/RN app, instead of reducing the platforms you have to support from 2 to 1, you've effectively increased it from 2 to 3
- resters 8y ago
  I agree with some of these. It's really annoying that Facebook can't figure out how to hire a dozen or so talented developers to focus on the open source side of react and try to minimize the number of warts that people in the community end up having to deal with. While React Native is open source, Facebook does not prioritize needs that are outside of its core use cases. So many frustrating aspects of RN go unfixed by FB, and issues and PRs about them get ignored by the arrogant guy who closes issues without any explanation. Not sure how he thinks he's helping anyone by doing that.
  - nathan_f77 8y ago
    > It's really annoying that Facebook can't figure out how to hire a dozen or so talented developers to focus on the open source side of react Now that I think about it, I think I would actually enjoy being employed to help maintain the React Native project. I really had a lot of fun building a React Native app, but there were so many issues that didn't get any attention. It would be quite fun to spend all day helping people with issues, fixing bugs, writing tests, and merging PRs. That probably sounds like a terrible job to some other developers, but I really enjoy it, and it would be great to get paid for it.

rickdg 8y ago

Google project dependant on another Google project. Which one will go puff first after the people involved get their promotion, Dart or Flutter?

UlisesAC4 8y ago
That is my biggest grip, Google is known to do great experiments and then closing them. Better wait to more info and maturity.

dreamer_soul 8y ago

What issues did you encounter with react native? I was going to start a project with it soon but can't decide to be honest

solarkraft 8y ago

Desktop compatibility is very important for Flutter adoption in my eyes. Even if only for rapid development, it is of tremendous value. Web runnability is quasi standard nowadays, too. Even if it's only for previews.