-
Notifications
You must be signed in to change notification settings - Fork 84
OneLang vs. Haxe vs. Progsbase comparison
Tamás Koczka edited this page Aug 6, 2018
·
1 revision
| OneLang | Haxe | Progsbase | |
|---|---|---|---|
| Stability | PoC. Unstable, half-done. Should not be used for production | Stable. Can be used for production | Stable. Can be used for production |
| Target language | C++, C#, Go, Java, JS, Perl, PHP, Python, Ruby, Swift, TypeScript | AS2, AS3, C++, C#, Java, JS, Lua, Neko, PHP, Python | Java, C, C++, JavaScript, C#, R, PHP, Python, Visual Basic (3) |
| Source language | TypeScript, C#, Ruby (1) | Haxe | Java (4) |
| Written in | TypeScript (2) | OCaml | Java and progsbase itself |
| Code generation | Based on template files | Hard-coded into compiler | Generated from the progsbase model (similar to an AST). |
| Type system | Simple and limited | Sophisticated | Static typing |
| Generated code quality | Sometimes compiles | Usually works as expected | Always works as expected. |
| Tooling support | Non-existing | Existing | Existing |
| Age | 6 months | 13 years | Released 2018 |
Notes:
- Various limitations apply. I plan to support most of target languages as source language too one day.
- OneLang is planned to be written in OneLang as soon as it stable enough
- In theory, supports all languages that basically supports imperative programming and pointers or references.
- Limitations apply: Reads a certain part of the language dealing with computations. In theory, supports this part of all languages that basically supports imperative programming, static typing and pointers or references.