ChakraCore

[ChakraCore @ChakraCore]

@koste4 If anyone is interested, this is followed up here https://t.co/JLlqEPZvjT

[ChakraCore @ChakraCore]

@matteocollina @paulatnearform @NodeSummit @charlesbeeler @nearForm ⏲️🧳
⏲️🧳
⏲️🧳

[ChakraCore @ChakraCore]

New patch release - ChakraCore v1.10.1

https://t.co/RrhBdqdysO

[ChakraCore @ChakraCore]

Meet ChakraCore v1.10.0 with tons of JavaScript, WebAssembly, performance, an JSRT updates. Also, special shout-out to our friends rhuanjl, fatcerberus, OSS-Fuzz, and Google Project Zero for many contributions during this release!

https://t.co/BZ3HxSCU0I

[ChakraCore @ChakraCore]

Leaner memory footprint and faster built-ins in EdgeHTML 17! Read about some of the cool stuff we did for JavaScript/WebAssembly performance 🚀.

https://t.co/LqbKDpUba8

[ChakraCore @ChakraCore]

@styfle @jdalton @MSEdgeDev YES you absolutely will! It is a high priority item on our roadmap, and when we implement it you'll see it show up in the ChakraCore repo.

We certainly welcome external PR as well.

https://t.co/vDIqNzineO

[Louis Maresca @LouMM]

Great Performance benefits when integrating @ChakraCore into Excel Custom functions running JavaScript. @hiteshk 'a team is doing amazing work on the JSC! #MSbuild

[ChakraCore @ChakraCore]

Welcome @zenparsing as a new member of the team! https://t.co/ctmYSq8Q62

[Gaurav Seth @gauravseth]

Welcome aboard @zenparsing! It's great to have you come and be a part of on the @ChakraCore and @MSEdgeDev team. https://t.co/JWc6EndIyv

[Matt Miller @epakskape]

"FromVar hardening". This change to @ChakraCore back in Oct 2017 seems like it might have gone unnoticed. Good example of trying to address a class of vulnerabilities vs. fixing individual instances, in this case related to type confusions https://t.co/Zt2SAQVhpO

[ChakraCore @ChakraCore]

Watch Louis talk about how Chakra JIT 🚀 works

https://t.co/9IiWskxnze

[Matt Hargett @syke]

Congratulations to @AruneshC @ChakraCore for the successful deployment of N-API! Besides easing upgrades, it moves JS runtime diversity forward. Allowing for more memory efficient JS runtimes increases the reach of @nodejs and allows for higher density of containers/core! https://t.co/1ahDmyaMkh

[ChakraCore @ChakraCore]

More security fixes in the patch release 1.8.2.

https://t.co/KWdcMkhHQ7

[ChakraCore @ChakraCore]

ChakraCore 1.8.1 - security fixes, performance improvements, and bug fixes!

https://t.co/tteAqnQsXf

[Gaurav Seth @gauravseth]

Want to come work on @ChakraCore and @MicrosoftEdge? We are hiring PMs and Devs for positions based out of Seattle area. DM open - msg me.

[ChakraCore @ChakraCore]

"...instead of developers specializing their JavaScript code for the compilers, compiler implementers should focus on optimizing common, real-world code patterns that developers are using."

True dat 💯💯💯 https://t.co/k7VLPENvF5

[Node.js @nodejs]

How to modernize #nodejs with idiomatic #JavaScript. Food for thought 🥑 from @AruneshC and Peter Marshall https://t.co/y6aXhL0z1G cc: @bmeurer

[ChakraCore @ChakraCore]

@hyperandroid There's no official Android support now, but you may want to check this thread :D

https://t.co/8M3MbcKduX

[Ariya Hidayat @AriyaHidayat]

Two years ago I was playing with the experimental 🐧 port of @ChakraCore. It was superfun! What is even more fantastic is that, quickly after that, Linux support was not experimental anymore as it's always part of the master branch 👍 https://t.co/avAVOWxyj5

[ChakraCore @ChakraCore]

1.8.0 is out! https://t.co/vFCUk8l3bt

[Doug Ilijev @DougIlijev]

We have just released @ChakraCore 1.8.0 (https://t.co/OT9l4reSu3) see https://t.co/uLqynCJUar for release notes. #ChakraCore

[Brian Terlson @bterlson]

ChakraCore is moving to ICU on all platforms which should make the output of Chakra/Edge's Intl APIs identical to other engines!

NB: with major implementations all aboard the ICU train, we may have to route through Defacto Standardsville before reaching our final destination.

[NodeConf EU @NodeConfEU]

📹@mhdawson1 & @AruneshC "Until now, native module (add-ons) maintainers have had to recompile for each #Nodejs release as well as potentially updating their code to cope with the rapid pace of changes in the v8 APIs"
#NodeConfEU
⏩ https://t.co/MV5dNuIAnN