4 ms·
I am using TypeScript in a middle sized app (around 200 react components) and its help is invaluable for collaborating and sharing APIs. Currently it is based
by kuon 10y ago
I am using TypeScript in a middle sized app (around 200 react components) and its help is invaluable for collaborating and sharing APIs.
Currently it is based on redux, but I have a feeling I have to write too much code, I am looking into MobX as an alternative.
I think TypeScript is the best thing that happened to the JS community in a long time.
- saosebastiao 10y agoDon't hesitate to jump ship to Mobx. No regrets at all, it was like trading in a Lada for a Toyota. And being written in typescript, the TS support is impeccable.
- kuon 10y agoI wonder if such comments: http://disq.us/p/1bpl2ua http://disq.us/p/1bpl2ua are actually based on reality or just a plain rant. I worked with SproutCore, Angular and others that tried to be "smart", and while it was awesome at first, in the long run it was hard to maintain.
- spion 10y agoIn this video: https://www.youtube.com/watch?v=TfxfRkNCnmk https://www.youtube.com/watch?v=TfxfRkNCnmk The author of MobX explains how MobX works and implements a 50 line version of it (a fast and functional one too, except without the sugary decorator syntax) You can see the presentation and decide for yourself.
- Keats 10y agoI just did that (redux -> mobx) as mentioned in another comment and it made the code easier to understand, everything typed with less than half of the code. No more connect or action, we just call the store method (equivalent to a reducer fn) directly. I also moved most of the components that had state to use observable variables and it's been working well.
- kuon 10y agoI've migrated a small part of my app to MobX to try it, and it's really a threat. Code size divided by like 4. I cannot really speak in term of maintenance or architecture quality yet. But it works.