At one point I really thought that this could be the notes/knowledge management tool I needed: the data model looked clean on the surface, everything's an object, objects are typed (Note, Journal Entry, Person, Company, ...), Types are defined by a layout (view) and properties (model), so, if you've spent any amount of time using a RDBMS/ORM/web framework/OOP, it clicks, and brings a ton of clarity and structure compared to the usual suspects (obsidian and Logseq are barely decent trash collecting systems in my rigid expectations, and those tools give me extra work to do to clean things up and maintain consistency instead of helping me organize and plan things).
But where Anytype disappointed me greatly is that this apparent structure is only used when new objects are instantiated: as soon as the base model changes, you are left with the exact same mess to clean as the alternatives. Say, if you define a "Colleague" object type with properties "Department: String" and later on, you want to add a new property "Manager: Person", your pre-existing "Colleague"s will not have nor display this property at all. Sure, you can manually add the property later, but you are SOL when you need to do that for dozens of objects: not only the model isn't inherited from the base class but the view isn't either, and while you go about updating every instance of your model to add missing properties, you get to do a lot of layouting at the same time.
That's especially disappointing because some of Anytype capabilities truly are mind blowing, the real time sync across devices gives a lot of hope for the upcoming collab and publishing features.
If you HN folks have suggestions as to what system would work in my case, please let me know.
But where Anytype disappointed me greatly is that this apparent structure is only used when new objects are instantiated: as soon as the base model changes, you are left with the exact same mess to clean as the alternatives. Say, if you define a "Colleague" object type with properties "Department: String" and later on, you want to add a new property "Manager: Person", your pre-existing "Colleague"s will not have nor display this property at all. Sure, you can manually add the property later, but you are SOL when you need to do that for dozens of objects: not only the model isn't inherited from the base class but the view isn't either, and while you go about updating every instance of your model to add missing properties, you get to do a lot of layouting at the same time.
That's especially disappointing because some of Anytype capabilities truly are mind blowing, the real time sync across devices gives a lot of hope for the upcoming collab and publishing features.
If you HN folks have suggestions as to what system would work in my case, please let me know.