Open chrisinajar opened 8 years ago
This creates a clear surface area in which customization to the system are possible. This fundamentally changes Maki from a magic black box where Eric Martindale's crackpot theories come to life in ways that only Eric Martindale can pretend to barely understand to instead a simple framework for orchestrating the construction of applications on the Fabric network.
bahahahaha
great writeup, and I think I understand the role of maki a bit more because of it. This project is highly ambitious... I would assume that there will be ways to hook into the maki architechture using other libraries/frameworks/etc, correct? For example, using angular templates at the UI and controller level and leveraging maki's more modular structure for models?
Angular would be an implementation detail of the UI layer. The idea is that the parts of the stack you interact with are abstracted from the UI implementation, your application should also work with a fat C++ client or a bash interface.
Nothing above the UI layer should be aware of the browser.
Amazing. Ty sir
Maki, as a framework, is unusably complex. Here is my proposal for how to re-architect and rethink the role of
Maki
without shrinking its scope or discarding the progress made.https://slack-files.com/T09HF1HK9-F0PBUR2AG-78ac26b2dc