Live data from Hacker News

Viewing profile — mweststrate

mweststrate

HN member
Joined
Tue, Jan 27, 2015, 7:37 PM UTC
HN karma
56
Public activity
29 items

About mweststrate

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. comment
    Comment #14717616

    > I look at mobx I get reminded of.. Looking like, and being like are two different things :) Mobx reminds people (rightfully) of Meteor, Knockout, Angular etc, but when working wi…

  4. story
  5. comment
    Comment #13027784

    See https://github.com/mobxjs/mobx/issues/681#issuecomment-26234... (that thread started only yesterday, so it isn't very long yet), but yes, MobX is in use in large complex produc…

  6. comment
    Comment #12376552

    yep that was the glitch I was referring to indeed :)

  7. comment
    Comment #12371743

    The idea is very much like knockout and meteor, but the reactivity implementation is completely different. First all it is generic and not designed for just the UI. MobX is complet…

  8. comment
    Comment #12371607

    Online courses: Introductoin by LearnCode.academy: https://www.youtube.com/watch?v=_q50BXqkAfI More in depth: https://egghead.io/courses/manage-complex-state-in-react-app...

  9. story
  10. story
  11. story
  12. story
  13. comment
    Comment #11303332

    For your first question: nope, the important edge case is that deep changes on _non_ observable objects won't be observed. But that is no different from the edge that deep changes …

  14. comment
    Comment #11281454

    In MobX it actually doesn't matter whether the events happen inside or outside the component. Components themselves are part of the nervous system. They react to changing observabl…

  15. comment
    Comment #11273177

    I think it is quite different, at least if I read the docs correctly mercury is much closer to Redux / OM then MobX + React. MobX doesn't work with cursors and your tree doesn't ha…

  16. story
  17. comment
    Comment #11192291

    Sure, the promise of VDoms is performance. And vDOM has improved DOM performance a lot. But also not nearly enough to support the complexity of most real life applications that han…

  18. comment
    Comment #11192257

    Exactly. Integrating many apps is something we do as well. We have a large application that handles roughly 500 different domain classes (just scan through https://apidocs.mendix.c…

  19. comment
    Comment #11187127

    "With mutable data structures, it is trivial to guarantee that there is only one version of a certain domain object in memory." That statement refers to the fact that you loose (au…

  20. story
  21. comment
    Comment #10804071

    Object.observe was a bad idea. Even when it was available in chrome I didn't consider using it. However, the ES6 proposal for object proxies will hopefully become generally availab…

  22. story
  23. story
  24. comment
    Comment #10597919

    We use both; local component state as long as nobody else (might) be interested (this usually the case for generic components that are not application specific, such as page contro…

  25. story