7 ms·

React Native 0.69

72 points by soheilpro 4y ago

wfrew 4y ago
TobyTheDog123 4y ago
joshxyz 4y ago
I wonder what it qualifies for them to release a 1.0. Or maybe it is just my fixated beliefs that 0.x are unstable and 1.x are stable.
- dstaley 4y ago
  Honestly I think they'll eventually drop the `0.` and just call it React Native 80. I can't imagine them ever referring to it as "React Native 1.1".
tadpol 4y ago
- radicalriddler 4y ago
  Everyday we get closer and closer to reddit level comments.
  - TobyTheDog123 4y ago
    I also hate levity and humor on my serious professional tech news feed
  - thomassmith65 4y ago
    I get the frustration but it's literally against the guidelines here (https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html) to make that complaint. It isn't true anyhow; the comments in question are disappearing nearly as quickly as people write them (because the community is flagging them).
atakari 4y ago
deleted 4y ago
[deleted]
account-5 4y ago
BossingAround 4y ago
How does react native compare to flutter nowadays? Is this still the framework for simple apps that need to be cross platform?
- RayVR 4y ago
  React native now has enough useful but abandoned projects to make it a minefield. Reading through the list of changes, I know of several projects which are unmaintained that I would have to scrap in order to upgrade. I don’t know much about flutter.
  - jrumbut 4y ago
    That was my experience with RN. The React ecosystem is nice but the RN specific libraries that come with native components have been nightmares. This includes libraries from major companies that were incomplete (as in didn't implement functionality that they claimed to have in the repository readme file), badly broken, and nearly no documentation. Once I realized how common this was, I just implemented my own native components when required. React Native itself was and is very good, good enough to make it worth using despite the minefield ecosystem.
- mhoad 4y ago
  I just saw a bunch of numbers last night that suggested Flutter had taken the title as more popular and had it beat fairly comprehensively in terms of developer experience and performance. I’m trying to find it now but not having a lot of luck as it was a random Twitter thread that was pulling in a bunch of things from various sources, so take it for what you will in the meantime. For what it’s worth as someone who has spent a bunch of time with Flutter at this point, none of that surprised me to hear, it’s actually a really pleasant experience, the tooling is amazing and unlike anything I had seen before as all of my experience was with web before. It’s underlying architecture feels really solid, also despite people talking a lot of trash about it, it turns out Dart is actually a really great language as a mix between C#, Java, Kotlin and JavaScript of sorts. I think every serious criticism I have seen levelled at both Dart and Flutter is also actively addressed on their roadmap so I also feel extremely good about the future direction of both projects. Like in short, probably the best thing I’ve discovered in a few years code wise, would recommend checking it out.
steve_mcdougall 4y ago
deleted 4y ago
[deleted]
syspec 4y ago
On this thread, there are bunch of comments which are just "Nice". I clicked on a few of the usernames, and while a couple are new, many have decent Karma accrued. I also tried to search for "React Native 'nice'" to see if anything came up on google. No luck. So is that a meme that i'm not aware of or something?
- Deukhoofd 4y ago
  It is yes. https://knowyourmeme.com/memes/69 https://knowyourmeme.com/memes/69
  - egeozcan 4y ago
    > Online, it (the number 69) has a reputation as "the sex number." People often joke about it by replying "nice" to posts that use the number 69 regardless of the context in which the number is used. Why would people keep doing it in HN, and some of those accounts aren't event that new...
    - jiikonen 4y ago
      Because it’s funny.
      - BurningPenguin 4y ago
        No fun allowed on HN
        egeozcan 4y ago
        Fun is definitely not disallowed, you can read the guidelines here: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html But it also says: > Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community. Which puts your comment in a grey area :) That said, nobody follows rules to the letter, and you can definitely find a lot of comments from me as well that don't follow them strictly, but here is a community and by spending time here, you can surely get a good gut feeling of what's allowed really and what not. Remember: Nobody is here to teach a lesson to anyone, and it can be said that most basically just want some thought put into the comments. Having a hundred replies that says "nice" therefore won't do great.
