ikido

4 ms·

1.
by ikido 8y ago
While I don't think that posting solutions or using them is the right thing to do I'm grateful to the author for mentioning the course — it's fantastic!
2.
by ikido 10y ago
Very valid points addressed in this essay, I wonder if OS and messengers vendors will ever take that into account
3.
by ikido 11y ago
can you elaborate more why this approach is convoluted?
4.
by ikido 11y ago
Thanks, I'm actually working on it
5.
by ikido 11y ago
The concept of tracking data is actually quite simple — when you define some object property as observable it is replaced with a getter & setter that invoke a callback when you get/set that property. Then you can bind a function th
6.
by ikido 11y ago
That's a good point, but in Redux you subscribe to all changes in single state tree where all data lives. That means that every update of data (which has no upper limit) will cause your UI to re-render. Sure, you can implement shouldCo
7.
by ikido 11y ago
No difference in how you handle routing and history in a regular React app, those things are not related. Mobx (and mobx-react) just re-renders your component when data changes. You can check out performance tests here: https://w
8.
by ikido 11y ago
I know that a lot of people like to use different kinds of flux libraries for their React apps, with Redux having a lot of traction, but you should definitely look at Mobx. We've introduced it to one of our project 4 months ago and our
9.
by ikido 11y ago
Doesn't look very ergonomic — it's kind of hard to keep your hands in the air for a long time