www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - G Language (written in D) featured in awesome-d and

reply pouyathe <pouya.momhidei gmail.com> writes:
Hello D Community,

I wanted to share a project I've been working on that might be of 
interest: the G Language.

G is a minimalist, memory-safe interpreter for systems scripting 
with a footprint of about 2.4MB. The entire toolchain is written 
in D.

Recently, it was accepted into the awesome-d list. I also wrote 
an article about the experience of building it and getting 
feedback from Walter Bright: [When Walter Bright Told Me to Write 
About My 2.4MB Language (cross-posted on 
Dev.to)](https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-my-24mb-language-37ki).

I'm sharing this here for two reasons: first, to say thank you to 
the D community and ecosystem that made it possible, and second, 
in case anyone is curious about a non-trivial use of D for 
building language tools.

I would be very grateful for any feedback, technical insights, or 
questions from the community that understands the foundation it's 
built upon.

Best regards,
Pouya Mohammadi
[github](https://github.com/pouyathe/glang)
Feb 01
next sibling parent reply matheus <matheus gmail.com> writes:
On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 ...


Interesting and for what it seems it's a script language, I wish 
you success.

You could write more how you're using at work work.

Just a information:


 Try it (30 seconds): glang.ct.ws


Well, I enter that site but any links (ie: Docs, Downloads, 
About) gives me 404.

For example Download is pointing to: 
https://github.com/pouyathe/glang/releases/v5.0.0
"Docs" and "About" are ending up to: 
https://errors.infinityfree.net/errors/404/

Matheus.
Feb 01
parent pouyathe <pouya.momhidei gmail.com> writes:
On Sunday, 1 February 2026 at 18:47:22 UTC, matheus wrote:

 On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 ...


 Interesting and for what it seems it's a script language, I 
 wish you success.

 You could write more how you're using at work work.

 Just a information:


 Try it (30 seconds): glang.ct.ws


 Well, I enter that site but any links (ie: Docs, Downloads, 
 About) gives me 404.

 For example Download is pointing to: 
 https://github.com/pouyathe/glang/releases/v5.0.0
 "Docs" and "About" are ending up to: 
 https://errors.infinityfree.net/errors/404/

 Matheus.


Thanks for your kind words, Matheus!

You're right about documentation - I'm actively working on the 
website and comprehensive docs since G is new.
The docs will cover everything from basics to advanced features.

I'm committed to making G the best experience for all users. If 
you have specific questions meanwhile, feel free to ask!

Thanks for using G,
Pouya

PS: Have a good day/night (our timezones differ, but good wishes 
are universal!)
Feb 02
prev sibling next sibling parent reply MacAsm <netorib94 gmail.com> writes:
On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 [...]


Wish you success
Feb 01
parent pouyathe <pouya.momhidei gmail.com> writes:
On Sunday, 1 February 2026 at 23:14:00 UTC, MacAsm wrote:

 On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 [...]


 Wish you success


Thank you, MacAsm! I appreciate the encouragement.

If you have any technical questions or feedback about G's 
implementation in D,
I'd be very interested to hear your thoughts.

Best regards,
Pouya
Feb 02
prev sibling next sibling parent reply =?UTF-8?Q?S=C3=B6nke_Ludwig?= <sludwig outerproduct.org> writes:
Looking at the project, this appears to be nothing but a big pile of AI 
slop with no real functionality (just like the newsgroup post itself). 
As an example, look at the "source code": 
https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

My suspicion would be that the repository contains malware, although I 
haven't looked into that.
Feb 02
next sibling parent reply matheus <matheus gmail.com> writes:
On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": 
 https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


If that's true this is sad, in fact really sad times we are 
living in. In this case there were even a page for the project 
and a a blog post in some site detailing things.

An awkward note was the math operation which seems like a stack 
calculator than anything, that's why I asked in my post how he 
was using this script language at work (Which he claims is his 
dev.to blog post).

Anyway internet is going to be tough and even tougher to be in...

Matheus.
Feb 02
parent reply pouyathe <pouya.momhidei gmail.com> writes:
On Monday, 2 February 2026 at 19:38:12 UTC, matheus wrote:

 On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": 
 https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


 If that's true this is sad, in fact really sad times we are 
 living in. In this case there were even a page for the project 
 and a a blog post in some site detailing things.

 An awkward note was the math operation which seems like a stack 
 calculator than anything, that's why I asked in my post how he 
 was using this script language at work (Which he claims is his 
 dev.to blog post).

 Anyway internet is going to be tough and even tougher to be 
 in...

 Matheus.


Hello Matheus,

Thank you for your comment. You are right to feel skeptical, and 
Sönke was right to point out the state of the code. I should have 
explained the context from the beginning.

The project is not AI-generated slop or malware. It is a working 
but very poorly presented interpreter that I built under 
difficult conditions.

The reason the code looks so strange—full of empty functions and 
messy structure—is because I developed it mostly offline with 
extremely limited resources. I live in Iran, where:

     Stable internet access is a luxury, not a given.

     Many developer tools, AI assistants, and even educational 
platforms are blocked or inaccessible.

     Coding sessions are often interrupted, leading to fragmented 
progress and placeholder functions.

The "stack calculator" feel you noticed is accurate for the early 
version. It was a kind of stack-based interpreter because that's 
what I could figure out and build on my own, with no mentors and 
spotty access to reference materials.

You were intrigued by the idea of a minimal language, and that 
idea is real. The current code is just a very flawed first draft 
of that idea.

I have now updated the README to be transparent about this being 
a personal learning project built in isolation. My goal now is to 
refactor it into something clean and usable, step by step.

If the concept of a minimal, memory-safe language is interesting 
to you, I would be grateful for any advice on how to structure 
such a project properly. The current mess is not the final 
vision, just the starting point.

Sincerely,
Pouya
Feb 02
parent reply ketmar <ketmar ketmar.no-ip.org> writes:
On Tuesday, 3 February 2026 at 03:33:04 UTC, pouyathe wrote:

 The current mess is not the final vision, just the starting 
 point.


so, you wrote a barely working mess (and why it is on version 5+ 
then?), created a site for it (i see, problems with internet 
access, so the site is a must, of course), and started to promote 
your "product" by pushing it into lists and writing articles.

nowhere in dev.to artictle you wrote that this is just a 
beginners attempt made for learning. you said that it is used in 
"production", it is ready for such use, and you even versioned it 
as "5.x", to make it look mature.

and when people started asking questions, you quickly backpedaled 
and begin making excuses. now you are looking even worser.

ah, and before you try to make some more calls to your bad living 
conditions: i am living in Ukraine, i not only have blackouts, 
there is a real full-scale war here going for 4 years. so your 
excuses will not work on me, try to invent something better.

p.s.: btw, 2.4MB binary is HUGE. my optimising Scheme compiler 
with various libraries is only 1.4MB, and it is fully featured 
programming language, i wrote several video games with it.

i also looked at your source code, and it is not only bad, i 
immediately spot several bugs, even without trying. those bugs 
should not survive v0.0.0.1-prealpha, how come they managed to 
make it to version 5+?

can we take a look at the first PoC, v1, v2, v3 and v4, please? 
or it is simply started as "version 5" because you tried to sell 
it as some mature thing?
Feb 03
parent reply pouyathe <pouya.momhidei gmail.com> writes:
On Tuesday, 3 February 2026 at 09:03:43 UTC, ketmar wrote:

 On Tuesday, 3 February 2026 at 03:33:04 UTC, pouyathe wrote:

 The current mess is not the final vision, just the starting 
 point.


 so, you wrote a barely working mess (and why it is on version 
 5+ then?), created a site for it (i see, problems with internet 
 access, so the site is a must, of course), and started to 
 promote your "product" by pushing it into lists and writing 
 articles.

 nowhere in dev.to artictle you wrote that this is just a 
 beginners attempt made for learning. you said that it is used 
 in "production", it is ready for such use, and you even 
 versioned it as "5.x", to make it look mature.

 and when people started asking questions, you quickly 
 backpedaled and begin making excuses. now you are looking even 
 worser.

 ah, and before you try to make some more calls to your bad 
 living conditions: i am living in Ukraine, i not only have 
 blackouts, there is a real full-scale war here going for 4 
 years. so your excuses will not work on me, try to invent 
 something better.

 p.s.: btw, 2.4MB binary is HUGE. my optimising Scheme compiler 
 with various libraries is only 1.4MB, and it is fully featured 
 programming language, i wrote several video games with it.

 i also looked at your source code, and it is not only bad, i 
 immediately spot several bugs, even without trying. those bugs 
 should not survive v0.0.0.1-prealpha, how come they managed to 
 make it to version 5+?

 can we take a look at the first PoC, v1, v2, v3 and v4, please? 
 or it is simply started as "version 5" because you tried to 
 sell it as some mature thing?


Subject: About survival, not versions

ketmar,

You asked about versions and bugs. Let me tell you about survival.

**I'm Afghan. In Iran. 17 years old.**

When I connect to the internet, I don't know how long it will 
last.
When I code, I don't know if I'll survive tomorrow just for being 
Afghan.

**v5.7.7 means:** I survived to rewrite this 5 times.
**The bugs mean:** I'm learning while running from danger.
**The 2.4MB means:** It runs in the moments between fear.

You fight for Ukraine's survival with rockets.
I fight for my survival with code.

**About my country Afghanistan:**
People say everything about Afghans.
But I still love my country.
Even when it hurts to love it.

**What I'm fixing:**
I'll make the binary smaller.
I'll fix the bugs you found.
Not because the code deserves it.
Because I survived to improve it.

**The version stays v5.7.7:**
It's not about software maturity.
It's about how many times I didn't quit while surviving.

Alive today,
An Afghan teenager who still codes
Feb 03
parent David T. Oxygen <TKC847567 outlook.com> writes:
On Tuesday, 3 February 2026 at 10:15:26 UTC, pouyathe wrote:

 **I'm Afghan. In Iran. 17 years old.**

 When I connect to the internet, I don't know how long it will 
 last.
 When I code, I don't know if I'll survive tomorrow just for 
 being Afghan.

 **v5.7.7 means:** I survived to rewrite this 5 times.
 **The bugs mean:** I'm learning while running from danger.
 **The 2.4MB means:** It runs in the moments between fear.

 You fight for Ukraine's survival with rockets.
 I fight for my survival with code.

 **About my country Afghanistan:**
 People say everything about Afghans.
 But I still love my country.
 Even when it hurts to love it.

 **What I'm fixing:**
 I'll make the binary smaller.
 I'll fix the bugs you found.
 Not because the code deserves it.
 Because I survived to improve it.

 **The version stays v5.7.7:**
 It's not about software maturity.
 It's about how many times I didn't quit while surviving.

 Alive today,
 An Afghan teenager who still codes



--


Hello Pouya,
good morning.

I looked through [https://glang.ct.ws/](https://glang.ct.ws/) 
about G Language and was so surprised about it. In a country 
which doesn't have stable Internet (even without stable 
electricity),it was truly difficult to build such a big project 
without good learning materials.
I'm also a teenager,who is younger than you.I've also tried to 
make my own programming language in D,but I just made an toy 
because 1)I don't have many experiences 2)I don't have much spare 
time.

