Post #661862

I'm now some 68 hours into rewriting faircamp's internal architecture for handling manifests, to accomodate (a) continuous reading and writing of settings at runtime, simultaneously from the outside (e.g. in a text editor) and in the desktop application (with live updates in the interface!), and (b) an entirely new settings inheritance system (actually a bit like the one that existed pre-1.0, just without the footguns [fingers crossed :D], and streamlined and redesigned for the new data model in 2.0). Truthfully this hasn't been my favorite part of the project so far '^^ - constantly too many things to trip over that can instantly turn into a productivity sink if you're not 100% on guard, fighting between uncomfortable levels of boilerplate/repetition and uncomfortable levels of abstraction (on the upside I've collaterally picked up a mad amount of new rust generics skills these last days). But ... I'm beginning to see the light at the end of this tunnel, and if the end result of this is roughly what I imagine it to be, faircamp 2.0 will be standing on one hell of a solid foundation for the coming months and years. (˶′◡‵˶) #faircamp