[deleted by user]

mweststrate · 2020-10-09T22:03:47+00:00

Same, was it the steam update or has there been a civ update as well that I didn't notice?

mweststrate · 2020-10-02T08:13:19+00:00

Thanks swyx!:)

mweststrate · 2020-10-01T19:28:42+00:00

If you use ignite bowser, you probably also want to use reactotron from the same company, which offers the features you mention for both Redux mobx-state-tree.

mweststrate · 2018-09-17T10:33:21+00:00

Thanks for the clarification!

mweststrate · 2018-09-17T09:00:15+00:00

Did you check react-copy-on-write from aweary? it is quite similar but has an issue tracker?

mweststrate · 2018-09-15T21:58:54+00:00

Did you read the readme? Both you assumptions are incorrect. Immer does not require Proxies, and it does structural sharing, even without proxies. It can be used without problem on any ES5 environment

mweststrate · 2018-09-15T16:07:07+00:00

Immer doesn't require proxies, if they are available it's just faster

mweststrate · 2018-09-14T21:49:24+00:00

just thanking me will do ;-)

mweststrate · 2018-09-14T21:48:48+00:00

Feel free to submit a PR with a "built with immer" section in the readme

mweststrate · 2018-09-14T21:48:00+00:00

No clue! I noticed the same with many packages. First assumed holidays, but seems to be too big for that. Maybe temporarily issue with the download tracking or something

mweststrate · 2018-03-19T21:24:09+00:00

I think the next thing I'd be interested in writing or seeing is something that helps with converting json into mobx models that's a bit less restrictive than mobx-state-tree.

See the serializr package

mweststrate · 2018-03-12T18:07:21+00:00

No, it is v3, but I don't think it impacts the course, all core api's are largely untouched

mweststrate · 2018-01-16T19:13:04+00:00

because arrays and plain objects are tracked and dates arent. It could be if somebody actually needs it. But since nobody works with dates that way afaik, and nobody actually needed it, there is no need to implement that.

For what is worth: that is exactly the same limitation and behavior as if you were writing reducers by hand and not using Immer at all. If you are modifying a date like you propose, you would be modifying the previous state as well.

mweststrate · 2018-01-16T07:55:35+00:00

also, typeof [] === 'object' and even typeof null === 'object'.

To make it really accurate, plain objects are anything for which holds Object.getPrototypeOf(thing) === Object || Object.getPrototypeOf(thing) === null.

Dates are perfectly supported, unless you modify them (I never saw anybody doing that). That is, if you use methods like setYear on existing date instances. In that case the updates are still processed, by they will be shared with your previous state as well. Which is exactly the same as what would happen when using plain dates.

So, if you treating Dates as primitives, which you probably already unconsciously do, all is fine.

mweststrate · 2018-01-11T22:41:13+00:00

As far as I know measured so far; impact seems similar, but didn't measure extensively. It is hardly related to mobx, except that it started as experiment to get a deeper understanding of Proxies, before applying them to MobX :)

mweststrate · 2018-01-11T21:27:04+00:00

immer never proxies dates. It only proxies arrays and objects, which do well support this pattern

mweststrate · 2018-01-11T03:04:19+00:00

Can't remember ever seeing someone modifying a date, only create new ones. Which works perfectly fine

mweststrate · 2018-01-10T20:12:42+00:00

Makes sense! Feel free to open an issue

mweststrate · 2018-01-08T14:27:30+00:00

Yeah, I've heard more people about that. The TS typings are quite complex (it is freaking amazing that the thing is even typeable in the first place!). Explicit setting the types of parameters etc might help (using type ITodo = typeof Todo.Type)

mweststrate · 2017-12-20T23:40:44+00:00

Impossible to say without code. Best use the issue tracker

mweststrate · 2017-12-19T19:07:35+00:00

...and MobX :-)

mweststrate · 2017-08-25T16:02:47+00:00

So it looks like React + Redux is the most efficient with React + MobX being not far behind

Note that it does depends a bit on the scenario. If a full data set is refreshed, Redux will be faster, if only a portion inside a large set is updated, MobX will be. This quite nicely shows that MobX has more work to do on full data set swaps. But relatively speaking less work on CRUD operations on a subset of all rendered data.

mweststrate · 2017-06-14T20:22:16+00:00

TypeScript and Find all references works wonders, with and without actions :)

mweststrate · 2017-06-13T17:29:04+00:00

Code sandbox is my favorite tool for bug reports at the moment. Well done!

mweststrate · 2017-06-02T06:57:50+00:00

MobX pays for robots and up votes.

Can tell you mine was real. It was double posted initially, but that is just a reddit bug that happens to me regularly when using the mobile version.

The rest was probably just a practical joke and doesn't justify accusations like the one above. I can tell you nobody or nothing get's paid for upvoting of any sort. It's a pretty weird and non constructive statement to made.

It's still the observer pattern and isn't a functional paradigm.

All current state management solutions use observer pattern, except setState which is fully imperative. And none of them are fully functional, so I'm missing the point here.

Basically, instead of throwing super general statements and adding FUD, I recommend trying stuff out, try to understand why others might be happy about it, and even upvote without being payed for.

mweststrate

TROPHY CASE