On the view side, it looks (conceptually) a lot like Microsofts WPF view framework (built in 2005): Declarative logical views, with the actual rendering infrastructure handled totally separately, allowing it to happen on separate threads (an IPC call in WPF's case). And I guess the web had declarative views long before that, although it's origins (Hypertext Markup Language, and not App Markup Language) caused so other particularities not found in native apps. Seems insane NOT to do views in this declarative way now.
Totally true, Core Data is elegantly multithreading-friendly, and can use multiple persistent stores if need be. Now, the project started 2 years ago (26:40) so maybe CD was not as mature at the time. Also, I would argue that FB needs a framework that also works on Android, hence their interest to develop their own framework.
I also fail to see how auto layout and a good understanding of Appkit doesn't meet their needs. Why a change in layout should propagate to the model, for example?
Shame that they did not mention any intentions to open source these projects. That would be awesome. Maybe once they finish swift port :-).
Why does the graph at 12:13 not have any units on the axes? Pretty useless visualization...
On the view side, it looks (conceptually) a lot like Microsofts WPF view framework (built in 2005): Declarative logical views, with the actual rendering infrastructure handled totally separately, allowing it to happen on separate threads (an IPC call in WPF's case).
And I guess the web had declarative views long before that, although it's origins (Hypertext Markup Language, and not App Markup Language) caused so other particularities not found in native apps.
Seems insane NOT to do views in this declarative way now.
If not open sourced, native developers would best keep using Core Data.
Keywords: native / ❌CoreData / immutable / eventual consistency / one way data flow / declarative / view recycling / component / infrastructure / Objective C++ / 🔜 Swfit
Someone at Facebook needs to go out and buy a Core Data book
Totally agree!!!
Totally true, Core Data is elegantly multithreading-friendly, and can use multiple persistent stores if need be.
Now, the project started 2 years ago (26:40) so maybe CD was not as mature at the time. Also, I would argue that FB needs a framework that also works on Android, hence their interest to develop their own framework.
I also fail to see how auto layout and a good understanding of Appkit doesn't meet their needs. Why a change in layout should propagate to the model, for example?
"… But iOS is still a relevant platform …" Lol.