mattpodwysocki
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.
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.
Still in its early days but is very promising for making RxJS as small as you wish.
We've made great strides recently making Rx more accessible including making it easier to pull in only the things you want/need: https://github.com/Reactive-Extensions/RxJS/releases/tag/v2....
In addition, we ship a good number of samples within our RxJS repository: https://github.com/Reactive-Extensions/RxJS/tree/master/exam...
stream1.combine(stream1.skip(1), ...)
We encourage since it is the same stream to use zip to avoid glitches and keep our overall memory footprint low:
stream1.zip(stream1.skip(1), ...)
We then updated it to have .pause and .resume methods on the Observable itself to take care of some of the ugliness: https://github.com/Reactive-Extensions/RxJS/releases/tag/v2....
Overall, these do not go ultimately up to the publisher as we're dealing with multicast streams in which we don't want other subscribers to pay any penalty for one slow subscriber.
That and it's very applicable to current problems with web-based programming of the coordination of events, promises, and any other I/O such as Web Sockets, XHRs, etc.
I would disagree as being the primary author of RxJS as well as a contributor to all other flavors that it's just about slinging around events. It's more than just that as we have to deal with failure, load, etc.
We cover that a bit in our repository with the Reactive Manifesto: https://github.com/Reactive-Extensions/RxJS
And I've even covered it at StrangeLoop 2013: video: http://www.infoq.com/presentations/rx-event-processing slides: https://github.com/Reactive-Extensions/StrangeLoop2013
As well as FutureJS: video: https://www.youtube.com/watch?v=zlERo_JMGCw slides: https://github.com/Reactive-Extensions/FutureJS