Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I see a ton of discussion about the NodeJS decision and almost nothing about the more interesting industry paradigm shift to reactive programming and using functional-style programming in an imperative language.

They're joining the likes of Facebook, Netflix, Square, Microsoft, Instagram, Khan Academy, SoundCloud, Trello, New York Times, and others in adopting reactive extensions.



Yahoo is moving to the React javascript library. The "react" in React js does not refer to reactive programming in the "Reactive Manifesto"[1] sense.

    [1] http://www.reactivemanifesto.org/


They are also moving to a Flux-inspired application structure which is supposedly very similar to functional reactive programming, which is what the OP was referencing.


Good call. It seems a lot of the reactive examples I saw with React involved either RxJS or BaconJS. It's confusing naming for sure!


"paradigm shift to reactive programming"

What exactly do you mean by reactive here? As one of the other posters said, react's 're-render the virtual dom' concept doesn't have any direct relationship with the reactive manifesto, though flux might be a better candidate.


Your comment reminded me of this blog from Netflix: http://techblog.netflix.com/2013/01/reactive-programming-at-...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: