Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bartqk
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
bartqk
11y ago
certainly, after there's a better API for completions and evaluations created. Will be easy to write plugins then.
2.
▲
by
bartqk
11y ago
Indeed MetaES may be a way to pave a path to new kind of development. Bret Victor's work, LightTable, Swift Playground and others proved that small improvements are possible. I believe though, that next bigger step requires new fundame
3.
▲
by
bartqk
11y ago
or just `1..constructor` -> function Number().
4.
▲
by
bartqk
11y ago
Yeah, much older project. Looks like it intereprets some kind of IR code, it's not the case in MetaES, it just executes AST. I don't know either if it allows interoperate with surrounding interpreter. MetaES interops native code o
5.
▲
by
bartqk
11y ago
Thanks. Didn't heard of Higgs, but looks interesting. You could use JITting in MetaES as well, you have all information about execution during runtime, so why not? That was one of my ideas for demo, but this one is quite heavy ;) Whe
6.
▲
by
bartqk
11y ago
MetaES was tested using test262. Passed most of the cases. https://github.com/metaes/metaes - "MetaES was tested using test262 test suite. Runnable test suite is currently not added to the repository." You&#x
7.
▲
by
bartqk
11y ago
nice trick. You can, but you can't reference `Number` directly, that's the point. `Number` is a part of standard library, so being in JS it's possible use hack that you've shown. But you won't find a reference to le
8.
▲
by
bartqk
11y ago
Yep. But it went nowhere, as far I know.
9.
▲
by
bartqk
11y ago
Yeah, it would be slower. But you could use some kind of JITting while the interpreter goes and create appropriate ES5 code. That's possible next step.
10.
▲
by
bartqk
11y ago
It is very similar. But MetaES tries to be production ready and reliable. As far I rememember, tailspin wasn't metacircular, but just an interpreter that interprets some kind of bytecode created from JavaScript source.
11.
▲
by
bartqk
11y ago
and thanks! ;)
12.
▲
by
bartqk
11y ago
That's the plan, although it may take few weeks or months to create something solid :)
13.
▲
by
bartqk
11y ago
Could be :) If you accept that it's slower. Benchmarks would show the difference.
14.
▲
MetaES – JavaScript in JavaScript interpreter
(metaes.org)
51 points
by
bartqk
11y ago
|
31 comments