Eco is an independently developed Elm compiler project with its own architecture, implementation history and technical objectives.
Some similarities have been drawn between Eco and other projects in the Elm ecosystem, particularly in relation to website design, roadmap structure and terminology. Similarity alone, however, is not evidence of plagiarism. Projects working in the same technical space will often converge on similar concepts, milestones and vocabulary because they face many of the same engineering problems.
The use of terms such as “bytecode” and “runtime” reflects Eco’s actual implementation.
Eco compiles Elm through an MLIR-based intermediate representation. That representation can be serialized into a binary file, so describing it as bytecode is technically accurate. The change from “MLIR dialect” to “Eco bytecode dialect” was intended to describe the existing system more clearly, not to signal a new direction or a borrowed idea.
Similarly, a GitHub link was corrected to point to a repository named eco-runtime. That repository had already carried that name since November 2025. The correction therefore did not represent a sudden change in product positioning on 3 June. The repository was subsequently renamed eco-compiler, which further demonstrates that the link correction was not evidence of an attempt to reposition Eco around the word “runtime”.
The roadmap similarities also need to be understood in context. Compiler projects commonly progress through comparable stages: establishing an intermediate representation, compiling or executing programs, adding runtime support, improving tooling, stabilising releases and extending deployment options. These are largely determined by technical dependencies rather than by any one project’s originality.
Common technical words such as “bytecode”, “runtime”, “compiler”, “enterprise support” and “roadmap” are not distinctive expressions. A credible claim of copying would require evidence of unusual shared wording, non-obvious duplicated structure, copied implementation ideas or a clear development chronology showing direct derivation.
Eco has been developed over a substantial period, with its design decisions visible in its code, commit history and documentation. Its architecture is materially different from other Elm execution projects. It uses MLIR and LLVM, preserves type and representation information through the compiler pipeline, and includes its own work on specialization, runtime representation, garbage collection and native code generation.
The central point is simple: Eco should be judged on its implementation and development history. Publicly visible terminology changes or broad similarities between roadmaps do not establish plagiarism, particularly where those changes have direct technical explanations.
Reasonable questions about provenance, design and chronology are welcome. They should be addressed by examining the underlying work carefully and by distinguishing ordinary convergence from genuine copying.
I reject the portrayal of me as dishonest, opportunistic, or willing to take credit for another person’s work.
I have spent much of my professional life building complex systems, sharing technical ideas, and engaging seriously with the work of others. I understand the importance of attribution. Where an idea comes from someone else, I believe in acknowledging that clearly. I would not knowingly present another person’s original work as my own.
My record is one of sustained effort rather than shortcuts. I am prepared to do difficult, detailed work over long periods, to explain my reasoning publicly, and to accept scrutiny of what I have produced. That is not consistent with the picture of someone seeking attention through appropriation.
I have also tried to resolve disagreements directly and privately before allowing them to become public disputes. I approached the earlier concern in a conciliatory manner and was willing to make changes to reduce friction, even though I did not accept the underlying accusation. That willingness should not be mistaken for an admission of wrongdoing.
When I was later accused publicly in severe and personal terms, I responded defensively. Some of my language was sharper than it needed to be. I can acknowledge that without accepting a false account of my intentions or character. Irritation under attack is not evidence of dishonesty.
I do not believe that another person’s success diminishes my own, nor do I object to others working in the same field. I welcome independent projects, competing approaches, and serious technical disagreement. My aim is to contribute useful work, not to claim ownership of an area or prevent others from participating in it.
The accusations made against me attribute motives that are not mine. They turn disagreement, coincidence, and competition into allegations of moral misconduct. Those allegations should not be accepted merely because they are expressed forcefully.
I ask to be judged by my established conduct: whether I work openly, whether I give credit where it is due, whether I engage with evidence, whether I try to resolve conflict reasonably, and whether I stand behind my own work.
On that basis, I believe the suggestion that I am a plagiarist or a person of bad faith is both unsupported and unjust.