Open swoolcock opened 4 years ago
Well, Swift source stability has settled down now, so going forward I don't see too many changes needed to keep it up to date.
I prefer using NFAllocInit over FazeKit, not sure why, maybe because I'm more familiar with it's contents.
Option 4: Make FazeKit mixed source, and move all the NFAllocInit code over to it, and sunset NFAllocInit?
FazeKit is the future
Most of the NextFaze projects that import FazeKit also import NFAllocInit just because FazeKit is incomplete.
Proposals
Make FazeKit feature parity with NFAllocInit, thus sunsetting NFAllocInit
Pros:
Cons:
Make NFAllocInit feature parity with FazeKit, thus sunsetting FazeKit
Pros:
Cons:
Strip any code from FazeKit that already exists in NFAllocInit
Pros:
Cons:
The third option is my where I'd personally like to take it. @ricsantos @SilkyPantsDan ?