5 ms·

my impression is, if you going choose a paradigm like MobX, you might as well use Angular, which is conceptually pretty similar, just with different opinions on

by platz 6y ago

my impression is, if you going choose a paradigm like MobX, you might as well use Angular, which is conceptually pretty similar, just with different opinions on library vs framework.

acemarke 6y ago
That's the first time I've ever heard anyone say that "MobX and React are conceptually similar". MobX is technically based on an "observable" paradigm, but it's a completely different API and mental approach than RxJS is. Also, while MobX is commonly used with React, it's really a UI-agnostic state management library (same as Redux). I really wouldn't compare MobX and Angular at all. To me they look like completely different tools.
- platz 6y ago
  All I meant was they're a bit similar in how one often centralizes logic into services based on observables which also cause globally visible mutable state changes.
  - acemarke 6y ago
    Ah, gotcha.
nsonha 6y ago
no, you are making an argument that is React must be used a certain way (that is incompatible with MobX). I'm not sure what makes you think you're someone who can make gatekeeping statements like that if the react team never said such thing. MobX adds reactivity to your object oriented domain code and React allows you to write functional view component, what's wrong with that? And no using MobX and using Angular are 2 vastly different things. One can like MVVM (MobX) and dislike string template and other convoluted mechanisms Angular.