Filter
Exclude
Time range
-
Near
Replying to @withfolyd
在任何一个成熟的大公司里做"创新"都很难.6年前,MS内部做过类似Bun的项目,为此MS开源了Edge内部的JS engine ChakraCore, github.com/search?q=ChakraCo…. MS的NodeJs项目最后无疾而终,后面在GitHub github.com/nodejs/node-chakr… Bun项目借鉴过不得而知,向理想主义者致敬
4
886
6 Jun 2025
「v8の事はGeminiに聞け」とか「ChakraCoreの事はCopilotに聞け」とか、そういう多少は自社のコードベースに触れてる事に期待とかできないのかなってGemini君に聞いてみたんだけど…… 「面白い視点だけど、現状では断言できる根拠はありませんね。」て流されたw ちくしょー
4
746
27 May 2025
Don’t assume the JS engine running the Start menu is something like V8 or a headless Chromium instance. It’s almost certainly Hermes, ChakraCore, or a custom minimal JS engine built specifically for low-memory, low-I/O system components. We’re talking tight native bindings, RAM-conscious execution, and components that are likely already preloaded or idle-resident. If anything, you're splitting hairs. This isn't "web bloat" like you see in Electron apps. It's more like embedding a small, scriptable runtime into a native shell for flexibility, not spinning up a browser every time you press the Windows key.
1
1
52
Chakracore JavaScript engine (jscript9) was embedded in Excel for ages, it was easy to attack but hard to reach in real life. v8 would mean that it’s now both hard to reach and hard to attack. Congrats to Microsoft and good luck to the fuzzers!
1
7
562
Replying to @cjihrig
node-chakracore flashbacks
4
213
Following our successful exploitation of CVE-2018-3048 on the ChakraCore engine, myself and @f00fc7c800 have decided to write a blogpost about it. You can read about our journey into building the proof of concept exploit here execc0de.github.io/posts/cve…
1
30
94
9,348
17 Sep 2024
"Microsoft Edge and ChakraCore in Microsoft Windows 10 Gold, 1511, 1607, 1703, 1709, and Windows Server 2016 allows remote code execution, due to how the scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability" 👇
17 Sep 2024
shoutout @reubensammut carried my asss hardd.. but we finished it ! cfg bypass , aslr ,dep bypass CVE-2018-0834 . we killed float array :) to many more when we eventually start the start up :) github.com/SpiralBL0CK/-CVE-… . enjoy!
2
2
1,150
I miss ChakraCore... Wait shi it still powers my app Jokes aside, if you love ChakraCore as much as I do, there is a vcpkg port for its embedding. Go ahead and build some pet projects
2
38
I commented before reading the issue 😅 but we still could eventually get ChakraCore back again too, it was such a sad day to see MS knocking it out of business after so much work — hopefully the folks running Ladybird will get us a reliable and promising 4th mainstream engine
3
540
Replying to @matthewcp @meijer_s
There actually was. For a couple or years microsoft sponsored Node-Chakracore.
5
133
…but investing $$ in improving Node.js cold start, apparently does not. Heck, we were planning to make Node.js multi-vm when MS was backing Chakracore.
1
6
211
マイクロソフトの ChakraCore におけるリソースの枯渇に関する脆弱性 dlvr.it/T20vQQ

1
2
2,776
#NGK2024S へ〜 ECMAScript ランタイムの、仕様の実装度をあらわすテストスイートがあるんだ。Hermes はまだまだ低いが、Microsoft が捨てた ChakraCore よりは高くなっている test262.fyi/#

5
382
5 Jan 2024
I made it for extending bedrock scripting API and supported node.js later. と書いてあったけど、V8, JSC, SpiderMonkeyのような最新のECMAScriptをほぼカバーしているエンジンがありながら、なぜ機能の追加もほぼないChakraCoreを使用したのかは書いてない... github.com/bdsx/bdsx/issues/…
1
2
91
5 Jan 2024
今でもちまちま開発が続いてるChakraCoreくんはどこまで新機能サポートされてるんだろう
2
75
Waiting for a 🤓 (me) to say "Node with ChakraCore" or @justjs14 or something else as niche as possible
1
538
Initially the project used ChakraCore (by Microsoft) in Node.js, but then as soon as V8 added jitless mode, no need for ChakraCore anymore.
1
3
122
23 Jul 2023
It's wild that they open sourced ChakraCore and just left the HTML and CSS parsers and renderers closed. Also I wish Opera open sourced Presto, it makes no sense that it's still closed source. Luckily other than Ladybird, Servo is back alive and there's also Flow now.
1
3
53
Replying to @bcomnes
I’m pretty sure they don’t plan to. I would love to see Microsoft resurrect Chakracore!
2
7
1,696