News for hackers. Stuff that matters.

mattpodwysocki

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.

Re:Highland.js on Friday April 17, 2015 @10:54AM (#9394665)
RxJS authoer here. Instead, here are the reasons you may want to consider RxJS instead of Highland https://github.com/Reactive-Extensions/RxJS/blob/master/doc/...
Re:Highland.js on Thursday April 16, 2015 @06:37PM (#9391140)
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.

It's not. Virtual time can mean anything in this case as in not real time and it can be swapped out at any point.
As in you can specify the time at which things execute and swap out the concurrency model at any time. This makes it perfect for testing: https://github.com/Reactive-Extensions/RxJS/blob/master/doc/...
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
@jhusain not only that but we did introduce a CLI which allows you to bring in only what you need: https://github.com/Reactive-Extensions/RxJS/releases/tag/v2....

Still in its early days but is very promising for making RxJS as small as you wish.

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.
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.

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....

Re:C++React: A reactive programming library for C++11 on Sunday August 03, 2014 @12:13PM (#8128297)
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.
Re:TypeScript: New Compiler and Moving to GitHub on Tuesday July 22, 2014 @12:44AM (#8067432)
And the Reactive Extensions for all languages: https://github.com/Reactive-Extensions/
Re:An Introduction to Reactive Programming on Tuesday July 01, 2014 @12:03PM (#7971597)
I would certainly say that Rx has a superset of the operators in standard CEP which largely deals with buffers and windows, yes. In addition, we have time-based join and group join behavior, join calculus eg: Rx.Observable.when( stream1.and(stream2).then(...), stream3.and(stream4).then(...) );
Re:An Introduction to Reactive Programming on Tuesday July 01, 2014 @12:00PM (#7971556)
Yep, there are plenty of examples to be found such as those listed here: https://github.com/Reactive-Extensions/NDC-Oslo-2014

In addition, we ship a good number of samples within our RxJS repository: https://github.com/Reactive-Extensions/RxJS/tree/master/exam...

Re:An Introduction to Reactive Programming on Tuesday July 01, 2014 @11:57AM (#7971531)
There were definite tradeoffs to make while we were designing Rx and that was certainly one of them. Since we don't want to have to check if the stream is the same stream, instead of saying:

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), ...)

Re:An Introduction to Reactive Programming on Tuesday July 01, 2014 @11:55AM (#7971508)
That information is a bit dated as we have several ways of dealing with backpressure starting with RxJS 2.2.15 with the inclusion of pausable/pausableBuffered and controlled https://github.com/Reactive-Extensions/RxJS/releases/tag/v2....

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.

Re:An Introduction to Reactive Programming on Monday June 30, 2014 @04:37PM (#7967544)
Using Rx, you can certainly do CEP as we have buffer and window operators, and the ability to so groupBy and other complex operators. For example we have one that analyzes stock streams https://github.com/Reactive-Extensions/NDC-Oslo-2014/blob/ma...
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @04:34PM (#7967522)
steveklabnik, still working on the Ruby port of Rx. It will get there but needs more community support.
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @04:32PM (#7967511)
As the primary author of RxJS, I take exception to that characterization. Anyways, you should look at the performance differences between RxJS and Bacon.js. They are quite significant! https://github.com/pozadi/kefir/blob/master/test/perf/memory...
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @04:27PM (#7967482)
You can try our Learn RxJS tutorial here as well: http://reactive-extensions.github.io/learnrx/
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @04:25PM (#7967478)
Ok, the consider GitHub for Mac and Windows are both written using Rx frameworks. In addition, so is Cortana from Microsoft and has been in the phone ROM since day 1
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @02:44PM (#7966775)
Node.js streams are largely unicast, instead RxJS and related libraries can be multicast. RxJS, on the other hand has been fairly stable for quite some time now and the APIs largely haven't changed from when we first released in 2010.
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @02:42PM (#7966759)
Can you give some examples? I'm failing to see how this was a step backwards.
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @02:41PM (#7966754)
Why not try watching the video from Jafar Husain, a tech lead from Netflix, talk about Async JavaScript at Netflix which uses RxJS to explain these concepts? https://www.youtube.com/watch?v=XRYN2xt11Ek
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @02:40PM (#7966744)
It's not a fad at all, with Netflix and other companies using Rx in all flavors on their platforms. See this video from Jafar Husain, a tech lead at Netflix, talk about how they use RxJS at Netflix: https://www.youtube.com/watch?v=XRYN2xt11Ek
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @11:50AM (#7965672)
In this case, it's no more abuse than Ruby's Enumerable, JavaScript's Array#extras, and of course .NET's LINQ. How is this abuse exactly?
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @11:45AM (#7965635)
Because in this case, RxJS is actually quite easy to explain because of the lack of generics and angle brackets to get in your way to explain concepts. (Speaking as the author of RxJS).

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.

Re:An Introduction to Reactive Programming on Monday June 30, 2014 @11:43AM (#7965619)
Elm nor Rx or any of its variants are FRP, and instead, we like to consider ourselves on the Rx team as complex event processing and stream-based programming.
Re:An Introduction to Reactive Programming on Monday June 30, 2014 @11:41AM (#7965601)
It's funny how people think Reactive is new as we've been around since 2007 in different forms with a big release back in 2009 (so five years ago).

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.

Re:An Introduction to Reactive Programming on Monday June 30, 2014 @11:38AM (#7965582)
The Reactive Extensions covers all of those particular topics quite well, in terms of responsive to failure, responsive to events, responsive to 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

Older »