15:03:03srazzaqueCurious question for all: in situations where you're consuming a library that de/serializes messages from <some format>, would you prefer the representation be in a (a) plist or a (b) alist, or (c) a CLOS object (assuming these messages are not particular large, <100 key-value pairs)
15:04:17dloweit depends on how static those keys are
15:04:50dloweif the messages have a defined schema that doesn't change a lot, I'd prefer a CLOS object
15:05:15srazzaqueyep, the messages do indeed have a schema
15:05:28dloweif the messages could contain anything (like a JSON blob) I'd probably prefer a plist or alist
15:06:57dloweNested plists if the messages are hierarchical
15:08:12srazzaqueI made the decision early on to go with CLOS objects for something I'm working on, but complexity and compilation times are getting, a bit high...
15:10:53dloweyou could be solving complexity in one spot instead of adding complexity all over, I can't tell from here