Live data from Hacker News

ChakraCore GitHub repository is now open

blogs.windows.com

231–240 of 324 posts

Re: ChakraCore GitHub repository is now open

#231

Earlier quoted context omitted.

That's correct. V8 license is required in v8-*.h files because they are v8 header files that chakra shim uses. The implementation files has Microsoft license. E.g. All files in https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... Disclaimer: I work for Chakra team (powering node.js)

Any progress in talks with Node.JS to make an implementation independent JS engine API for node?

Its a long goal as of now that everyone want to achieve. You can follow this discussion at https://github.com/nodejs/nan/issues/349

Re: ChakraCore GitHub repository is now open

#232

Earlier quoted context omitted.

>When Joyent decided they didn't want to embrace anymore, the community took the extinguisher out of their hands Joyent wound up embracing io.js, and Node.js is moving at a very fast pace now while maintaining LTS branches in parallel. It's a very well managed project, in my opinion. Aside, how come anything remotely questioning of Microsoft when there's an announcement is met with downvotes?

> how come anything remotely questioning of Microsoft when there's an announcement is met with downvotes? Selection effects! Posts about Microsoft doing something cool will attract a readership in which Microsoft fandom is over-represented, compared to the average readership of HN.

I don't agree with your characterisation. GP was complaining about downvotes to anti-MS comments, and that's nothing to do with 'attracting a readership'. More like the specific criticism of Microsoft demonstrated in this thread so far is the same tired old crap and not relevant to the actual topic.

Re: ChakraCore GitHub repository is now open

#233
post #136
post #108

Earlier quoted context omitted.

> Want to loan someone money? consider their credit rating. Want to hire someone? consider their employment record. That's a single person. Microsoft is many thousands of people, and the most important decision makers have changed. In your analogy, you're considering whether to loan money to an almost completely different person.

Those same decision frequently had hiring and promotion authority. How different are these new people? Are they someone the old decision makers promoted minutes before leaving or are they fresh new hires? Chances are there is a complex mix and at least some of microsoft's behavior has changed and some will remain the same.

> some of microsoft's behavior has changed and some will remain the same

That's the exact argument I was making. The analogy doesn't work because this is, literally, a new Microsoft. It has new leadership. You can't use the past as a benchmark for how this company will behave because no one really knows what parts of the company's behavior and culture have changed and what parts haven't.

Re: ChakraCore GitHub repository is now open

#234

I'm skeptical. Over the past 5 years or so, Microsoft has lost developers as a core group. There are certainly interesting things happening out of their dev group, but with the rise of Cloud infrastructure, cheap (free) alternatives to WINS stacks rose tremendously in popularity. I was a Seattle Techstars 2013 Founder, and the only two teams using MSFT tech were those whose founders were ex-Microsoft employees. This…

One thing that always baffled me was "routine software audits" by Microsoft, Oracle, and the likes. So, you license a technology, and now your supplier can police you at their own wish. OK, there are situations when you have no choice - they are the only game in town. But in the last decade much of the infrastructure has been available in an open-source form. I am surprised anyone would touch anything from such compa…

You agree to this even if you're just using Windows and/or IE, or any other Microsoft software for that matter. So either you have absolutely no Microsoft software, or you're open to an audit.

Re: ChakraCore GitHub repository is now open

#235

Earlier quoted context omitted.

That's correct. V8 license is required in v8-*.h files because they are v8 header files that chakra shim uses. The implementation files has Microsoft license. E.g. All files in https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... Disclaimer: I work for Chakra team (powering node.js)

Just curious: If I would like to write a native extension for a possible Chakra powered node.js, which methods would then be possible? - Use V8 C++ API - Use Chakra extension API - Use NAN - All of those? And in your port are Nodes inbuilt native functions (like the libuv based IO functions) still using V8 APIs which are mapped to Chakra by this shim or are they reimplemented directly on top of Chakra APIs?

For native modules, below options are ideal: - V8 C++ API : These APIs will continue to work with node.js v8 as well as with Chakra because in shim layer we map them to equivalent Chakra APIs. If you see problem in any APIs not working as expected using Chakra engine, please file an issue on Microsoft/node and we will happy to fix it. - NAN : Node.js Chakra is compatible with latest NAN version so it should continue to work with V8 and Chakra engine.

Regarding, Node inbuilt native functions (in other works deps) that are independent of v8, continue to work in Chakra without reimplementation. Chakra shim comes into picture to map V8 C++ APIs to Chakra equivalent.

Re: ChakraCore GitHub repository is now open

#236

Earlier quoted context omitted.

The first step is to get the runtime and interpreter running. Next step is to bring the jit up. Chakra is the hybrid engine where we have the interpreter, simple jit and full jit. The interpreter is the one which does all the profile data collection. Profile data is required to get the quality jit code. Declaimer: I work for Chakra team.

Hi! Thanks for explanation and another cool product! One question that just came to my mind regarding this: Have you thought about a configurable/modular build where this interpreter/simple jit/full jit can be switched? Or is this perhaps already there? I can think of some use cases where it would be interesting to build a modern and full featured JS engine in interpreter-only mode. E.g. to integrate it into platform…

Great question. Yes, we have a way to disable jit. See the merged pull request by our super cool dev here: https://github.com/Microsoft/ChakraCore/pull/4. We have build configuration which produces daily builds without JIT as well: https://github.com/Microsoft/ChakraCore/pull/42.

Re: ChakraCore GitHub repository is now open

#237
post #228

Earlier quoted context omitted.

I'd prefer Apache with its patent clause but what can you do?

Care to elaborate?

If you publish something using apache license you grant users the right to use your patents that cover this software. When you publish under MIT, you can still keep a patent and sue any user.

Re: ChakraCore GitHub repository is now open

#238

I'm skeptical. Over the past 5 years or so, Microsoft has lost developers as a core group. There are certainly interesting things happening out of their dev group, but with the rise of Cloud infrastructure, cheap (free) alternatives to WINS stacks rose tremendously in popularity. I was a Seattle Techstars 2013 Founder, and the only two teams using MSFT tech were those whose founders were ex-Microsoft employees. This…

I'm more than skeptical towards M$, I have a deep deep aversion to anything they are associated with - based on decades of using their products and wrangling their apis as a developer.

Every time I use firefox or libre-office or linux or vim or postgres or http or node.js or any of the great open alternatives to the ugly walled garden that is Microsoft, I feel free as an individual and empowered as a developer - I at least have the tools I can use to make peoples daily work better.

I particularly want them to leave node.js alone, as I use this on a daily basis for real work - I don't want to see them screw that up aswell.

Re: ChakraCore GitHub repository is now open

#239

Earlier quoted context omitted.

Ironically Microsoft had to create a V8 C++ API facade over Chakra in order for Node to compile with it. https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... It's interesting that the license of the Chakra shim is the V8 license: https://github.com/Microsoft/node/blob/chnext/deps/chakrashi...

That's correct. V8 license is required in v8-*.h files because they are v8 header files that chakra shim uses. The implementation files has Microsoft license. E.g. All files in https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... Disclaimer: I work for Chakra team (powering node.js)

You disclose facts you wish people to consider. You disclaim things when you want them to not be considered.

Sorry, it's my pet peeve. Downvote at will

Post reply on HN