It's called ChakraCore because it is the core engine component of Chakra, not because of any "trend". Specifically, they mention it excluding the runtime bindin

It's called ChakraCore because it is the core engine component of Chakra, not because of any "trend". Specifically, they mention it excluding the runtime bindings for browser or Windows apps. > ChakraCore is a fully capable JavaScript virtual machine that has the exact same set of capabilities and characteristics that are supported by Chakra, with two key differences. First, it does not expose Chakra’s private bindings to the browser or the Universal Windows Platform, both of which constrain it to a very specific use case scenario. Second, instead of exposing the COM based diagnostic APIs that are currently available in Chakra, ChakraCore will support a new set of JSON based diagnostic APIs, which are platform agnostic and could be standardized or made interoperable across different implementations in the long run. As we make progress on these new diagnostics APIs, we plan to make them available in Chakra as well. From: https://github.com/Microsoft/ChakraCore/wiki/Architecture-Overview https://github.com/Microsoft/ChakraCore/wiki/Architecture-Ov...