PJpjmlp·Jul 30, 2018
Not necessarily, given that a binary representation is also being discussed (not to mix with WebAssembly).
https://github.com/binast/ecmascript-binary-ast
In Announcing TypeScript 3.0binast
ecmascript-binary-ast
HTML2018–2018
binast / ecmascript-binary-ast
ecmascript-binary-ast
Binary AST proposal for ECMAScript
2Distinct people
2Mentions
0Explicit recommenders
2GitHub stars
What to know before exploring
What it is
Binary AST proposal for ECMAScript
GitHub
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, 1:49:46 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 week2 dated mentions
Observed mentions: 2018-05-16 20:31:59 UTC to 2018-07-30 20:46:18 UTC. Weeks start Monday, 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 |
|---|---|---|---|---|---|
| May 14 | 2018-05-14 00:00:00 UTC | 2018-05-21 00:00:00 UTC | 1 | 0 | 1 |
| May 21 | 2018-05-21 00:00:00 UTC | 2018-05-28 00:00:00 UTC | 0 | 0 | 0 |
| May 28 | 2018-05-28 00:00:00 UTC | 2018-06-04 00:00:00 UTC | 0 | 0 | 0 |
| Jun 4 | 2018-06-04 00:00:00 UTC | 2018-06-11 00:00:00 UTC | 0 | 0 | 0 |
| Jun 11 | 2018-06-11 00:00:00 UTC | 2018-06-18 00:00:00 UTC | 0 | 0 | 0 |
| Jun 18 | 2018-06-18 00:00:00 UTC | 2018-06-25 00:00:00 UTC | 0 | 0 | 0 |
| Jun 25 | 2018-06-25 00:00:00 UTC | 2018-07-02 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2 | 2018-07-02 00:00:00 UTC | 2018-07-09 00:00:00 UTC | 0 | 0 | 0 |
| Jul 9 | 2018-07-09 00:00:00 UTC | 2018-07-16 00:00:00 UTC | 0 | 0 | 0 |
| Jul 16 | 2018-07-16 00:00:00 UTC | 2018-07-23 00:00:00 UTC | 0 | 0 | 0 |
| Jul 23 | 2018-07-23 00:00:00 UTC | 2018-07-30 00:00:00 UTC | 0 | 0 | 0 |
| Jul 30 | 2018-07-30 00:00:00 UTC | 2018-08-06 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesFirst, I suppose I'm obligated to say that I'm a huge fan of Wasm (and was a huge fan of pnacl for years before that).
Wasm (like asm.js before it) is target at unmanaged languages. A C++ codebase likely does very well with good performance. That was not what I was talking about. Convincing a game company to write their games in C++ is trivial. Convincing that same game company to write their normal CRUD website in C++ would be incredibly difficult.
Looking at apps, there's still issues. Consider Qt. While it's very possible to write everything in C++, loads of companies jumped straight onto the QML/JS bandwagon because its (generally speaking) much faster to write safe code in JS (also, running the v8 version that Qt requires would be terribly slow compared to the native engine). UI development is hard no matter what and C++ doesn't do i
Read the rest
t any favors. JS features like closures and dynamic objects make many things easier than static classes functions.
This means we need to look away from C++ to something that is managed and has faster code turnaround times. The best possible languages for this are (IMO) Scheme (or maybe Common Lisp) and SML (or maybe Ocaml or F#). You could also make arguments for something in the vein of Dart or Kotlin.
How do you bring these languages to wasm? If you use a JIT, you run into a rather large payload (4-10mb of code is going to have obvious impacts). In some cases like Ocaml where a native compiler to wasm is in the works, you still have a GC issue (basically, you can make an advanced GC that is slow or a basic GC that is "fast", but with other issues).
The addition of DOM API will solve the GUI issues (and maybe they'll rework them to be more like dart's API). Adding hooks into the builtin GC would reduce payload size down to something closer to unmanaged languages. 10 years after those are added (when outdated browsers can finally be ignored), wasm will finally be ready to replace JS.
Adding those features doesn't seem to be highest priority. Unfortunately, you and I will probably be nearing retirement age before they are generally usable.
As a point of interest, JS code could be getting much smaller and much faster to parse (plus becoming a better compilation target) with the JS binary AST proposal.
https://github.com/binast/ecmascript-binary-ast