I'm Jordan and I'm on the React (and React Native) team. There's been some great questions and insight on this thread. React Native offers a ton of benefits around productivity (and ability to use React of course), but since there are many questions about performance, I thought I'd share some of my own personal perspective on the matter. React Native is very different than other approaches because: 1. We're not promi…
Does JS run on the device or it's RN a pre-compiler?
Introducing React Native [video]
151–160 of 193 posts
Re: Introducing React Native [video]
#152If I'm one of Reacts competitors I'm ecstatic that they're abandoning the web. It reminds me of when Angular wastes energy on angular.dart because of a Google mandate. Didn't help them much.
Also, while all Dart does for Angular is fragment the community (because now we have Angular web devs using Dart, Angular web devs using JS and soon Angular web devs using AtScript), React Native actually does the opposite.
A lot of web devs already also do mobile development or at least work on hybrid apps (i.e. WebView-based mobile apps). React Native enables web devs to develop mobile apps that wouldn't have been feasible before (either because of the limitations of WebView or because they would have had to worry about learning an entirely different stack that is orthogonal to their web technology knowledge).
Re: Introducing React Native [video]
#153Can someone elaborate on how React Native would fit into the app development workflow (iOS)? Having a brief look over the ReactJS webpage, it seems like it would replace view controllers and perhaps Storyboards? Or are we talking about writing the entire application in Javascript, declaratively?
Re: Introducing React Native [video]
#154Re: Introducing React Native [video]
#155Earlier quoted context omitted.
TL;DR to below: focusing on JS instead of Xaml seems like a smarter play for a .NET developer that hasn't used Xaml in WPF or SL previously. I put "web oriented .NET developer" in my response for this specific type of question. I kind of defaulted (11 years ago) into ASP classic and ASP.NET as a result of ad hoc consulting/support work for MS technologies back in 2000. But despite my affection for C# I abandoned ASP.…
I program in WPF in C# with absolutely no XAML. I used to use dependency properties/data binding a lot, I even made a wrapper [1] so you could write things like: w0.Right.Bind = w1.Left + w2.Width; And that would automatically generate a one way data binding in WPF (so if w1's left property, w2's width property, or w0's width property changes, w0's left property is automatically recomputed). I've since moved on to my…
Re: Introducing React Native [video]
#156I'm part of the group that thought "what the hell?" when I first saw the React syntax - but seeing this has completely changed my mind and I'm really looking forward to picking up React as soon as possible. If this delivers on its promises (no reason to assume it won't, seeing as it's already being used in large apps) then it's going to change the mobile development landscape. It sounded like they may even be hinting…
> when I first saw the React syntax Do you mean JSX? Because "the React syntax" is just plain JS unless you're using JSX, is it not? IIRC even vdom nodes can be created by hand with literal objects.
Re: Introducing React Native [video]
#157Re: Introducing React Native [video]
#158I'm Jordan and I'm on the React (and React Native) team. There's been some great questions and insight on this thread. React Native offers a ton of benefits around productivity (and ability to use React of course), but since there are many questions about performance, I thought I'd share some of my own personal perspective on the matter. React Native is very different than other approaches because: 1. We're not promi…
Re: Introducing React Native [video]
#159Re: Introducing React Native [video]
#160Earlier quoted context omitted.
Very interesting. Microsoft allows you to build fully native (not webview wrappers) apps using WinJS, and they have shown that React (along with Angular) can be used to build those apps [1]. I wonder if Microsoft will put resources into bridging the gap between React Native and Windows 10. As a long time web oriented .NET developer wanting to pick up mobile who has been wondering whether to go Cordova or dive in full…
Honest question: Would you even need something like react on windows given that wpf/winrt already support dependency properties and data binding?