HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nodejs
node-chakracore
JavaScript2015–2020
nodejs / node-chakracore · Archived

node-chakracore

Node.js on ChakraCore :sparkles::turtle::rocket::sparkles:

Web Development
Explore on GitHubRead Hacker News discussions
32Distinct people
36Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Node.js on ChakraCore :sparkles::turtle::rocket::sparkles:

GitHub

Where it is used

No documented product use was verified in the last source check.

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, 11:56:56 AM 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 year36 dated mentions

Observed mentions: 2015-05-12 18:36:35 UTC to 2020-03-16 17:10:25 UTC.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 13 mentions; 4 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC725
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1349
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC716
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC606
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101

What Hacker News says

36 sources
no_wizard·Feb 27, 2019
I really don't think this is it, if I'm being completely frank, because they already have an enormous amount of up front work done with making Windows PWA friend: https://developer.microsoft.com/en-us/windows/pwa I also am willing to surmise that they are going to put in alot of work re-working all their APIs that are exposed as Edge based interfaces into whatever engine they and up with here (namely chromium), so I don't think it would have been beyond them to put in the work to do something like they did with node and chakra core: https://github.com/nodejs/node-chakracore (which, btw, for now isn't dead: https://github.com/Microsoft/ChakraCore/issues/5865 likely for the reasoning I mentioned above) I just don't buy it. I don't think easy electron compatibility is the main drive here.
In We Need Chrome No More
VoxPelli·Dec 6, 2018
Will Microsoft use V8 as the javascript engine then as well or continue to use Chakra? If they won’t continue to use Chakra, what happens to that project then? It is open sourced and there’s work to make Node.js use it: https://github.com/nodejs/node-chakracore All the more important to support Servo and Gecko – we can’t have all browsers be of WebKit origin – we rather need more initiatives like Servo, that reinvents the engine from scratch, optimized for modern environments.
In Microsoft Edge and open source collaboration
Klathmon·Dec 6, 2018
This is probably going to get a bit "rant-ey", it's not directed at you, but at the ecosystem at large (and kind of at myself). Everyone keeps saying this, but nobody is actually doing anything about it. People (myself included) talk about how a monoculture is bad, but we still don't use Edge. We talk about how more competition in the browser space is a good thing, but we still complain when the latest features or security benefits are missing from a browser. And then when the feature lands, nobody cares. We complain about how bloated and slow browsers are getting, but completely ignore those which are/were slimming that down. And we talk about how Chrome and V8 are taking over the world, but we won't use tech like node-chakracore[1] despite it being a very positive experience when I last used it. I'm assuming that Microsoft is spending a
Read the rest
shitload of time and money on their browser engine, and it was still getting very little usage. They have great performance, some really cool security features, lots of great user-oriented features, and it very rarely gave me issues as a developer, but still nobody (again, myself included) used it. Can you blame them for not wanting to continue? I feel the same as you, this sucks. But I can't blame anyone but myself, because I don't use Edge (despite using Windows as my daily-driver), and I most likely won't switch to it, and it has very little to do with its capabilities as a browser, and more to do with network effects (i'm used to chrome, my information is in chrome, I'm used to the dev tools in chrome, and I personally and selfishly have no reason to switch to Edge, even if it's technically better) You can't blame the company for not wanting to continue pouring money into something which is getting very little usage or return on investment at all. At least by working with Chromium more people are going to get the benefits of their work. [1] https://github.com/nodejs/node-chakracore
In Microsoft Edge and open source collaboration
Cu3PO42·Jun 21, 2018
They did! "Node.js on ChakraCore" [0] already exists. It is maintained by Microsoft, but lives under the NodeJS organization on GitHub. Instead of reimplementing the Node APIs, they roughly implemented the V8 API layer on top of Chakra (which they call chakrashim) to enable "normal" Node to run. I believe the original use case was to run Node on Windows IoT, but I can't seem to find a source on that currently. A very cool feature that is enabled by ChakraCore is time travel debugging (i.e. the ability to go backwards when stepping through code), which has worked very well for me so far. In terms of performance, it does not appear to perform better (or just as good as) V8. The most recent benchmarks I could find are roughly one year old, but have Chakra consistently performing worse than what was at the time a recent V8 version [1]. It wou
Read the rest
ld be interesting to see how memory usage compares. MS has benchmarks to compare different engines for Node in the repository, however I am currently not able to run those. Maybe someone can provide current insight? If you are interested in just testing it out, you can get Node versions built on Chakra from nvs and potentially other Node version managers (see [0]). [0] https://github.com/nodejs/node-chakracore [1] https://sqreen.github.io/node_engine_bench/?q=eyJ0ZXN0cyI6Wy...
In Improved JavaScript and WebAssembly performance in EdgeHTML 17
partycoder·Jun 9, 2018
At least in the case of Microsoft + node foundation, they are forking node so it can operate on top of the MS Chakra "JScript" VM. Chakra supports reverse debugging ("time travel debugging"), similar to the rr project (https://rr-project.org). So... so far: 1. Embrace (join node foundation as platinum member) [1] 2. Extend (add ChakraCore support, time travel debugging) [2] 3. ? [3] If you are smart enough you see where this is going. [1]: https://foundation.nodejs.org/about/members [2]: https://github.com/nodejs/node-chakracore [3]: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
In Microsoft Is Buying Control of Linux [video]
partycoder·Nov 17, 2017
The new Microsoft * Microsoft and node.js 1. Microsoft embraces node.js (embrace) 2. Microsoft forks node (extend) https://github.com/nodejs/node-chakracore 3. Soon! (extinguish) --- * Microsoft and R 1. Microsoft embraces R 2. Microsoft forks R. Fully compatible, but interoperability is one-way only. https://mran.microsoft.com/open 3. Soon! (extinguish) --- The old Microsoft: - Microsoft <3 Apple -> Let's work on Macintosh -> Windows - Microsoft <3 IBM -> Let's work on OS/2! -> Windows NT - Microsoft <3 Sun -> Let's work on Java -> .NET - Microsoft <3 Sybase -> Let's work on Sybase ASE -> SQL Server
In Microsoft joins the MariaDB Foundation as a Platinum level sponsor

Showing the 15 most recent of 36 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.