HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pouyathe
glang
HISTORICAL RECORD2026–2026
pouyathe / glang · Not publicly available

glang

Discover this repository through its Hacker News conversations.

5Distinct people
5Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval5 dated mentions

Observed mentions: 2026-01-30 13:56:04 UTC to 2026-02-03 09:14:17 UTC.

012026-01-30 12:00:00 UTC to 2026-01-30 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 30, 12:002026-01-30 15:00:00 UTC to 2026-01-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-30 18:00:00 UTC to 2026-01-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-30 21:00:00 UTC to 2026-01-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 00:00:00 UTC to 2026-01-31 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 03:00:00 UTC to 2026-01-31 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-01-31 06:00:00 UTC to 2026-01-31 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 09:00:00 UTC to 2026-01-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 12:00:00 UTC to 2026-01-31 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 15:00:00 UTC to 2026-01-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 18:00:00 UTC to 2026-01-31 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-31 21:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-02-01 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 03:00:00 UTC to 2026-02-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 06:00:00 UTC to 2026-02-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 09:00:00 UTC to 2026-02-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 1, 09:002026-02-01 12:00:00 UTC to 2026-02-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 15:00:00 UTC to 2026-02-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 18:00:00 UTC to 2026-02-01 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 21:00:00 UTC to 2026-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 00:00:00 UTC to 2026-02-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 03:00:00 UTC to 2026-02-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 06:00:00 UTC to 2026-02-02 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 09:00:00 UTC to 2026-02-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 12:00:00 UTC to 2026-02-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 15:00:00 UTC to 2026-02-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 18:00:00 UTC to 2026-02-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-02 21:00:00 UTC to 2026-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-03 00:00:00 UTC to 2026-02-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-03 03:00:00 UTC to 2026-02-03 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-02-03 06:00:00 UTC to 2026-02-03 09:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-03 09:00:00 UTC to 2026-02-03 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 3, 09:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 30, 12:002026-01-30 12:00:00 UTC2026-01-30 15:00:00 UTC110
Jan 30, 15:002026-01-30 15:00:00 UTC2026-01-30 18:00:00 UTC000
Jan 30, 18:002026-01-30 18:00:00 UTC2026-01-30 21:00:00 UTC000
Jan 30, 21:002026-01-30 21:00:00 UTC2026-01-31 00:00:00 UTC000
Jan 31, 00:002026-01-31 00:00:00 UTC2026-01-31 03:00:00 UTC000
Jan 31, 03:002026-01-31 03:00:00 UTC2026-01-31 06:00:00 UTC110
Jan 31, 06:002026-01-31 06:00:00 UTC2026-01-31 09:00:00 UTC000
Jan 31, 09:002026-01-31 09:00:00 UTC2026-01-31 12:00:00 UTC000
Jan 31, 12:002026-01-31 12:00:00 UTC2026-01-31 15:00:00 UTC000
Jan 31, 15:002026-01-31 15:00:00 UTC2026-01-31 18:00:00 UTC000
Jan 31, 18:002026-01-31 18:00:00 UTC2026-01-31 21:00:00 UTC000
Jan 31, 21:002026-01-31 21:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 1, 00:002026-02-01 00:00:00 UTC2026-02-01 03:00:00 UTC000
Feb 1, 03:002026-02-01 03:00:00 UTC2026-02-01 06:00:00 UTC000
Feb 1, 06:002026-02-01 06:00:00 UTC2026-02-01 09:00:00 UTC000
Feb 1, 09:002026-02-01 09:00:00 UTC2026-02-01 12:00:00 UTC000
Feb 1, 12:002026-02-01 12:00:00 UTC2026-02-01 15:00:00 UTC000
Feb 1, 15:002026-02-01 15:00:00 UTC2026-02-01 18:00:00 UTC000
Feb 1, 18:002026-02-01 18:00:00 UTC2026-02-01 21:00:00 UTC000
Feb 1, 21:002026-02-01 21:00:00 UTC2026-02-02 00:00:00 UTC000
Feb 2, 00:002026-02-02 00:00:00 UTC2026-02-02 03:00:00 UTC000
Feb 2, 03:002026-02-02 03:00:00 UTC2026-02-02 06:00:00 UTC000
Feb 2, 06:002026-02-02 06:00:00 UTC2026-02-02 09:00:00 UTC000
Feb 2, 09:002026-02-02 09:00:00 UTC2026-02-02 12:00:00 UTC000
Feb 2, 12:002026-02-02 12:00:00 UTC2026-02-02 15:00:00 UTC000
Feb 2, 15:002026-02-02 15:00:00 UTC2026-02-02 18:00:00 UTC000
Feb 2, 18:002026-02-02 18:00:00 UTC2026-02-02 21:00:00 UTC000
Feb 2, 21:002026-02-02 21:00:00 UTC2026-02-03 00:00:00 UTC000
Feb 3, 00:002026-02-03 00:00:00 UTC2026-02-03 03:00:00 UTC000
Feb 3, 03:002026-02-03 03:00:00 UTC2026-02-03 06:00:00 UTC101
Feb 3, 06:002026-02-03 06:00:00 UTC2026-02-03 09:00:00 UTC110
Feb 3, 09:002026-02-03 09:00:00 UTC2026-02-03 12:00:00 UTC101

What Hacker News says

5 sources
No offense, but the source code for this is wild. It's almost like outsider art. https://github.com/pouyathe/glang/blob/main/source/dub/sourc... Still, I have to respect the dedication it must have taken to get this working. I'm sure you'll go far. My advice to you would be to read Crafting Interpreters by Bob Nystrom (it's free online) and try to apply some of the techniques from it to your project. https://craftinginterpreters.com/
In G Lang – A lightweight interpreter written in D (2.4MB)
_pouya_·Jan 31, 2026Submission

Show HN: G – A fast, memory-safe language with a symbol-free syntax

Hi HN, I built G, a lightweight programming language written in D (with a Go interpreter available). It is designed to be memory-safe and super fast, with a tiny footprint (~2.4MB). The most unique aspect of G is its syntax. It doesn't use symbols for comments or complex punctuation for functions. It uses a stack-based approach (similar to concatenative languages) where arguments are passed before the function call. For example, defining an addition function looks like this: fn add_two [@] : + 2 It also comes with Flex, a built-in package manager to handle external libraries (sudo flex add <lib>). I’d love to get feedback on the syntax design and the interpreter architecture. GitHub: https://github.com/pouyathe/glang
1 points · Open discussion
pouyathe·Jan 30, 2026Submission

G Lang – A lightweight interpreter written in D (2.4MB)

Hi HN, I've been working on a programming language called G. It is designed to be memory-safe and extremely fast, with a focus on a tiny footprint. The entire interpreter is written in D and weighs in at only 2.4MB. I built it because I wanted a modern scripting language that feels lightweight but has the safety of a high-level language. Key Features: Small: The binary is ~2.4MB. Fast: Optimized for x86_64. Safe: Memory-safe execution. Std Lib: Includes std.echo, std.newline, etc. GitHub: https://github.com/pouyathe/glang I would love to get some feedback on the syntax or the architecture from the community!
35 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.