Eko: New Programming language write entirely in D (Feedback welcome)

[pouya1dev]

On Saturday, 22 August 2026 at 09:18:36 UTC, user1234 wrote:
> On Saturday, 22 August 2026 at 08:38:39 UTC, pouya1dev wrote:
>> On Friday, 21 August 2026 at 20:44:37 UTC, user1234 wrote:
>>> On Friday, 21 August 2026 at 17:54:32 UTC, user1234 wrote:
>>>> On Friday, 21 August 2026 at 17:01:13 UTC, pouya1dev wrote:
>>>>> Thank you very much. I will definitely look into the 
>>>>> examples you provided.
>>>>
>>>> I forgot to mention a few several ones. Notably styx-lang. 
>>>> You also have two alternatives D front-ends written 
>>>> themselves in D. You see it's a classic to write programming 
>>>> languages. A bit like game engines.
>>>>
>>>> Recently we also had an annouce about someone using D to 
>>>> write a scripting engine but it was AI slop (Kite), so the 
>>>> topic was a bit delicate if you see what I mean.
>>>>
>>>> There is also one that was made for a game engine, I 
>>>> remember a conversation with the author on IRC but I cant 
>>>> find any official annouce RN.
>>>
>>> And of course "Beast". How I could forget this one. The 
>>> author used to be a casual contact on IRC too. IIRC he finaly 
>>> worked on a voxel engine because the thesis director was not 
>>> found on prog-langs. Also after the preliminary work the 
>>> student discovered that actually "code hatching" already 
>>> existed.
>>>
>>> - https://github.com/beast-lang
>>> - https://excel.fit.vutbr.cz/submissions/2017/018/18.pdf
>>>
>>> Really there is a lot of PL made in D. More or less 
>>> successful tho.
>>
>> I checked the link you gave 
>> https://github.com/beast-lang/beast-dragon and it seems that 
>> this language is no longer being updated. Because its last 
>> commit was 8 years ago. Also, the developer himself said that 
>> he has stopped developing the project. But I still think it is 
>> a great resource to learn. I think it could become a 
>> successful language. I was wondering if I could email him and 
>> he would respond? If so, that would be great.
>
> That a meme "dont ask to ask, just ask". The author explicitly 
> told me on IRC that his preliminary work can be used, i.e he 
> switched to something else. The licence also gives you rights.
>
> Before using Beast as a base for something else, however, I 
> would consider a bit how things are organized. If you look 
> well, each node had its own source file, which is not something 
> I liked. The big 5000 SLOCs source is not great either but 
> actually, with the visitor pattern, that's often just N 
> micro-programs, with N the number of nodes.

Also, having each node in its own file can be useful at first, 
especially when you are trying to find where a bug is. But as the 
project grows, maintaining and navigating all those small files 
can become a nightmare.