icr
ChakraCore
Our great sponsors
icr | ChakraCore | |
---|---|---|
2 | 15 | |
500 | 9,028 | |
0.4% | 0.2% | |
1.8 | 5.3 | |
over 2 years ago | 2 days ago | |
Crystal | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
icr
-
Crystal's Interpreter (2021)
it's had an IRB-like REPL for years. It just wasn't built into the language. Admittedly it was limited compared to IRB but it was more than enough to test out quick ideas.
It's called ICR: Interactive Crystal
https://github.com/crystal-community/icr
the first release was back in 2017
-
Simple Jupyter kernel for Crystal with 140 lines
I wrote a Crystal kernel for Jupyter, just a modified bash_kernel, 140 lines of code, but it was tiring because I don't have enough Python ability. icrystal is the widely used Jupyter kernel for Crystal, which uses ICR . On the other hand, this crystal_kernel uses the official crystal interpreter.
ChakraCore
-
This year in Servo: over 1000 pull requests and beyond
I thought it would be a fun weird project to make Servo work with MS' abandoned JavaScript engine:
https://github.com/chakra-core/ChakraCore
Of course it is written in C++ and you'd probably want a pure Rust browser. But it is sad seeing that fairly complete open source JIT JavaScript engine sit and rot.
-
Microsoft defends Edge's predatory practices with cringe reply on X
The JS engine is open source: https://github.com/chakra-core/ChakraCore
-
A list of JavaScript engines, runtimes, interpreters
ChakraCore
-
Roll your own JavaScript runtime, pt. 3
Not to forget the engine Charka: https://github.com/chakra-core/ChakraCore
The only bit of the old Edge that had its source emancipated. It was/is? quite performant.
-
Have you deployed Microsoft Todo to end users? How did you deploy it?
As a Linux user, I very much think Microsoft should have continued Trident and Chakra. Apple also should have continued releasing Safari for Windows. Our web QA setup was entirely built around Macs back then, but it was great to be able to test sites with Safari on Windows, and to have another responsive browser on Win32.
-
The Javascript Engine
Edge was initially using Chakra but has been rebuilt using Chromium and the V8 engine.
-
Crystal's Interpreter (2021)
https://github.com/chakra-core/ChakraCore/wiki/Architecture-...
I've found the source code to be quite readable too - albeit from a bug-finding perspective, not a strictly pedagogical one.
-
Exploring React Native’s new architecture
Furthermore, the new architecture decouples the JavaScript interface from the engine, enabling the use of other JavaScript engines such as Hermes, V8, or Chakra.
-
How web browsers work - executing the Javascript (part 5, with illustrations)💻🌠
ChakraCore
-
Enumerating and analyzing 40 non-V8 JavaScript implementations
I am astonished at the omission of ChakraCore, open sourced by Microsoft but sadly abandoned by them after they switched Edge to Chromium: https://github.com/chakra-core/ChakraCore. But it looks like it’s still chugging along as a community effort rather than being completely abandoned.
What are some alternatives?
crystal_kernel - Python wrapper kernel for Crystal
Jint - Javascript Interpreter for .NET
charly - 🐈 The Charly Programming Language | Written by @KCreate
hermes - A JavaScript engine optimized for running React Native.
bash_kernel - A bash kernel for IPython
V8 - The official mirror of the V8 Git repository
fancyline - Readline-esque library with fancy features
v8.dev - The source code of v8.dev, the official website of the V8 project.
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
AutoHotkey-jk - AutoHotkey, running JavaScript.
kemal - Fast, Effective, Simple Web Framework
astexplorer - A web tool to explore the ASTs generated by various parsers.