None of my projects want to be SPAs

Re:None of my projects want to be SPAs by poink on Monday February 11, 2019 @05:09PM (#19138851)

I read the thread. You hand-waved away a non-trivial problem by "explaining" properties are a thing. Thanks, bud. I'm sorry I didn't cite your favorite source to your satisfaction, but I quoted the relevant parts of the post I replied to.

> Futher, Redux doesn't solve synchronization issues in situations where you can't represent the data the same way.

It's kind of the whole Redux philosophy that you won't do that. It's in the FAQ. There's no "can't". You're never forced to keep duplicate data in your store.

[ Parent | on HN ]

Re:None of my projects want to be SPAs by kerkeslager on Saturday February 16, 2019 @09:57AM (#19178771)

But, in a project of any significant complexity, you will represent the data in different formats, because transforming data into different formats is one of the main functions of software. Relying on a framework that assumes you won't do something that you will do is a Very Bad Idea.

[ Parent | on HN ]

Re:None of my projects want to be SPAs by poink on Wednesday February 20, 2019 @07:49PM (#19213541)

It's almost like `mapStateToProps` is a thing and Dan Abramov has built a web app before. You have to store and transform your data in a normalized form, but you can consume it however you want.

Restrictions are the price of solving hard problems (even if you don't want to admit they're hard) in a deterministic fashion.

[ Parent | on HN ]