Show HN: React Native Express – Learn React Native Through Interactive Examples
reactnativeexpress.com
Show HN: React Native Express – Learn React Native Through Interactive Examples
1–10 of 54 posts
Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#2Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#3This is the best way to get started learning React Native, really amazing work Devin!
Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#4This is the best way to get started learning React Native, really amazing work Devin!
Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#5Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#6The sections with ES6 vs output compiled with babel is amazing. Javascript really has come a long way.
Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#7The sections with ES6 vs output compiled with babel is amazing. Javascript really has come a long way.
Amazing yes. But I think that on certain sections they should output the console value instead. I'm specific talking about the Array Spread example as the Babel output in that case is a very roundabout and verbose way of showing me what the Array Spread Operator actually does. I think it would be better to allow the user to play with the operator and see the output of it right next to the code.
The compiled output starts out awesome with the first few sections, and then just gets tedious and weird.
Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#8Question - is it possible to make a third-party keyboard in react native currently (the kind you download an install from the app store)?
Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#9Re: Show HN: React Native Express – Learn React Native Through Interactive Examples
#10Earlier quoted context omitted.
Amazing yes. But I think that on certain sections they should output the console value instead. I'm specific talking about the Array Spread example as the Babel output in that case is a very roundabout and verbose way of showing me what the Array Spread Operator actually does. I think it would be better to allow the user to play with the operator and see the output of it right next to the code.
Totally agree with you on that. When I have a little more time I'm gonna add that. The compiled output starts out awesome with the first few sections, and then just gets tedious and weird.