How Redux Works: A Counter-Example • Hacker News Board

Re: How Redux Works: A Counter-Example

#81

Post by lsdafjklsd » Tue, Nov 21, 2017, 3:38 AM UTC

interlocutor wrote: post #71

whitefish wrote: post #64

Earlier quoted context omitted.

Sorry, that’s not making sense. In the MVC I am used to there’s only one controller active at one time and that controller owns the entire screen.

@arximboldi, I wouldn't use MVC for implementing something like Photoshop or and IDE, that's not the kind of application MVC is good for. MVC works well for applications that navigate through multiple screens.

Yea basically this. Built a 'big data app' using Ember, which was all well and fine until some of the routes essentially became their own apps, that were more akin to apps like photoshop. MVC really broke down for us here, and it wasn't until we introduced react / redux and slowly refactored the application until things got more manageable and sane.

Re: How Redux Works: A Counter-Example

#82

Post by zebraflask » Tue, Nov 21, 2017, 4:01 AM UTC

newbear wrote: post #80

zebraflask wrote: post #37

Earlier quoted context omitted.

Agreed! Redux is cool but often overkill for basic CRUD apps, which the majority of JavaScript SPAs tend to be. My approach has been to take a long look at the app structure - if there's a way to refactor it to remove Redux (or what have you), that's probably the most sensible thing to do. Simple code > clever code where performance and maintainability are concerned. I wouldn't mind a use case where Redux would be ne…

Hey, this is a bit tangental but since you mention building enterprise SPAs I'll guess your experience will be able to help me. So, I'm not as experienced but can get around to learning any code and as I need to start building a portfolio I dove in again to build one. But things were breaking and I couldn't get rolling as fast I thought and although for a longer term bigger project I would spend the time tweaking I w…

The process stuff would probably be off-topic. But for something to get started with quickly, this is good:

https://github.com/kriasoft/react-starter-kit

Redux-friendly, too.

Re: How Redux Works: A Counter-Example

#83

Post by dimillian » Tue, Nov 21, 2017, 8:20 AM UTC

hakonber wrote: post #66

dimillian wrote: post #20

Switched our entire native app stack to a redux backend (Swift and Kotlin), never been happier. Sure there is more code in the end, but the decoupling and simplicity to use is just too good. Especially on iOS when you know how complex it is to maintain a controller hierarchy with a (now dead) dependency chain.

Did you use ReSwift and ReKotlin, or something else?

Both :)

Re: How Redux Works: A Counter-Example

#84

Post by beaconstudios » Tue, Nov 21, 2017, 11:27 AM UTC

Scarblac wrote: post #79

whitefish wrote: post #64

Earlier quoted context omitted.

Sorry, that’s not making sense. In the MVC I am used to there’s only one controller active at one time and that controller owns the entire screen.

In the original Smalltalk MVC pattern, every single element of the UI had its own model, view and controller. Since then a lot of different things have been called MVC..

OOP was very different in smalltalk too. Industry software dev has really strayed away from the theoretical origins it was based in, although I think the tide is starting to turn back now.