VIvictorriba·Jul 30, 2026Submission
Show HN: Full stack development from one codebase web, Android, and iOS
14 points · Open discussionusedowe
dowe-lang
HISTORICAL RECORD2026–2026
usedowe / dowe-lang · Not publicly available
dowe-lang
Discover this repository through its Hacker News conversations.
2Distinct people
2Mentions
0Explicit recommenders
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, 5:04:57 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 interval2 dated mentions
Observed mentions: 2026-07-28 00:38:23 UTC to 2026-07-30 00:34:19 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jul 28, 00:00 | 2026-07-28 00:00:00 UTC | 2026-07-28 03:00:00 UTC | 1 | 0 | 1 |
| Jul 28, 03:00 | 2026-07-28 03:00:00 UTC | 2026-07-28 06:00:00 UTC | 0 | 0 | 0 |
| Jul 28, 06:00 | 2026-07-28 06:00:00 UTC | 2026-07-28 09:00:00 UTC | 0 | 0 | 0 |
| Jul 28, 09:00 | 2026-07-28 09:00:00 UTC | 2026-07-28 12:00:00 UTC | 0 | 0 | 0 |
| Jul 28, 12:00 | 2026-07-28 12:00:00 UTC | 2026-07-28 15:00:00 UTC | 0 | 0 | 0 |
| Jul 28, 15:00 | 2026-07-28 15:00:00 UTC | 2026-07-28 18:00:00 UTC | 0 | 0 | 0 |
| Jul 28, 18:00 | 2026-07-28 18:00:00 UTC | 2026-07-28 21:00:00 UTC | 0 | 0 | 0 |
| Jul 28, 21:00 | 2026-07-28 21:00:00 UTC | 2026-07-29 00:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 00:00 | 2026-07-29 00:00:00 UTC | 2026-07-29 03:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 03:00 | 2026-07-29 03:00:00 UTC | 2026-07-29 06:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 06:00 | 2026-07-29 06:00:00 UTC | 2026-07-29 09:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 09:00 | 2026-07-29 09:00:00 UTC | 2026-07-29 12:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 12:00 | 2026-07-29 12:00:00 UTC | 2026-07-29 15:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 15:00 | 2026-07-29 15:00:00 UTC | 2026-07-29 18:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 18:00 | 2026-07-29 18:00:00 UTC | 2026-07-29 21:00:00 UTC | 0 | 0 | 0 |
| Jul 29, 21:00 | 2026-07-29 21:00:00 UTC | 2026-07-30 00:00:00 UTC | 0 | 0 | 0 |
| Jul 30, 00:00 | 2026-07-30 00:00:00 UTC | 2026-07-30 03:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesI can see this was largely AI written. There is nothing wrong with that, but how much did you test and vet what the AI wrote?
Looking at the compiler, it doesn't make much sense. You have an AST that is rather minimal and I can't seem to find an IR. There are files, such as cron.rs, which have very little code relating to what I would expect, and the tests seem to test very little that is worthwhile.
Some of these are absolute monsters, like this one:
https://github.com/usedowe/dowe-lang/blob/main/crates/compil...
The codebase seems tightly coupled and to cover specific cases, as if something was off and more features were requested. I think a 12k line file is evidence of that.
Perhaps it is a useful tool for you but I would have trouble using something like this with just my quick skim because it seems a mile wide and an inch deep.
A
Read the rest
lso, because of the sheer size of it, it would be extremely difficult to have an agent properly comprehend much if anything. Which I would want in order to audit the internals.
The language itself seems minimal, but then I look at the skills, like this one for example:
https://github.com/usedowe/dowe-lang/blob/main/skill-data/do...
That is a lot of tokens. The problem here is that you have a compiler; why are you encoding standards as a prompt instead of as compiler errors?
You can use linting and static analysis to force conformance with agents instead of suggesting with a prompt.
I wish you luck with the project. I'll have to pass, too much code for me to follow when I could simply have an agent directly write the html now days.