You are, however, correct when you ask if my point is that ReadingChangedObservable could have been used identically in both the async version and the Rx version. That's precisely the point. By defining your API (ReadingChangedObservable / ReadingChangedAsync / WhenReadingChanged / whatever) to return an IObservable you can use it with either Rx composition (appropriate when composing streams) or with async/await (appropriate when composing the "next" event as was done in several examples here). Contrast this with returning a Task. If you do that, you've lost the stream and can only compose with async/await (actually, we're totally glossing over composing with ContinueWith... the key is that await works not on Task but on awaitables, and both Task and IObservable are awaitables). IMHO, nothing is gained by returning Task, but a lot is lost, so you simply shouldn't return Task here.

posted by wkempf

The guidelines as I see how they should be followed:

1. If the legacy event is part of an EAP implementation, wrap it with a Task, otherwise wrap it with an IObservable.

2. When composing, if you're composing streams you'll use Rx combinators, otherwise you should prefer language combinators using async/await.

(2) is a little oversimplified, so there's likely exceptions to be found, but 1 seems pretty obvious and I see no room for variation.

posted by wkempf

posted by wkempf

// Shake detection using async (from a stream of Accelerometer.ReadingChangedEventArgs)
public async void StartShakeWatcher(Accelerometer accel) {
    var t = DateTime.Now;
    while (true) {
        // Doesn't matter if WhenReadingChanged returns a Task or an IObservable, this works the same.
        var e = await accel.WhenReadingChanged();
        if (Math.Pow(e.AccelerationX, 2) + Math.Pow(e.AccelerationY, 2) < 1.1) continue;
        if ((DateTime.Now - t).Milliseconds < 200) Shake(this, null);
        t = DateTime.Now;
    }
}

posted by wkempf

At an implementation level, you also have problems. Your TaskCompletionSource pattern fails to handle exceptions.

posted by wkempf

posted by wkempf

1 hour ago

Is there a dependency on Team System in order to use GitHub from Visual Studio?

If I've read the linked pages correctly, no. You can create just a local Git repository when creating a project, and you can clone a project from GitHub or anywhere else.

posted by wkempf

I'm actually disappointed with the B&N and MS collaboration so far. A Windows 8 app, but no WP8 app? The Windows 8 app isn't all that spectacular, either, in comparison to the Kindle app (I'm a NOOK owner, and live in that ecosystem, so I'm not playing fan boy here). Then the most recent NOOK tablet was still an Android based system. Doesn't seem like much of a collaboration to me.

posted by wkempf

posted by wkempf

Everything else you said I've already said I'm in total agreement on. TypeScript should have source mapping, and that source mapping should be (barring compelling reasons otherwise) based on the existing draft proposal. If the existing proposal falls short for some reason, first the proposal should be tweaked before abandoning for an entirely different proposal. That's how standardization processes work.

posted by wkempf

posted by wkempf

There's a reason the mozilla source mappings are in draft. Ignoring their existence would be wrong, so I mostly agree with your sentiment. However, that doesn't entirely preclude the possibility that the draft either needs tweaking or even may need to be thrown out for an alternative design... it just means such direction should include documented reasons and be submitted as a competing proposal.

That said, you're quite correct that source mappings should be a high priority feature to add here, and the goal should be to use the draft proposal for the feature.

posted by wkempf

posted by wkempf

posted by wkempf

posted by wkempf

posted by wkempf

posted by wkempf

posted by wkempf

4 hours ago

Am I only one who thinks MS behavior is pretty much same as other

Obviously not. At least two other people made that observation before you in this thread.

It's not precisely the same, but it's close enough to be creepy.

posted by wkempf

posted by wkempf

posted by wkempf

Nice to see myself in the show though

posted by wkempf

posted by wkempf

posted by wkempf

posted by wkempf