gosumemory
gosumemory copied to clipboard
Complete rewrite
Original architectural structure decisions were made back in the day when I was just starting coding and so it really is a mess. Was honestly surprised how stable it became after so many crutches and polishing attempts.
Current flaws:
- Blocking loops on each goroutine instead of a sequential operations/channels
- Asynchronous websocket stream as a result of ^
- Cgo calls mix within go calls/multiple instances of pp calculators
- Bad error handling (non-existent in some cases)
- .ini config was a mistake after all, we probably should move to something like json/yaml
- Mix of {log/pp/fmt}.Println calls for no reason
- Global variables mess across packages
- Non-Existent debug logging (besides
mempackage)
To combat that until it's too late I made a decision to rewrite most of the project.
The progress will be updated below:
- [ ] replace a mess that's also known as a
pppackage with https://github.com/l3lackShark/cgoppai - [ ] rewrite
memorypackage to the point that it's consistent with the way we read memory and send payload to web - [ ] GUI?