sorry, i would disagree. in general: results matter, not announcements. and as for announcements go – this one is vague at best.
- let’s take “SQL”: who cares where the data is saved? that’s a technical detail, which no one cares about. (it might be incredibly important, technically, for the development of the product – the user does not care at all …)
- then JSON: while “JSON” surely is super simple and standardized, the structure you use is … neither. you can change it any time, and at will – and it’s everything but “simple”.
- the API is not even planned.
- download anytype: well, even if you do, you can only export the data in the aforementioned JSON structure, which is of absolutely no use to anyone not willing or able to download and run source code from github – not knowing whether it will work or not.
I myself have already been burned by that export limitation, and there are several requests already to mitigate.
(for me, the exporter mentioned by @Filip here – thanks for the link – might be a solution, but that’s just a stop-gap, and a non-starter for non-tech-folks anyway …)
so yes, if you ask me, there most definitely is a “lock in” –at least at the present moment.
so “solving” this as @anton apparently did … a bit premature, and i fully understand @anytype_guru – i “only” created a massive list of watches and watchmakers, and already i am feeling the limitations up to the point where I cannot realize something I wanted to do.