Someone thinks there are bugs in your source code. I've 
downloaded it. Unluckily,I can't try G on my Windows computer. 
But I looked through the source code. I tried to compile it on 
Windows but I can't. I got a compiler error and I didn't know why.
It's true that your code seems messy. There are some strange 
names in your code without comments. It's worth fixing.
Although the code seems a little messy, you really did well in a 
difficult situation. And your story was so moving. **It became an 
encouragement for me.**

**Wish you success,and wish for the peace in Afghanistan and 
Iran.**


David T. Oxygen *(pseudonym)*
Feb 03
prev sibling next sibling parent Kapendev <alexandroskapretsos gmail.com> writes:
On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": 
 https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


The code is simple and I did compile it. The part I checked was 
fine.
I do think though that it would be better if some of the 
executables got replaced with instructions about how to build 
those executables. Or even removing some entirely, because from 
my experience they weren't needed. Anyway, hope it helps.
Feb 02
prev sibling next sibling parent pouyathe <pouya.momhidei gmail.com> writes:
On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": 
 https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


Hello Sönke and everyone,

My response is late due to my timezone - I'm based in Iran.

Your comment was correct—the code was full of empty functions and 
appeared non-functional. However, the reason is not that the 
project is "AI slop." The reason is that I wrote this interpreter 
with very limited internet access and no AI assistance.

