Dowe - Full-stack language for server, web, desktop, Android, and iOS
Show HN: Dowe – A full-stack language for server, web, desktop, Android, and iOS
Dowe is a revolutionary full-stack language designed for the AI era, transforming a single declarative source into verified software across server, web, desktop, Android, and iOS platforms. Unlike traditional stacks, Dowe embeds architecture directly into the source, allowing AI agents to edit intent while the compiler ensures system coherence. It generates native outputs like Jetpack Compose and SwiftUI from one unified model, eliminating the need for ambient Node.js runtimes. By validating contracts and boundaries automatically, Dowe makes the path from agent edits to platform artifacts visible, deterministic, and reviewable, enabling developers to build the entire system rather than just managing a stack.
AI generates code. Dowe generates the system.
- survirtual
I 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.
Also, 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 m […]
- nirvdrum
It's an interesting idea, but it's hard to tell what the native parts are. The home page has a section titled "Native Targets" with an arrow icon that looks like it'd go to some docs, but appears to just be an icon. The running example is a straightforward responsive web page. The docs are centered around UI components for this tool and the lack of a Tree component really makes it look like this is a web framework.
Does it actually generate a native mobile or desktop application? I probably overlooked it, but I couldn't find an example app to build and experiment with locally.
- hyperhello
If you can’t even make the web page yourself, what am I supposed to conclude about your web language?