[stachudotnet]

appreciate the feedback here. as noted in some other comments, we spent all of 2023 on code, and only sprung up the new website at the end of the year. it needs a few iterations, and this feedback is useful. cheers.

By no git we definitely don't mean no version control.

[worksonmine]

> By no git we definitely don't mean no version control

So what does it mean?

[stachudotnet]

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.

[worksonmine]

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.

[stachudotnet]

The goal isn't lock-in.

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]

I do like git yes, and I don't see how I would've designed it any different. And I certainly wouldn't want it tied to my choice of language. The eco-system is large and I can host it on git{lab,hub} or any of the alternatives. Personally I self-host a Gitea instance. I use it for much more than just code, such as notes and personal wiki.

I get the feeling that Darklang is intended more as a platform than a language is that correct?

[refulgentis]

^ This, and gently, with your interests only in mind: you're sort of missing the point if you're still asserting "no, its the VCS and the host and the storage service and the and the and the" when people are interacting with you, with no further detail.

Shortly before I got a job at Google in Boston, I was still living in my dying steeltown and beautiful hometown Buffalo, NY.

I was absolutely _over the moon_ that a combined juicery/bar/Indian food/sandwich shoppe/bakery was opening nearby.

It never opened

In retrospect, with age, it would have been horrible[^1], and my friends were gently teasing me about my excitement were right.

Lets say the owner did have a series of specialists or a transformative way to pull of fusing these: they would have frustrated the small portion of the vast majority willing to engage by saying "hold on, it'll be awesome and totally will have all of those foods"

[^1] it wasn't a food hall, picture the size of maybe a mcdonald's and a half. even if you had a series of specialists for each of those, there wasn't enough room for a tandoor, grill, real juicer, deli, etc. etc.