4 ms·
One announcement I'm waiting to hear about in all honesty is Microsoft open sourcing Edge, they don't have to reveal Cortana specifics (though that would be fun
by giancarlostoro 8y ago
One announcement I'm waiting to hear about in all honesty is Microsoft open sourcing Edge, they don't have to reveal Cortana specifics (though that would be fund to read through if they'd allow it) but just EdgeHTML with Chakra in a way that compiles nicely. I would love to see what would happen if they allowed the community to contribute back to Edge if it could become much more competitive as a result of them welcoming contributors.
A few years ago I'd sound like I'd be tripping on bathsalts but I think it could happen, just a matter of when they choose to do so.
- Flenser 8y agoChakra is Open Source: https://github.com/Microsoft/ChakraCore https://github.com/Microsoft/ChakraCore but I guess what you want is an "Edgeium" equivalent of Edge in the way that Chromium is the full (compilable) OSS version of Chrome.
- giancarlostoro 8y agoYes, I want an all in one solution that's open.
- danShumway 8y agoI think that Microsoft is still working on a Chakra version of Node as well. That's probably what I'm most excited about, V8 hasn't had much competition, which means that there's nobody to question its approach to resource usage, garbage collection, etc... V8 is great for some things, but it falls down hard on low-resource environments. This is one of the reasons why Electron apps are so greedy, you have to kind of do a lot of fighting with V8 if you don't want it to balloon RAM usage. If you have open RAM sitting around, sometimes V8 will decide to just take it so it can defer garbage collection longer, or so it doesn't need to waste time asking for it in the future. From what I've heard, Chakra is better about those kinds of situations. I would really like to see a runtime ecosystem for Node and Electron that is as competitive as browsers are. Microsoft is probably in the best position to push that. There's some potential that with a solid competitor they could open the floodgates and encourage other developers to start building browser runtimes that are optimized for specific scenarios rather than a one-size-fits-all approach.
- Flenser 8y agoThey've open sourced some of their work on this, but it look abandoned: https://github.com/Microsoft/node-v0.12 https://github.com/Microsoft/node-v0.12 https://github.com/Microsoft/node-uwp https://github.com/Microsoft/node-uwp
- kodablah 8y agohttps://github.com/nodejs/node-chakracore https://github.com/nodejs/node-chakracore
- ksec 8y agoI am thinking of the same. No one uses Microsoft Browsers anymore, especially Edge. Even if you exclude Phones and Tablet, Chrome, Firefox, Safari and Internet Explorer combined to have close to 90% market share. And if you include Smartphone and Tablet, which has 4 times the user base of PC, Edge has less then 2% of total web market share. They could made EdgeHTML and Chakra the base for Visual Studio Code, allowing it to have an wider use case, instead of relying on Electron.
- giancarlostoro 8y agoI've thought about this too. Would be interesting to see how they could add Node-like support to Chakra (APIs) and see how it performs on Windows compared to Electron in regards to memory consumption and Battery usage. But when you talk about making even more web browser apps people don't get too excited.
- Cu3PO42 8y agoThey 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 would 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 https://github.com/nodejs/node-chakracore [1] https://sqreen.github.io/node_engine_bench/?q=eyJ0ZXN0cyI6WyIuL3Rlc3RzL2FjY2Vzcy1ub24tZXhpc3RlbnQtYXJndW1lbnRzLWluZGV4LmpzIl0sInZlcnNpb25zIjpbIjYuMTAuMV92OCIsIjcuMTAuMF92OCIsIjcuMTAuMF92OF90dXJib19pZ25pdGlvbiIsIjguMC4wX3Y4IiwiOC4wLjBfdjhfdHVyYm9faWduaXRpb24iLCI4LjAuMC1uaWdodGx5MjAxNzA0MTUyNjVmYzBiZWRjX2NoYWtyYSIsIjguMC4wLW5pZ2h0bHkyMDE3MDUwNWZlNDRmNTQ5NDlfY2hha3JhIl19 https://sqreen.github.io/node_engine_bench/?q=eyJ0ZXN0cyI6Wy...