Darklang classic had version control built into the project. We'll build version control into the new version of Darklang as well. If you need something to reference, Unison's mechanism for version control is an inspiration.
What's the reasoning behind that choice? Wouldn't it be more useful to have some kind of integration with git if it really has to be a part of the platform? Seems like it would be very isolating and hinder adoption.
Is the goal as much lock-in as possible or do you see benefits that I'm missing? I prefer the unix philosophy and like to setup my own toolbox so I'm not the target audience, I'm just curious.
Do you actually _like_ git? Or is it just good enough to get by?
Do you like having to git pull and git push and set up remotes and such? Or would something more integrated into your language and team and setup be nicer?
I think git is great, and better than many other options, but I don't think it's optimal. And it's not integrated with a larger system optimally.
Besides, while you do edit Darklang code in a text editor, it's not (WIP[1]) saved just in text files on disk. When you save, the code is automatically synced, available to you (and your team) immediately (with feature flagging and other tools to help make sure you don't "merge" incomplete/bad/broken stuff).
I absolutely understand the hesitancy, and concerns about vendor lock-in. We're doing our best to not lock users in, including working towards nice ways to "export" all of your dark stuff to another language/etc, using AI, if you so choose to bail.
[1] with minor extension, a text editor may work upon 'virtual' text files / workspaces, and when you save those, cool things happens. (yes, this is a bit hand-wavey, but we're just a few folks at this point and doing our best to make it less hand-wavey, soon :) )
worksonmine|1 year ago
Is the goal as much lock-in as possible or do you see benefits that I'm missing? I prefer the unix philosophy and like to setup my own toolbox so I'm not the target audience, I'm just curious.
stachudotnet|1 year ago
Do you actually _like_ git? Or is it just good enough to get by?
Do you like having to git pull and git push and set up remotes and such? Or would something more integrated into your language and team and setup be nicer?
I think git is great, and better than many other options, but I don't think it's optimal. And it's not integrated with a larger system optimally.
Besides, while you do edit Darklang code in a text editor, it's not (WIP[1]) saved just in text files on disk. When you save, the code is automatically synced, available to you (and your team) immediately (with feature flagging and other tools to help make sure you don't "merge" incomplete/bad/broken stuff).
I absolutely understand the hesitancy, and concerns about vendor lock-in. We're doing our best to not lock users in, including working towards nice ways to "export" all of your dark stuff to another language/etc, using AI, if you so choose to bail.
[1] with minor extension, a text editor may work upon 'virtual' text files / workspaces, and when you save those, cool things happens. (yes, this is a bit hand-wavey, but we're just a few folks at this point and doing our best to make it less hand-wavey, soon :) )