kajaktum 4y ago
I am not primarily a front end developer but I am always intrigued by React as a way to develop UI (Its significantly better than having a separate XML). Several things that bother me right now is while working on personal projects involving React: 1. Generating unique ID for debugging purposes. Currently, I simply use the project directory "component-user-settings-name". 2. React claims "As a React developer, you focus on what you want the user experience to look like, and React handles how to deliver that experience"[1] but this is not always true. JS have something like COW memory management and AFAIK, React already requires you to make a full clone for each render (if the object changes) so you _really_ want to avoid them if possible. So you actually do care what React does internally thus I wonder if the COW semantic can be made clearer. 3. You sometimes have to do object of arrays instead of array of objects when you have a short list of very complex objects. The fact that I have to care about this is unfortunate, as refactoring from one to the other is not always straightforward, especially when you need to consider if you changes will cause JS to make clones. I also wish React can be transpiled/compiled into a much lower level language with clearer performance characteristics. I think Slint UI is the closest that I can find. [1] https://reactjs.org/blog/2022/03/29/react-v18.html https://reactjs.org/blog/2022/03/29/react-v18.html
kkarimi 4y ago
What is the reason for not releasing a v1 after so many years?
- bartq 4y ago
  Probably psychological: major version change equals in people's minds to some marketing event/website announcement, developers/users meeting etc. Which is not how semver was designed. For this kind of event developers should reserve subname, like macOS Mojave, Monterey etc.
- wener 4y ago
  Checkout ZeroVer: 0-based Versioning https://0ver.org/ https://0ver.org/
  - Zababa 4y ago
    This sounds like the unofficial versioning scheme of most Rust libraries. That and 2 years old libraries that are at 18.3.5 or something.
  - bberrry 4y ago
    Is this a joke or did they just forget to provide a justification for _why_ 0ver should be used?
- jdthedisciple 4y ago
  you don't simply skip v0.69 ... hehe
deleted 4y ago
[deleted]
whateveracct 4y ago
BilalBudhani 4y ago
Coming from web I gave serious shot to React Native for quite sometime but I learned the hard way that it can go only so far in mobile app development. There will come a point in React Native development where you have to go under the hood to the native side of the operating system to deliver that last mile experience to your users.
- htormey 4y ago
  Care to give some specific examples?
  - saghul 4y ago
    Navigation for example. If you use react-navigation stack and native-stack may look very similar but have tons of hidden implications. If you are presenting a screen modally on iOS you cannot present a Modal component over it for example. This requires that you understand (or at least research) platform specific behavior. Even so, I’d take RN any day of the week.
  - deleted 4y ago
    [deleted]
- antihero 4y ago
  That’s kind of the point though? It means most of your time is spent rapidly developing in cross platform React, and only some of it doing platform specific stuff, as opposed to 100% off the time. This is a feature.
