[ziyadb]

Interesting project. Semantically organizing code is a longstanding problem in the world of software development. The primary concern with this project, or any other attempts at solving this problem is practicality and actual utility.

I suppose utility rests on whether you treat it as a collaborative development platform or merely as a host for your code (and keep track of discussions, proposed changes, and what-not through other means).

Essentially, whether or not it turns out to be useful assumes that it is used as the central collaboration platform to an extent. Though on the other hand, merely tracking changes on a higher-level could be sufficient.

[caustic]

> I suppose utility rests on whether you treat it as a collaborative development platform or merely as a host for your code (and keep track of discussions, proposed changes, and what-not through other means).

They both naturally blend together. I honestly can't understand what is the difference between these two that you are thinking about.

> Essentially, whether or not it turns out to be useful assumes that it is used as the central collaboration platform to an extent.

This is the initial plan.

> Though on the other hand, merely tracking changes on a higher-level could be sufficient.

Some day we can implement a client side structural diff tool.