but I ask why the devs didn’t implemented ‘md to docx’ as a built-in solution, when there are many open source scripts lying out there on github?
isn’t it a kind of locking?
Hi again!
Yeah, well, in my mind: to not natively support all formats ever constructed by other developers can hardly be called “locked-in”.
Most app developers try to concentrate on “doing their thing”, their “Unique Selling Point” (USP) as well as possible first and foremost. Do remember that this whole thread mainly is about if plugins, and their use by us, the users, creates a kind of lock-in or limitation in portability.
It is mostly not core functionality we are talking about in this thread, it is voluntarily added functionality created by users for other users. You, as a user, can just as easily chose to not install the plugins mentioned. What you will be left with is a “vanilla” Obsidian, which writes Markdown, and does it well (IMHO). Markdown is generally considered to be very portable, even though there are a couple of dialects (such as “Github flavour” etc).
I think you should turn your question around: would it not make more sense if Microsofts Word-team created an “import markdown” function? Markdown is an open standard that is very possible for them to add, if they were to prioritise users coming from Markdown based software, and MS Word tried to lure those users in to the fold.
To me that would make more sense than to say “Obsidian doesn’t export to my preferred external format, therefore it is lock-in”. Then another user might come along and say “booo! It doesn’t natively export to json, which is my preferred format!” and then a third one coming in saying “oh noes! Obsidian doesn’t support direct export to RSS, which I love!” and all of the sudden the very limited Obsidian developer resources have to concentrate on, and dig out, every format ever created by man, to create export functionality for those formats.
Ok, slight exaggeration, but you perhaps get my point? I know lots of apps that does not export to .docx. I wouldn’t dream of saying they therefore are locking users in, as I wouldn’t consider it to be true.
Another thing users often forget when it comes to development is maintenance. If any of those formats were to change, which they do (in many cases often too), things will start to break if all apps that claim they export to one of those formats doesn’t also update their code base to cater for the added/new/changed/deleted functionality in that format over there. In Obsidians case that could grind actual feature addition development to a halt, just keeping 67 export formats up to date whilst being backwards compatible.
So…many developers, rightfully so, concentrate on doing their thing, and to do it well. That is not lock-in.
IMHO of course.