Hi, this is Matthew Podwysocki from the React Native Windows team here at Microsoft. I can address some of these points.
1. Yes, we are working on Windows tutorials at the moment and more detailed writeups such as how we got the F8 App from Facebook to run on RN for UWP. We've made a lot of strides lately with our React-Native CLI integration so you can do `react-native windows` and `react-native run-windows` which allows you to build and run your applications without requiring you to fire up Visual Studio.
2. We are definitely working on the examples to make sure they work out of the box with our run-windows command and will make sure that's done ASAP.
3. Yes, that's the intention to have a Hello Windows module. Right now we have a little sample that shows how to make custom controls and modules such as here: https://github.com/rozele/rn-tr23 with a map control but we will move a few to our GitHub organization to show you how its done.
4. With the React-CLI and run-windows, you should not need full Visual Studio running unless you are deploying to a device or emulator. If you are having issues with that, please file an issue and we'll get to it as soon as possible.
Unrelated: We are open to prettier templates but currently we are using the standard XAML templates which come with UWP so they have the look and feel of a common UWP app.
We're also looking at the list of the most popular React Native modules and ensuring that they work with React Native for UWP.
Awesome thanks for the hard work and feedback! yeah with respect to point 4, I mainly mentioned this because I do almost all of my app development while running the thing in an emulator - maybe you are saying it's only needed for the deployment step, and not the reload nowaways? (that would be a definite improvement) will have to check it out.
RxJS author here. Right, an advantage is if you know the Java, .NET, Python, C++ version, etc, then you know the JavaScript version. That and we try to adhere to an Array#extras style following all of ES2015/ES7 Array methods.
Another advantage is that many frameworks such as Angular 2.0 are shipping with support for Observables, so that's a huge win for users of RxJS that it automatically just works.
RxJS author here and creator of some of those exercises. This was meant as a hands on lab where we proctor the event. We've given this at a number of conferences including QCon, CodeMesh, among others to great success. If you have suggestions, please do file an issue and I'll make sure we get them addressed: https://github.com/jhusain/learnrx
RxJS author here. I'll make sure that it's more cross platform as I do actually work for Microsoft. This has been a Netflix only training platform, but in order for us to teach more, we have to be better about supporting all browsers.
RxJS author here. We on the RxJS team have never called RxJS FRP as we do not have a continuous notion of time, instead we have a notion of virtual time. That and we do not distinguish between events and behaviors as they all are Observable objects.
It doesn't seem to be very related. Virtual time as defined in jefferson's seminal paper is a variation of Lamport's virtual clocks used in distributed discrete simulations; it is the analog of virtual memory.
The name clash wouldn't be such a big deal (systems is far away from webdev), but time warp is also very related to transactions and FRP in providing abstractions to deal with change in reactive programs.
The RxJS author here. This was meant to be training for Netflix team members to become familiar with RxJS as they use Rx for pretty much all of their systems, whether front end or back end.
Yep, speaking as part of the team, we're committed to making it cross platform where it works with GCC, Clang and MSVC. It works on Linux, Mac OSX, Windows, Android and iOS.
1. Yes, we are working on Windows tutorials at the moment and more detailed writeups such as how we got the F8 App from Facebook to run on RN for UWP. We've made a lot of strides lately with our React-Native CLI integration so you can do `react-native windows` and `react-native run-windows` which allows you to build and run your applications without requiring you to fire up Visual Studio.
2. We are definitely working on the examples to make sure they work out of the box with our run-windows command and will make sure that's done ASAP.
3. Yes, that's the intention to have a Hello Windows module. Right now we have a little sample that shows how to make custom controls and modules such as here: https://github.com/rozele/rn-tr23 with a map control but we will move a few to our GitHub organization to show you how its done.
4. With the React-CLI and run-windows, you should not need full Visual Studio running unless you are deploying to a device or emulator. If you are having issues with that, please file an issue and we'll get to it as soon as possible.
Unrelated: We are open to prettier templates but currently we are using the standard XAML templates which come with UWP so they have the look and feel of a common UWP app.
We're also looking at the list of the most popular React Native modules and ensuring that they work with React Native for UWP.