I live in Iran. Here:

     Access to AI tools like ChatGPT is often blocked or requires 
payment, which isn't feasible for me.

     Internet connectivity is unstable, forcing me to code offline 
much of the time.

When I say "I wrote it," I mean I built it from scratch, through 
trial and error. The code is messy because I was learning in a 
vacuum. The empty functions were personal notes to 
myself—placeholders for logic I planned to complete later, 
whenever I might have a reliable connection to look things up.

This project is the real effort of one person building something 
with severely limited resources.

I have updated the README to clearly state this context. I fully 
understand the code needs a fundamental refactor, and I am now 
working on it with this new clarity.

If anyone is willing to offer technical guidance—not based on 
what I've built so far, but on my determination to build under 
difficult circumstances—I would gratefully accept it.

Sincerely,
Pouya
Feb 02
prev sibling next sibling parent reply pouyathe <pouya.momhidei gmail.com> writes:
On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": 
 https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


Subject: Re: Concerns about G Language code quality

Hi Sönke,

Thank you for reviewing the code. I understand your concerns 
about code quality.

To address your specific points:

     1. **"AI-generated slop" accusation:**
        The unconventional variable names (like friend names) come 
from:
        - My personal coding style (I'm 17, learning)
        - Coding during difficult conditions (power outages, 
limited time)
        - Not from AI - AI would generate more consistent, 
"professional" names

     2. **"No real functionality":**
        G Language has working functionality:
        - File I/O operations
        - System command execution
        - Variable management
        - Network server (basic HTTP)
        - Package manager (flex)
        Examples in repository: system_info.g, webserver.g

     3. **"Malware suspicion":**
        The entire source is available for review. There is no:
        - Network calls to suspicious domains
        - File system damage operations
        - Obfuscated code
        - Privilege escalation attempts
        You can audit any function.

I acknowledge the code needs improvement in:
- Consistent naming conventions
- Better error handling
- More comprehensive testing
- Documentation

I'm working on v5.7.7 with:
- Dead code removal
- Bug fixes
- Size reduction
- Better code organization

The project is a learning effort, not production-ready. I 
appreciate technical feedback to improve it.

Best regards,
Pouya Mohammadi
Feb 03
next sibling parent reply ketmar <ketmar ketmar.no-ip.org> writes:
On Tuesday, 3 February 2026 at 14:53:51 UTC, pouyathe wrote:

 The project is a learning effort, not production-ready.


oh… let's take a look at 
https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-m
-24mb-language-37ki then — the link you posted yourself.

quote:
"Is this "production ready"? It's ready for the productions I use 
it in."

no single word about "learning effort" there. and very evasive 
non-answer about G being production ready.

just in case something will… well… mysteriously change or 
disappear there, i took webarchive snapshot of that page. you 
know, for preservation purposes.

and while i am at it… "GNU G", really? can i see a link to GNU 
project page featuring G?

p.s.: it is amazing how fast you answer in this thread for 
somebody with limited internet access.
Feb 03
next sibling parent reply pouyathe <pouya.momhidei gmail.com> writes:
On Tuesday, 3 February 2026 at 15:11:25 UTC, ketmar wrote:

 On Tuesday, 3 February 2026 at 14:53:51 UTC, pouyathe wrote:

 The project is a learning effort, not production-ready.


 oh… let's take a look at 
 https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-m
-24mb-language-37ki then — the link you posted yourself.

 quote:
 "Is this "production ready"? It's ready for the productions I 
 use it in."

 no single word about "learning effort" there. and very evasive 
 non-answer about G being production ready.

 just in case something will… well… mysteriously change or 
 disappear there, i took webarchive snapshot of that page. you 
 know, for preservation purposes.

 and while i am at it… "GNU G", really? can i see a link to GNU 
 project page featuring G?

 p.s.: it is amazing how fast you answer in this thread for 
 somebody with limited internet access.


ketmar,

You're right about:
1. "GNU G" - removing it now
2. "Production ready" - clarifying in article
3. Code quality - fixing bugs you found

Thanks for the technical review.
Feb 03
parent reply ketmar <ketmar ketmar.no-ip.org> writes:
On Tuesday, 3 February 2026 at 18:14:59 UTC, pouyathe wrote:

 Thanks for the technical review.


no, it wasn't any kind of technical review. but you keep ignoring 
obvious questions. anyway, i am still not finished with you. let 
me quote you once again:

"Access to AI tools like ChatGPT is often blocked or requires 
payment, which isn't feasible for me."

more lies from you. this: 
https://forum.dlang.org/thread/mqivmzhifvnzdwbycbvw forum.dlang.org — is
clearly generated with ai. and at least some (if not all) your answers. do you
really think that people are blind and dumb?
Feb 03
next sibling parent ketmar <ketmar ketmar.no-ip.org> writes:
p.s.: oops. sorry for messed formatting.
Feb 03
prev sibling parent reply pouyathe <pouya.momhidei gmail.com> writes:
On Wednesday, 4 February 2026 at 05:40:44 UTC, ketmar wrote:

 On Tuesday, 3 February 2026 at 18:14:59 UTC, pouyathe wrote:

 Thanks for the technical review.


 no, it wasn't any kind of technical review. but you keep 
 ignoring obvious questions. anyway, i am still not finished 
 with you. let me quote you once again:

 "Access to AI tools like ChatGPT is often blocked or requires 
 payment, which isn't feasible for me."

 more lies from you. this: 
 https://forum.dlang.org/thread/mqivmzhifvnzdwbycbvw forum.dlang.org — is
clearly generated with ai. and at least some (if not all) your answers. do you
really think that people are blind and dumb?


Again Hi ketmar,
I use Iranian AI whose link is this: https://ivira.ai/
And maybe it will open in your country because usually it's only 
available in Iran.
I'm honestly not very good at English, that's why I write my 
articles with it.
And I don't have money to give to this AI tool, I use its limited 
and free version.
Which isn't connected to the global internet and can't work with 
specific languages like D.

And I also thank you for talking with me, this was an honor for 
me, thank you very much.
I've never talked with people outside Iran and from Europe and 
the world before.
And until now I haven't been active in programming communities 
either.
If I make mistakes, it's because of my inexperience and because 
I'm new to the global community.

I know you're also an excellent programmer and definitely code 
thousands of times better than me.
And it's truly an honor for me that you point out my mistakes to 
me and I learn from you.
I hope you have a good day or night.
Feb 04
parent reply ketmar <ketmar ketmar.no-ip.org> writes:
On Wednesday, 4 February 2026 at 08:10:08 UTC, pouyathe wrote:

 If I make mistakes, it's because of my inexperience and because 
 I'm new to the global community.


nope. i'm not buying it. there is a huge difference between being 
inexpirienced and hyping yourself. you very well know what you're 
doing. you ignored all real concerns i voiced like they simply 
don't exist, and cherry-picked only the things you can answer 
without making you look even slightly wrong. and you "answered" 
to those things completely out of context. this is NOT a 
coincidence, this is conscious choice. you keep acting as if all 
other people around you are blind and dumb. this is insulting. 
and no, your flattery will not work.

people who want to learn are not hyping their learning efforts 
like it's the best thing since sliced bread. you haven't even 
admited that "G" is a throwaway thing you used to learn the 
basics until you was pressed hard. this is called "self-hyping", 
and then you fall back to damage control mode. nobody's doing 
things like that (and in that order) by accident.

but i'm done with you. you definitely won't going to admit your 
mistakes, apologise, and change the way you're acting. i tried to 
put you back on tracks, but it looks like you've never been on 
the tracks at all.
Feb 04
parent pouyathe <pouya.momhidei gmail.com> writes:
On Wednesday, 4 February 2026 at 08:43:21 UTC, ketmar wrote:

 On Wednesday, 4 February 2026 at 08:10:08 UTC, pouyathe wrote:

 If I make mistakes, it's because of my inexperience and 
 because I'm new to the global community.


 nope. i'm not buying it. there is a huge difference between 
 being inexpirienced and hyping yourself. you very well know 
 what you're doing. you ignored all real concerns i voiced like 
 they simply don't exist, and cherry-picked only the things you 
 can answer without making you look even slightly wrong. and you 
 "answered" to those things completely out of context. this is 
 NOT a coincidence, this is conscious choice. you keep acting as 
 if all other people around you are blind and dumb. this is 
 insulting. and no, your flattery will not work.

 people who want to learn are not hyping their learning efforts 
 like it's the best thing since sliced bread. you haven't even 
 admited that "G" is a throwaway thing you used to learn the 
 basics until you was pressed hard. this is called 
 "self-hyping", and then you fall back to damage control mode. 
 nobody's doing things like that (and in that order) by accident.

 but i'm done with you. you definitely won't going to admit your 
 mistakes, apologise, and change the way you're acting. i tried 
 to put you back on tracks, but it looks like you've never been 
 on the tracks at all.


I get it, thanks.

History repeats itself: PHP was just a bunch of simple scripts, 
Go was built for Google's internal problems.

Anything new is ridiculed at first.

I pay attention to technical comments, I listen to constructive 
criticism, I ignore the rest.

And I don't stop - I keep learning.

Thanks for your time.
Feb 04
prev sibling parent Kapendev <alexandroskapretsos gmail.com> writes:
On Tuesday, 3 February 2026 at 15:11:25 UTC, ketmar wrote:

 and while i am at it… "GNU G", really? can i see a link to GNU 
 project page featuring G?

 p.s.: it is amazing how fast you answer in this thread for 
 somebody with limited internet access.


I didn't know it was also on the website of this project. First 
time I noticed GNU being used was on the language itself when 
running it. When I asked about it, I got an answer like: "it's an 
inside joke of the project lol"

Well... I tried to be nice and keep an open mind, but using the 
GNU name all over the place starts to look weird and misleading.
Feb 03
prev sibling parent reply =?UTF-8?Q?S=C3=B6nke_Ludwig?= <sludwig outerproduct.org> writes:
Okay, assuming you are actually trying to build a language and this is 
not just some kind of social engineering situation, then you should 
seriously consider approaching this a bit differently:

- Don't include any obscure executable binaries into the repository¹.

- Instead of letting a chat bot write answers and articles for you, 
write them yourself and, *if necessary*, use AI just for pure 
translation or for correcting grammar/spelling errors. All of the text 
and graphics being clearly generated by AI does not make this credible. 
And even with good intentions, AI is very likely to insert hallucinated 
information.

- The extremely deeply nested command line and script parsing code¹ in 
combination with a more advanced language like D just feels very 
unexpected to me. If you actually wrote that by hand, you should really 
try to learn about more general approaches. Some existing implementations:

     - Command line parsing: 
https://dlang.org/library/std/getopt/getopt.html
     - Code parsing: 
https://github.com/dlang-community/Pegged/blob/master/examples/arithmetic/src/pegged/examples/arithmetic.d
     - Also look for "recursive descent parsing" for a way to write an 
expression parser by hand

- Wait with the big marketing until the project actually in use by at 
least a few people.

Speaking of hallucinated information - here you are saying that you are 
17, whereas it says 18 on your GitHub profile. Things like this and the 
"GNU G"/"Copyright (C) 2026 Free Software Foundation" also don't create 
trust.


¹ Another example of an obscure binary is the "fuchsia" binary in the 
repository with the same name that, AFAICS, will be "sudo" copied to 
"/usr/bin" when running "flex build". This, at the very least, is very 
bad practice (not actually "building" anything, but instead *installing* 
with root privileges, using /usr/bin for non-distro files). But it also 
resembles a possible attempt to get malicious code installed in the system.


Am 03.02.26 um 15:53 schrieb pouyathe:

 On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big pile of 
 AI slop with no real functionality (just like the newsgroup post 
 itself). As an example, look at the "source code": https://github.com/ 
 pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, although I 
 haven't looked into that.


 
 Subject: Re: Concerns about G Language code quality
 
 Hi Sönke,
 
 Thank you for reviewing the code. I understand your concerns about code 
 quality.
 
 To address your specific points:
 
      1. **"AI-generated slop" accusation:**
         The unconventional variable names (like friend names) come from:
         - My personal coding style (I'm 17, learning)
         - Coding during difficult conditions (power outages, limited
time)
         - Not from AI - AI would generate more consistent, 
 "professional" names
 
      2. **"No real functionality":**
         G Language has working functionality:
         - File I/O operations
         - System command execution
         - Variable management
         - Network server (basic HTTP)
         - Package manager (flex)
         Examples in repository: system_info.g, webserver.g
 
      3. **"Malware suspicion":**
         The entire source is available for review. There is no:
         - Network calls to suspicious domains
         - File system damage operations
         - Obfuscated code
         - Privilege escalation attempts
         You can audit any function.
 
 I acknowledge the code needs improvement in:
 - Consistent naming conventions
 - Better error handling
 - More comprehensive testing
 - Documentation
 
 I'm working on v5.7.7 with:
 - Dead code removal
 - Bug fixes
 - Size reduction
 - Better code organization
 
 The project is a learning effort, not production-ready. I appreciate 
 technical feedback to improve it.
 
 Best regards,
 Pouya Mohammadi
Feb 04
parent pouyathe <pouya.momhidei gmail.com> writes:
On Wednesday, 4 February 2026 at 09:17:35 UTC, Sönke Ludwig wrote:

 Okay, assuming you are actually trying to build a language and 
 this is not just some kind of social engineering situation, 
 then you should seriously consider approaching this a bit 
 differently:

 - Don't include any obscure executable binaries into the 
 repository¹.

 - Instead of letting a chat bot write answers and articles for 
 you, write them yourself and, *if necessary*, use AI just for 
 pure translation or for correcting grammar/spelling errors. All 
 of the text and graphics being clearly generated by AI does not 
 make this credible. And even with good intentions, AI is very 
 likely to insert hallucinated information.

 - The extremely deeply nested command line and script parsing 
 code¹ in combination with a more advanced language like D just 
 feels very unexpected to me. If you actually wrote that by 
 hand, you should really try to learn about more general 
 approaches. Some existing implementations:

     - Command line parsing: 
 https://dlang.org/library/std/getopt/getopt.html
     - Code parsing: 
 https://github.com/dlang-community/Pegged/blob/master/examples/arithmetic/src/pegged/examples/arithmetic.d
     - Also look for "recursive descent parsing" for a way to 
 write an expression parser by hand

 - Wait with the big marketing until the project actually in use 
 by at least a few people.

 Speaking of hallucinated information - here you are saying that 
 you are 17, whereas it says 18 on your GitHub profile. Things 
 like this and the "GNU G"/"Copyright (C) 2026 Free Software 
 Foundation" also don't create trust.


 ¹ Another example of an obscure binary is the "fuchsia" binary 
 in the repository with the same name that, AFAICS, will be 
 "sudo" copied to "/usr/bin" when running "flex build". This, at 
 the very least, is very bad practice (not actually "building" 
 anything, but instead *installing* with root privileges, using 
 /usr/bin for non-distro files). But it also resembles a 
 possible attempt to get malicious code installed in the system.


 Am 03.02.26 um 15:53 schrieb pouyathe:

 On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": https://github.com/ 
 pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


 
 Subject: Re: Concerns about G Language code quality
 
 Hi Sönke,
 
 Thank you for reviewing the code. I understand your concerns 
 about code quality.
 
 To address your specific points:
 
      1. **"AI-generated slop" accusation:**
         The unconventional variable names (like friend names) 
 come from:
         - My personal coding style (I'm 17, learning)
         - Coding during difficult conditions (power outages, 
 limited time)
         - Not from AI - AI would generate more consistent, 
 "professional" names
 
      2. **"No real functionality":**
         G Language has working functionality:
         - File I/O operations
         - System command execution
         - Variable management
         - Network server (basic HTTP)
         - Package manager (flex)
         Examples in repository: system_info.g, webserver.g
 
      3. **"Malware suspicion":**
         The entire source is available for review. There is no:
         - Network calls to suspicious domains
         - File system damage operations
         - Obfuscated code
         - Privilege escalation attempts
         You can audit any function.
 
 I acknowledge the code needs improvement in:
 - Consistent naming conventions
 - Better error handling
 - More comprehensive testing
 - Documentation
 
 I'm working on v5.7.7 with:
 - Dead code removal
 - Bug fixes
 - Size reduction
 - Better code organization
 
 The project is a learning effort, not production-ready. I 
 appreciate technical feedback to improve it.
 
 Best regards,
 Pouya Mohammadi




Thank you so much for the feedback. I'm somewhat new to writing 
documentation. Those copyright texts were actually written by me 
for myself - I've already removed them in newer versions since 
users are using the language, and for future versions, I won't 
include any binaries and will focus on source compilation instead.

I used AI for writing articles because I'm not very good at 
writing articles myself. From now on, I'll try to write 
everything myself.
  Yes, I wrote "18" on GitHub because I didn't want people to 
think I'm just a kid or a student building something trivial. 
I've corrected this to my actual age (17).
I'm still learning and appreciate the guidance. The project is 
genuine - I'm just inexperienced with open-source practices. 
Thank you for your explanations and help.
Feb 04
prev sibling parent Quirin Schroll <qs.il.paperinik gmail.com> writes:
On Monday, 2 February 2026 at 18:26:14 UTC, Sönke Ludwig wrote:

 Looking at the project, this appears to be nothing but a big 
 pile of AI slop with no real functionality (just like the 
 newsgroup post itself). As an example, look at the "source 
 code": 
 https://github.com/pouyathe/glang/blob/main/source/oda/source/code/glang_foroda.d

 My suspicion would be that the repository contains malware, 
 although I haven't looked into that.


Yeah, I looked into [the file 
(permalink)](https://github.com/pouyathe/glang/blob/2ec1121cb079432ee84c2d9047e6a5987fc442ac/source/oda/source/c
de/glang_foroda.d), and I can say with reasonable confidence that no human
writes code like that. The else/ifs look like a bad disassembler.
Feb 04
prev sibling next sibling parent reply Dejan Lekic <dejan.lekic gmail.com> writes:
On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 G is a minimalist, memory-safe interpreter for systems 
 scripting with a footprint of about 2.4MB. The entire toolchain 
 is written in D.

 Recently, it was accepted into the awesome-d list. I also wrote 
 an article about the experience of building it and getting 
 feedback from Walter Bright: [When Walter Bright Told Me to 
 Write About My 2.4MB Language (cross-posted on 
 Dev.to)](https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-my-24mb-language-37ki).

 I'm sharing this here for two reasons: first, to say thank you 
 to the D community and ecosystem that made it possible, and 
 second, in case anyone is curious about a non-trivial use of D 
 for building language tools.

 I would be very grateful for any feedback, technical insights, 
 or questions from the community that understands the foundation 
 it's built upon.


Thank you very much for this wonderful gift from the Heaven! I 
love G so much that I am planning to replace all my Python 
scripts with G, once it has adequate standard library modules! :) 
Are you planning to add more to std? You should add 
sqlalchemy-like package so that I can access databases from G as 
well. Can't wait! Keep up with the good work. I hope you will 
also make it possible to embed G in our D applications and just 
like pyd we would be able to call G stuff from D code, and vice 
versa.
Feb 03
parent pouyathe <pouya.momhidei gmail.com> writes:
On Tuesday, 3 February 2026 at 12:13:43 UTC, Dejan Lekic wrote:

 On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 G is a minimalist, memory-safe interpreter for systems 
 scripting with a footprint of about 2.4MB. The entire 
 toolchain is written in D.

 Recently, it was accepted into the awesome-d list. I also 
 wrote an article about the experience of building it and 
 getting feedback from Walter Bright: [When Walter Bright Told 
 Me to Write About My 2.4MB Language (cross-posted on 
 Dev.to)](https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-my-24mb-language-37ki).

 I'm sharing this here for two reasons: first, to say thank you 
 to the D community and ecosystem that made it possible, and 
 second, in case anyone is curious about a non-trivial use of D 
 for building language tools.

 I would be very grateful for any feedback, technical insights, 
 or questions from the community that understands the 
 foundation it's built upon.


 Thank you very much for this wonderful gift from the Heaven! I 
 love G so much that I am planning to replace all my Python 
 scripts with G, once it has adequate standard library modules! 
 :) Are you planning to add more to std? You should add 
 sqlalchemy-like package so that I can access databases from G 
 as well. Can't wait! Keep up with the good work. I hope you 
 will also make it possible to embed G in our D applications and 
 just like pyd we would be able to call G stuff from D code, and 
 vice versa.


Dear Dejan,

Thank you so much for your kind words about G Language! It means 
a lot to me, especially coming from someone in the D community 
that I respect.

You raised excellent points about what G needs:

1. **Standard Library Expansion** - You're absolutely right. I'm 
prioritizing:
    - Database connectivity (starting with SQLite, then PostgreSQL)
    - JSON/XML parsing modules
    - HTTP client for web APIs
    - File format utilities (CSV, etc.)

2. **Embedding API** - This is a fantastic idea. I'm researching:
    - How to expose G as a D library
    - Bidirectional calling (D ↔ G)
    - Memory sharing between environments

3. **Package Ecosystem** - I'll enhance `flex` to support:
    - More library categories
    - Better dependency management
    - Community package repository


I'm working on v5.7.7 with:
- Binary size reduction (target: <1.5MB)
- Bug fixes from community feedback
- Better error messages
- Performance improvements


If you were to use G today, what specific task would you want to 
accomplish with it? This would help me prioritize features.

Thank you again for believing in this project. Feedback from 
experienced D developers like you is invaluable for a young 
language.

Best regards,
Pouya Mohammadi
Creator of G Language

P.S. If you'd like to contribute ideas or code, the repo is at: 
https://github.com/pouyathe/glang
Feb 03
prev sibling next sibling parent reply Dejan Lekic <dejan.lekic gmail.com> writes:
On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 G is a minimalist, memory-safe interpreter for systems 
 scripting with a footprint of about 2.4MB. The entire toolchain 
 is written in D.

 Recently, it was accepted into the awesome-d list. I also wrote 
 an article about the experience of building it and getting 
 feedback from Walter Bright: [When Walter Bright Told Me to 
 Write About My 2.4MB Language (cross-posted on 
 Dev.to)](https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-my-24mb-language-37ki).



It seems like world-wide adoption of the G programming language 
have already started. Balter is writing a book about it:

![The G Programming 
Language](https://gcdnb.pbrd.co/images/EpngRl1MPFEQ.png?o=1)

I think he picked the goat because

- starts with G
- meaning G is the G.O.A.T of programming languages
Feb 04
parent David T. Oxygen <TKC847567 outlook.com> writes:
On Wednesday, 4 February 2026 at 12:02:47 UTC, Dejan Lekic wrote:

 It seems like world-wide adoption of the G programming language 
 have already started. Balter is writing a book about it:

 ![The G Programming 
 Language](https://gcdnb.pbrd.co/images/EpngRl1MPFEQ.png?o=1)


--

Who is Balter Wright?
Feb 04
prev sibling parent reply pouyathe <pouya.momhidei gmail.com> writes:
On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 G is a minimalist, memory-safe interpreter for systems 
 scripting with a footprint of about 2.4MB. The entire toolchain 
 is written in D.

 Recently, it was accepted into the awesome-d list. I also wrote 
 an article about the experience of building it and getting 
 feedback from Walter Bright: [When Walter Bright Told Me to 
 Write About My 2.4MB Language (cross-posted on 
 Dev.to)](https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-my-24mb-language-37ki).

 I'm sharing this here for two reasons: first, to say thank you 
 to the D community and ecosystem that made it possible, and 
 second, in case anyone is curious about a non-trivial use of D 
 for building language tools.

 I would be very grateful for any feedback, technical insights, 
 or questions from the community that understands the foundation 
 it's built upon.

 Best regards,
 Pouya Mohammadi
 [github](https://github.com/pouyathe/glang)


A new version has been released.
Thank you to the D community for the help you gave me.
I tried to include all the problems and tasks you mentioned in 
the version. I hope you use it and have no problems.
I also cleaned up the code a bit, but there is still work to be 
done.
[github](https://github.com/pouyathe/glang0
Feb 04
parent pouyathe <pouya.momhidei gmail.com> writes:
On Wednesday, 4 February 2026 at 19:23:44 UTC, pouyathe wrote:

 On Sunday, 1 February 2026 at 17:48:34 UTC, pouyathe wrote:

 Hello D Community,

 I wanted to share a project I've been working on that might be 
 of interest: the G Language.

 G is a minimalist, memory-safe interpreter for systems 
 scripting with a footprint of about 2.4MB. The entire 
 toolchain is written in D.

 Recently, it was accepted into the awesome-d list. I also 
 wrote an article about the experience of building it and 
 getting feedback from Walter Bright: [When Walter Bright Told 
 Me to Write About My 2.4MB Language (cross-posted on 
 Dev.to)](https://dev.to/pouyathe/when-walter-bright-told-me-to-write-about-my-24mb-language-37ki).

 I'm sharing this here for two reasons: first, to say thank you 
 to the D community and ecosystem that made it possible, and 
 second, in case anyone is curious about a non-trivial use of D 
 for building language tools.

 I would be very grateful for any feedback, technical insights, 
 or questions from the community that understands the 
 foundation it's built upon.

 Best regards,
 Pouya Mohammadi
 [github](https://github.com/pouyathe/glang)


 A new version has been released.
 Thank you to the D community for the help you gave me.
 I tried to include all the problems and tasks you mentioned in 
 the version. I hope you use it and have no problems.
 I also cleaned up the code a bit, but there is still work to be 
 done.
 [github](https://github.com/pouyathe/glang0


sorry for link problom
https://github.com/pouyathe/glang
Feb 04