Architecting InnateMC #25
heftymouse
started this conversation in
RFCs
Replies: 2 comments 12 replies
-
|
Here's what I had so far:
|
Beta Was this translation helpful? Give feedback.
10 replies
-
|
InnateKit is starting to sound like over-engineering. It has a couple of abstractions for things that we could remove. The advantages of InnateKit are as follows.
InnateKit and InnateMC are also starting to have some blurred lines, namely preferences, as it is not known in which module they should be stored. The merger of InnateKit and InnateMC would signal the end of a hybrid development architecture and the beginning of a monolithic architecture. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As this app becomes larger, it becomes important to define a standardized architecture so that it remains easy to maintain in the future. This is dependent on opinions and peoples' conventions so it'd be good to discuss it in, well, this discussion.
Beta Was this translation helpful? Give feedback.
All reactions