ponyous 4y ago
Is anyone in the wild using herems? I tried upgrading our app to hermes but not all our dependencies were ready yet (think you need turbo modules?)? What issues did you encounter? Not anything exciting for me in 0.69 :(
- paldepind2 4y ago
  I use Hermes and have had zero issues with it. I use quite a bunch of native libraries.
schr3da 4y ago
To me react native is the only real way to go if you are considering cross platform development besides using a webview and web stack for your UI. Reason is simple. React Native abstracts only platform away by exposing base components. If you really need something for a specific platform it is very easy to write a custom plugin - so you will need some platform knowledge. I have used flutter as well but must admit it feels not the way as I would like to have - especially the shader compilation if a component gets shown for the first time I feel annoying. So to me react native is best - but comes with its own pain points like updates... If you can afford it go pure native and try to write business logic in a shareable language e.g. Rust, C, C++, Kotlin native... and integrate the UI based on the platform. If thats not an option I recommend react native + if needed custom modules and try to not use too many third party libs.
- andreidd 4y ago
  You can do both: two years ago I was looking for the best solution to ship a cross platform app (Android + Windows) and I just couldn’t decide whether to go platform-based UI + a shared C++ core or React Native. I ended up using React Native + a shared C++ core exposed as a RN module. As long as the API surface is narrow (and it is for my use case) this turned out well and it still gives me the possibility to scrap RN at any given time for platform based UIs. Bonus: since most of my logic is C++, I am still able to ship the app using two RN versions: 0.59 for Windows 7 and 0.67 for Android
- 1ark 4y ago
  Xamarin is a good alternative if you don't want the overhead of JS runtime, without going all the way down to the metal as you mentioned. Shared code base. But you sacrifice a bit of productivity for performance and maintainability.
  - jurmous 4y ago
    In React Native they now use the Hermes engine which can have the JS code precompiled into byte code. https://reactnative.dev/docs/hermes#confirming-hermes-is-in-use https://reactnative.dev/docs/hermes#confirming-hermes-is-in-...
jordiburgos 4y ago
deleted 4y ago
[deleted]

72 points by soheilpro 4y ago

I wonder what it qualifies for them to release a 1.0. Or maybe it is just my fixated beliefs that 0.x are unstable and 1.x are stable.

dstaley 4y ago
Honestly I think they'll eventually drop the `0.` and just call it React Native 80. I can't imagine them ever referring to it as "React Native 1.1".

tadpol 4y ago

radicalriddler 4y ago
Everyday we get closer and closer to reddit level comments.
- TobyTheDog123 4y ago
  I also hate levity and humor on my serious professional tech news feed
- thomassmith65 4y ago
  I get the frustration but it's literally against the guidelines here (https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html) to make that complaint. It isn't true anyhow; the comments in question are disappearing nearly as quickly as people write them (because the community is flagging them).

atakari 4y ago

deleted 4y ago

[deleted]

account-5 4y ago

BossingAround 4y ago

How does react native compare to flutter nowadays? Is this still the framework for simple apps that need to be cross platform?

RayVR 4y ago
React native now has enough useful but abandoned projects to make it a minefield. Reading through the list of changes, I know of several projects which are unmaintained that I would have to scrap in order to upgrade. I don’t know much about flutter.
- jrumbut 4y ago
  That was my experience with RN. The React ecosystem is nice but the RN specific libraries that come with native components have been nightmares. This includes libraries from major companies that were incomplete (as in didn't implement functionality that they claimed to have in the repository readme file), badly broken, and nearly no documentation. Once I realized how common this was, I just implemented my own native components when required. React Native itself was and is very good, good enough to make it worth using despite the minefield ecosystem.
mhoad 4y ago
I just saw a bunch of numbers last night that suggested Flutter had taken the title as more popular and had it beat fairly comprehensively in terms of developer experience and performance. I’m trying to find it now but not having a lot of luck as it was a random Twitter thread that was pulling in a bunch of things from various sources, so take it for what you will in the meantime. For what it’s worth as someone who has spent a bunch of time with Flutter at this point, none of that surprised me to hear, it’s actually a really pleasant experience, the tooling is amazing and unlike anything I had seen before as all of my experience was with web before. It’s underlying architecture feels really solid, also despite people talking a lot of trash about it, it turns out Dart is actually a really great language as a mix between C#, Java, Kotlin and JavaScript of sorts. I think every serious criticism I have seen levelled at both Dart and Flutter is also actively addressed on their roadmap so I also feel extremely good about the future direction of both projects. Like in short, probably the best thing I’ve discovered in a few years code wise, would recommend checking it out.

steve_mcdougall 4y ago

deleted 4y ago

[deleted]

syspec 4y ago

On this thread, there are bunch of comments which are just "Nice". I clicked on a few of the usernames, and while a couple are new, many have decent Karma accrued. I also tried to search for "React Native 'nice'" to see if anything came up on google. No luck. So is that a meme that i'm not aware of or something?

Deukhoofd 4y ago
It is yes. https://knowyourmeme.com/memes/69 https://knowyourmeme.com/memes/69
- egeozcan 4y ago
  > Online, it (the number 69) has a reputation as "the sex number." People often joke about it by replying "nice" to posts that use the number 69 regardless of the context in which the number is used. Why would people keep doing it in HN, and some of those accounts aren't event that new...
  - jiikonen 4y ago
    Because it’s funny.
    - BurningPenguin 4y ago
      No fun allowed on HN
      - egeozcan 4y ago
        Fun is definitely not disallowed, you can read the guidelines here: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html But it also says: > Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community. Which puts your comment in a grey area :) That said, nobody follows rules to the letter, and you can definitely find a lot of comments from me as well that don't follow them strictly, but here is a community and by spending time here, you can surely get a good gut feeling of what's allowed really and what not. Remember: Nobody is here to teach a lesson to anyone, and it can be said that most basically just want some thought put into the comments. Having a hundred replies that says "nice" therefore won't do great.

kajaktum 4y ago

I am not primarily a front end developer but I am always intrigued by React as a way to develop UI (Its significantly better than having a separate XML). Several things that bother me right now is while working on personal projects involving React: 1. Generating unique ID for debugging purposes. Currently, I simply use the project directory "component-user-settings-name". 2. React claims "As a React developer, you focus on what you want the user experience to look like, and React handles how to deliver that experience"[1] but this is not always true. JS have something like COW memory management and AFAIK, React already requires you to make a full clone for each render (if the object changes) so you _really_ want to avoid them if possible. So you actually do care what React does internally thus I wonder if the COW semantic can be made clearer. 3. You sometimes have to do object of arrays instead of array of objects when you have a short list of very complex objects. The fact that I have to care about this is unfortunate, as refactoring from one to the other is not always straightforward, especially when you need to consider if you changes will cause JS to make clones. I also wish React can be transpiled/compiled into a much lower level language with clearer performance characteristics. I think Slint UI is the closest that I can find. [1] https://reactjs.org/blog/2022/03/29/react-v18.html https://reactjs.org/blog/2022/03/29/react-v18.html

kkarimi 4y ago

What is the reason for not releasing a v1 after so many years?

bartq 4y ago
Probably psychological: major version change equals in people's minds to some marketing event/website announcement, developers/users meeting etc. Which is not how semver was designed. For this kind of event developers should reserve subname, like macOS Mojave, Monterey etc.
wener 4y ago
Checkout ZeroVer: 0-based Versioning https://0ver.org/ https://0ver.org/
- Zababa 4y ago
  This sounds like the unofficial versioning scheme of most Rust libraries. That and 2 years old libraries that are at 18.3.5 or something.
- bberrry 4y ago
  Is this a joke or did they just forget to provide a justification for _why_ 0ver should be used?
jdthedisciple 4y ago
you don't simply skip v0.69 ... hehe

deleted 4y ago

[deleted]

whateveracct 4y ago

BilalBudhani 4y ago

Coming from web I gave serious shot to React Native for quite sometime but I learned the hard way that it can go only so far in mobile app development. There will come a point in React Native development where you have to go under the hood to the native side of the operating system to deliver that last mile experience to your users.

htormey 4y ago
Care to give some specific examples?
- saghul 4y ago
  Navigation for example. If you use react-navigation stack and native-stack may look very similar but have tons of hidden implications. If you are presenting a screen modally on iOS you cannot present a Modal component over it for example. This requires that you understand (or at least research) platform specific behavior. Even so, I’d take RN any day of the week.
- deleted 4y ago
  [deleted]
antihero 4y ago
That’s kind of the point though? It means most of your time is spent rapidly developing in cross platform React, and only some of it doing platform specific stuff, as opposed to 100% off the time. This is a feature.

ponyous 4y ago

Is anyone in the wild using herems? I tried upgrading our app to hermes but not all our dependencies were ready yet (think you need turbo modules?)? What issues did you encounter? Not anything exciting for me in 0.69 :(

paldepind2 4y ago
I use Hermes and have had zero issues with it. I use quite a bunch of native libraries.

schr3da 4y ago

To me react native is the only real way to go if you are considering cross platform development besides using a webview and web stack for your UI. Reason is simple. React Native abstracts only platform away by exposing base components. If you really need something for a specific platform it is very easy to write a custom plugin - so you will need some platform knowledge. I have used flutter as well but must admit it feels not the way as I would like to have - especially the shader compilation if a component gets shown for the first time I feel annoying. So to me react native is best - but comes with its own pain points like updates... If you can afford it go pure native and try to write business logic in a shareable language e.g. Rust, C, C++, Kotlin native... and integrate the UI based on the platform. If thats not an option I recommend react native + if needed custom modules and try to not use too many third party libs.

andreidd 4y ago
You can do both: two years ago I was looking for the best solution to ship a cross platform app (Android + Windows) and I just couldn’t decide whether to go platform-based UI + a shared C++ core or React Native. I ended up using React Native + a shared C++ core exposed as a RN module. As long as the API surface is narrow (and it is for my use case) this turned out well and it still gives me the possibility to scrap RN at any given time for platform based UIs. Bonus: since most of my logic is C++, I am still able to ship the app using two RN versions: 0.59 for Windows 7 and 0.67 for Android
1ark 4y ago
Xamarin is a good alternative if you don't want the overhead of JS runtime, without going all the way down to the metal as you mentioned. Shared code base. But you sacrifice a bit of productivity for performance and maintainability.
- jurmous 4y ago
  In React Native they now use the Hermes engine which can have the JS code precompiled into byte code. https://reactnative.dev/docs/hermes#confirming-hermes-is-in-use https://reactnative.dev/docs/hermes#confirming-hermes-is-in-...

jordiburgos 4y ago

deleted 4y ago

[deleted]