G Language (written in D) featured in awesome-d and awesome-programming-languages

pouyathe pouya.momhidei at gmail.com
Wed Feb 4 14:24:08 UTC 2026


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.


More information about the Digitalmars-d mailing list