EYG: New Statically Typed Language for Glue Code
28 Jul 2026
A Visa Wait Becomes a Language Launch
Sometimes side projects come from unexpected downtime. According to the report, the creator of a new programming language called EYG began building it during a 10-week wait for a visa to start a new job in Sweden. The project was announced publicly via a post dated June 8, 2026.
EYG is a statically typed functional programming language inspired by Gleam, another statically typed functional language. But rather than competing for general-purpose programming mindshare, EYG is explicitly aimed at what its creator calls "human" programming problems: glue code, personal dashboards, and automations.
What Makes EYG Different
According to the report, EYG borrows structure from Gleam but diverges in a key way: EYG is nominally typed, while Gleam is structurally typed. This distinction could matter for developers moving between the two languages, as nominal typing enforces type identity by name rather than by shape — a difference that may introduce friction for those used to structural systems.
Another notable design choice is EYG's dependency model. Rather than relying on traditional package managers, EYG defines dependencies inline, identified by the hash of a module's contents. This hash-based approach is unconventional and may require developers to adjust their existing workflows.
EYG also incorporates effect typing, a system that captures side effects directly in the type system. The report notes this could help catch side-effect-related bugs earlier in the development process, though no technical implementation details are provided.
In a nod to the practical, human-centered philosophy behind the language, its creator has been quoted noting that the average human response to integer overflows is "WTF, that's not how numbers work." The report also draws a comparison to Excel, noting that Excel "completely solves the problem of deploying and running macros for end user programmers" — though the connection between this comparison and EYG's own deployment model isn't elaborated in the source material.
Why Founders Should Care
For early-stage founders evaluating lightweight tooling for internal automation, dashboards, or glue code between systems, EYG's stated focus may be worth watching. The effect-typing system could plausibly reduce certain classes of runtime bugs, though this remains unproven at scale — no adoption data, production usage figures, or performance benchmarks are currently available.
Founders considering EYG for anything beyond experimentation should weigh ecosystem risk carefully. As a newly created language, EYG likely lacks the mature tooling, libraries, and community support that founders typically rely on when adopting a language for production systems. The nominal typing difference from Gleam may also create friction for teams with structural-typing backgrounds, and the inline hash-based dependency model represents a workflow shift that teams would need to evaluate for compatibility with existing development pipelines.
In short, EYG's design choices suggest an interesting niche — automations and glue code for non-specialist programmers — but the lack of release version, licensing details, or roadmap information means it's likely too early to assess for production use.
What's Still Unknown
Several important details remain unaddressed in current reporting: there's no information on EYG's current adoption or user base, no specifics on versioning or licensing, and no comparative data on performance or tooling maturity relative to Gleam or other languages. Founders intrigued by the concept should treat EYG as an early-stage experiment rather than a ready-to-adopt tool, at least until more concrete adoption and technical details emerge.