bacro

The useValidation hook needs to add data to the dependency list of its useEffect or else it will run on each render unnecessarily.

Do you mind me asking what diet your grandfather was following?

My father died last year and he had a very bad case of Parkinson's. The diet does fit with the explanation to Parkinson's, although there is also sleep apnea that might have been an even bigger contributor to his Parkinson's development.

Start Using Hermes link is broken

It was 1985. In 1986 Keke Rosberg replaced him at Mclaren.

When React Native's fabric rearchitecture is available you will see much better performance. The thing that hurts performance today is that damn bridge communication between javascript and native that will be severely improved in fabric.

Agreed, that's the same thing I feel now that I am experienced in both types of languages (statically and dynamic typed). I am way faster when using dynamic typed languages.

Anything with windows is disqualified? To me is the other way around, anything with mac os x is disqualified, immediatelly with no mercy :)

I have developed in many static typed languages like C# and Java in my career but now I am being converted to web and mobile development so I know the advantages and disadvantages of a static type system. In my experience, I am much more productive in a dynamic instead of a static type system when implementing frontends. For you to have an idea, this react native project I developed alone was sold to the client to be implemented in 3 months. The catch was I didn't have any experience in mobile development and I was still developing another web project. So I had to learn react native, ios and android development as fast as possible to do a medium-sized app. Having more friction using typescript for me was a killer.

But for a backend I would certainly have used static types as it's way more critical.

I was investigating typescript to use in a react native project and while checking some of the definitions contained in a package in Visual Studio Code (I believe it was react-navigation) the way they were presented was so confusing that I aborted immediately going with typescript. It was a function that returned a function that accepted as a parameter another function and the extra syntax was really taxing to my brain to fully understand what the function was all about. When I removed the extra syntax it was way clearer for me to understand it. Sometimes, pure javascript with a good variable naming is better. Sure, I could use some of static type checking to avoid some bugs but there weren't many bugs that I remember when I was doing the app so I think it didn't impact me too much. Also I am a solo developer in my company, I don't work in a team so it's not a big problem here.

>Having to compile your javascript sucks.

That's why I don't like typescript :) Also because typescript makes things way less understandable than without type annotations

two hundred forty TWO billion to be correct :P

I had the internation Galaxy S as well and never my GPS worked, I say again __NEVER__ even after the Samsung promised fix. Lots and lots of lag when doing anything, the screen was awful with blue tint (it was marketed that amoled was much better than lcd at the time, a f*ing lie), battery was mediocre. Maybe you are talking about Galaxy S 2? I had mine in 2010.

2) How come the original Galaxy S "runs fine"? That was a pos! The gps didn't work, the performance was laughable compared to the iphone 4 at the time. How can you say this???

I love Hacker News. You get such geeky responses to a simple question :)

As someone that has done native and react native development this is far from true. Laying out views in react native using flex is 1000 times easier than anything iOS/Android has. Also you get to reload your code almost instantly to test changes in react native Creating a UITableView compared to FlatList in code is way easier. And don't get me started with the Android Activity/Fragments lifecycle methods mess. Android Studio and Xcode sucks both in different ways.

Even if it was the same effort to do these things in native it's stupid that in 2018 we have to implement basically the same things using 2 very different languages and tools. It's just sad to see the actual state of native development right now.

Sure performance is still a lot off than native but is enough most of the time. The complains I have about React native is that with version 0.56 they did lots of breaking changes that meant I am stuck for now with 0.55, the performance has much room for improvement and the quality of many modules are subpar. But I am hopeful that with the fabric rewrite things change.

>Allow me to preface this by saying that React Native sets out to solve problems I don’t think are very interesting to solve. In particular I don’t think that sharing a single UI between disparate platforms is desirable from any perspective that isn’t cost savings and that even from that perspective it’s dicey.

Allow me to disagree. Mobile development is a mess these days. Doing stuff in React native is way easier than native (when there is a module that implements what you want), so most of the time you do things (a lot) faster. Sure, react native needs a lot of work and stop breaking things every single version they update and the modules need to step up in quality. I hope with the fabric rewrite, things get much better.

Well I think today I fit in The Extreme Overestimator, The Bull in the China Shop, The Rockstar and The Hostage Taker, is this normal? :S

You are only telling part of the story here. What about the connect in the UI? mapStateToProps is called every single time the store is updated unless you provide a areStatesEqual function in each component you intend to connect to the store. This seems much more complicated that it should be. I have a react native app that receives market data quotes in real time and I have used redux to store all those market data updates along other data and now I regret it. If I had stored the data in POJOs and implement a very basic implementation of observer pattern would not only be more performant than would have been easier to implement. To connect the POJOs to the UI, I would only have created a smart component that connected to it and that's it. No redux, redux-sagas, areStatesEqual, mapStateToProps, reselect and all that. What do you think?

That is why I love React Native. Things like laying out screens is simple using flex and position properties. Laying out in iOS? Not as simple with those atrocities like auto layout, constraints...

NO, it isn't...

I would risk number 2 and replace it with exercise (not too early or too late)

668% wrong!! :D

Wow, how bright you are sir... If everybody thought like you, we would have a wonderful world, I am sure!

I agree with you, but could you care to elaborate on that?

In another news, people should duck and cover when there is lava coming in your way.

Hahaha understood friend :)

I understand that and I am an autodidact, but it's just unbearable the amount of information we need to learn to master a certain technology/language.

I have many projects at the same time and of different kinds, I am doing web projects, react-native mobile projects and I give support to older desktop applications. I am kind a jack-of-all-trades master of none, you know?

It's very difficult to improve like this because when I get home I am always tired and also I wanna have some life that is not coding...

Consider using Opera, it's so much better. It's the only mobile browser I know that does text reflow, which is essential for me.

What I meant was that Windows can have the good parts of both iOS and Android. To be clear: it can run as smooth as iOS while letting me access the file system as Android does. Another rant on Android: Developing apps for it is so bad... The guy that thought it was a good idea to destroy and recreate an Activity's after orientation changes should be fired. iOS's approach is 10000 times easier and faster

EDIT: Corrected when I said Activity's UI was destroyed to the Activity itself

This. 10000 times this. I really, really hope that Windows 10 wins this battle. It provides the best of both worlds. We can have snappy performance (iOS) while having access to the file system.