Great video, thank you! Can you explain the syntax used when you wrote Array(200)? I can't find that written anywhere - it's the first time I've come across something like it
@13:48 Can someone explain what this is: Animated.event([{ y: this.point.y }])({ y: gestureState.moveY }); I've seen code like this: 1. If you're interested to the `evt` Animated.event([ { nativeEvent: { contentOffset: { y: this._animation } } } ]) 2. If interested to `gestureState`. Animated.event([ null, { dx: this._animation.x, dy: this._animation.y } ]) So this `Animated.event([{ y: this.point.y }])({ y: gestureState.moveY });` is then probably an IIFE, and in the second (... ) Ben passes an object as a parameter. Right? But how does this work? And why he doesn't use null if the first place of the array, like in No 2? Thanks
@@bawad it's just a framework that wraps around another framework. So now its 3 levels of a mess that you have to deal with. I think it would be ok for simple small projects. Maybe even pure JS/TS project, but if you are doing anything with the hardware (GPS, camera, storage.. etc) or if the project is going to be big. Stay away from expo. I have really bad experience with it, I took over a project where the previous developer used expo, everything was broken, I spent 2 days trying to fix all the issues before I gave up. The funny thing is that I wasn't alone, I found all the issues on stackoverflow, github, and expo forums, there was always hacks, weird workarounds, and overall things not recommended. I ended spending 3 days stripping out expo and migrating everything to just pure React Native
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
Nice to have you back and good that you enjoyed your holiday! 😀
Thanks for this tutorial dude. Listening to you explain it slows things down so I actually understand it instead of skimming through docs.
How are you able to show console logs in nice way in terminal at @11:05
Great video, thank you! Can you explain the syntax used when you wrote Array(200)? I can't find that written anywhere - it's the first time I've come across something like it
initializes the array with length 200
@13:48 Can someone explain what this is: Animated.event([{ y: this.point.y }])({ y: gestureState.moveY });
I've seen code like this:
1. If you're interested to the `evt`
Animated.event([
{
nativeEvent: {
contentOffset: {
y: this._animation
}
}
}
])
2. If interested to `gestureState`.
Animated.event([
null,
{
dx: this._animation.x,
dy: this._animation.y
}
])
So this
`Animated.event([{ y: this.point.y }])({ y: gestureState.moveY });`
is then probably an IIFE, and in the second (... ) Ben passes an object as a parameter.
Right?
But how does this work?
And why he doesn't use null if the first place of the array, like in No 2?
Thanks
Did you ever find a good explanation for this syntax? Looks like greek to me. I would love to understand whats happening.
@@DryRotProjects No, not yet bro... and I’m Greek 😄 Imagine that... 😂😂😂
PS I know the expression. 😉
Dear Ben Award,
Do you test you solution inside parent ScrollView?
Thanks
Heyyy welcome back Ben :)
welcome back :)
have you done the other video?
ruclips.net/video/huLpYZ207pc/видео.htmlsi=SlwmyJyLdq1eyYtv
Can you share your RN settings in vscode (extension, config), such as a setting sync config file?
gist.github.com/benawad/1e9dd01994f78489306fbfd6f7b01cd3
can you please tell me which editor is this?
VS Code
can we expect a series on react native reanimated?
nope, I've never used reanimated
Hi Ben, awesome tutorial, but I a need help. Can you please show us how to do this coding in js instead of tsx.
hello, have you seen a solution for this on jsx?
Continuation: ruclips.net/video/qeKP2A7bLUw/видео.html
i know it's been 4 years already but thank you
Ben is back:)
why don't you use hooks?
Implementing this with a class was simpler
@@bawad But do you think that flatlist performance can be affected by hooks?
no, I don't think it matters either way
very very cool. thanks
Learning react native is very easy than setup it's environment 🥺😓
I despise expo to the core. 🤬
why
@@bawad it's just a framework that wraps around another framework. So now its 3 levels of a mess that you have to deal with.
I think it would be ok for simple small projects. Maybe even pure JS/TS project, but if you are doing anything with the hardware (GPS, camera, storage.. etc) or if the project is going to be big. Stay away from expo.
I have really bad experience with it, I took over a project where the previous developer used expo, everything was broken, I spent 2 days trying to fix all the issues before I gave up. The funny thing is that I wasn't alone, I found all the issues on stackoverflow, github, and expo forums, there was always hacks, weird workarounds, and overall things not recommended. I ended spending 3 days stripping out expo and migrating everything to just pure React Native
true if you have to do something that expo doesn't support, it gets messy