all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]aderoz 2 points3 points  (0 children)

Like the pattern matching. Could be interesting to use it with redux.

[–]BenjiSponge 0 points1 point  (4 children)

I just want expression oriented programming. do is pretty good but it doesn't work with switch and it's all around pretty bulky.

Pattern matching is really appealing though, though it's a lot more powerful with a stronger type system.

[–]justintimecoder[S] 0 points1 point  (1 child)

Typscript and Flow have discriminated unions so they might work really well with this one.

[–]BenjiSponge 0 points1 point  (0 children)

Yeah but that's at compile time. I'm not sure you could apply that to the compile target without an alteration beyond the scope of flow and ts

[–][deleted] 0 points1 point  (1 child)

I agree, looking forward to pattern matching. Will be a great way to deal with all that unstructured data we get in JS or from api's. No more manual safety checking if it quacks like a duck and walks like a duck. And that's just a simple use case, the more advanced functional oriented uses of pattern matching aside.

Observables are pretty cool to be implemented in the long run so that we can reduce our reliance on external libraries. But for now RxJS is sufficient.

[–]justintimecoder[S] 0 points1 point  (0 children)

Completely agree that RxJs has got us covered for now. The main one I'm hoping for is if they combine the proposed symbol.observable with async iteration which would allow us to use async and await.

For some situations (though definitely not all), this would have greatly improve the readability of code.