3 ms·
Other than declarative vs imperative, please substantiate your post with examples of what isn't possible in WPF or Cocoa. I have a feeling it's more of an expe
by LeoNatan25 10y ago
Other than declarative vs imperative, please substantiate your post with examples of what isn't possible in WPF or Cocoa.
I have a feeling it's more of an experience / competency issue rather than lacking APIs.
- mlsarecmg 10y agoIt's the ease of declaring components and structuring complex applications with it. There is nothing in WPF that is comparable to it unfortunately, except Redux.NET maybe, but XAML is a lost case against JSX. You'd have to see it, or work with it. The bottom line is, drastically less code, clean structures, things become simple to do. Debugging is also something different: https://camo.githubusercontent.com/a0d66cf145fe35cbe5fb341494b04f277d5d85dd/687474703a2f2f692e696d6775722e636f6d2f4a34476557304d2e676966 https://camo.githubusercontent.com/a0d66cf145fe35cbe5fb34149... Like hot module reload where you write your app live. You edit one component, everything else stays in place and maintains state. Or time travel with Redux, where each piece of state is inspectable. You roll back or slide through the apps history and see it literally build and deconstruct itself. That's possible because UI is just a function of state. Same state, same UI.