From bea4f1d7b3af4eda86013dfac2549e50de69b594 Mon Sep 17 00:00:00 2001 From: zeromus Date: Sun, 1 Feb 2015 02:57:52 +0000 Subject: [PATCH] philosophize about good cores and bad cores --- Good Core Bad Core.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Good Core Bad Core.txt b/Good Core Bad Core.txt index 7db098d16f..d5085d8d79 100644 --- a/Good Core Bad Core.txt +++ b/Good Core Bad Core.txt @@ -9,6 +9,7 @@ Multi-instance capable. Multi-threading, if applicable, is handled internally. The frontend will call FrameAdvance() on a single thread and callbacks will be marshalled back to that thread. Settings and preferences, where applicable, can be specified by the frontend. +Flat C-style exportable API Bad Core: @@ -20,3 +21,4 @@ Optical disk access through cruddy cuebin system that can't be replaced easily. Single instance. Sloppy multithreading, or main program loop that can't be easily factored out. Settings and preferences go to untrappable file IO or central registry. +Convoluted object oriented APIs or no organized API at all \ No newline at end of file