Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ChakraCore GitHub repository is now open

blogs.windows.com

Post reply on HN
Print view View original

71–80 of 324 posts

Re: ChakraCore GitHub repository is now open

#71

Post by abchatra »

bobajeff wrote: post #55
abchatra wrote: post #9

Earlier quoted context omitted.

Road map here: https://github.com/Microsoft/ChakraCore/wiki/Roadmap I work for Chakra team.

I'm happy to see WebAssembly talked about on there. It talks about standardisation and the polyfil (using asm.js). Any idea on when support will be worked on in the engine?

You can follow webassembly standardization process here: https://github.com/WebAssembly/spec

Look at prototype pull request in ChakraCore by one of our awesome engineer: https://github.com/Microsoft/ChakraCore/pull/63

Re: ChakraCore GitHub repository is now open

#72

Post by jdmichal »

BillinghamJ wrote: post #45
hiteshk_msft wrote: post #4

Earlier quoted context omitted.

Check out the Linux branch :) we are actively working on a port. Disclaimer: Msft employee on chakra

Why port rather than just writing it to be portable from the start? Seems like a lot of work?

Why design the engine first released in 2011 under a completely closed culture to be portable for its eventual open-source release five years later? I understand the appeal of the thoughts behind what you said, but you shouldn't burn time on things you don't foresee being an issue.

Re: ChakraCore GitHub repository is now open

#73

Post by saurik »

epmatsw wrote: post #61
brentvatne wrote: post #33

Where can I find side-by-side benchmarks for Chakra, JavaScriptCore and V8?

Chakra's not on there yet, but I'd expect it to be soon after this announcement: https://arewefastyet.com

Nor is JavaScriptCore, which has made that website pretty useless to me as of late.

Re: ChakraCore GitHub repository is now open

#74

Post by reitanqild »

Someone1234 wrote: post #60
krisdol wrote: post #54

Earlier quoted context omitted.

Wouldn't it be far easier with MIT than GPL? The BSD license sure did little to keep the open source roots of Mac OS thriving.

It could help Microsoft close source THEIR implementation later down the line, but it doesn't help them "extinguish" it completely, particularly if third parties wish to maintain it. MIT makes it easy to fork and relatively easy to re-license.

IANAL but AFAIK as long as they are the sole owner and contributor or has agreements in place with everyone the GPL doesn't protect us against going closed in future releases.

What it does secure is you right to fork the last open source version. Then again, so does BSD, MIT and ASL - and under better terms for everyone else.

Re: ChakraCore GitHub repository is now open

#75

Post by DoubleMalt »

jrcii wrote: post #31
DoubleMalt wrote: post #14

Even if I'm in danger of stating the obvious, but MS really changed its approach to software. And it is incredibly great having competition in the JS engine market.

> MS really changed its approach to software Their open-source friendliness has unfortunately coincided with a decline of their respect for user privacy and choice (Windows 10). I find the "New Microsoft" bittersweet.

While this is true, only open source makes choice and privacy even possible.

They are obviously trying to reinvent themselves partly in the image of Google, whose motto "Don't be evil" also sounds very hollow nowadays.

But I shudder when I think of a world where Google is built upon closed software.

[To clarify: I know that Google does not open most of their software. However, with their reliance on open source software they were a big driver for the legitimacy of the movement]

Re: ChakraCore GitHub repository is now open

#76

Post by petersellers »

krisdol wrote: post #54
Someone1234 wrote: post #24

Earlier quoted context omitted.

It is licensed under MIT. Good luck with that third step...

Wouldn't it be far easier with MIT than GPL? The BSD license sure did little to keep the open source roots of Mac OS thriving.

I thought that had less to do with the choice of license and more to do with the fact that Apple just bundles the zipped source and publishes it every year or so (in contrast to Swift where you can see every commit made since the beginning of the project).

Re: ChakraCore GitHub repository is now open

#77

Post by to3m »

rewqfdsa wrote: post #57

A few years ago, the trendy naming convention was Kit. Now it's Core, I guess. Will we stop wishing we were Apple one day?

Funny thing is that the core is the part of the apple that people generally don't eat.

As for the naming, I've always found it fairly standard for internal productized libraries. The library/product as a whole consists of all the possible pieces you can link with, but the core is the only mandatory part.

Re: ChakraCore GitHub repository is now open

#79

Post by simonw »

nly wrote: post #23
DoubleMalt wrote: post #14

Even if I'm in danger of stating the obvious, but MS really changed its approach to software. And it is incredibly great having competition in the JS engine market.

Three existing production-ready open source engines + other embedded options wasn't already "competition"? It's nice to see but, as far as competition within OSS is concerned, it's about 7-8 years too late. MS will no doubt, at some point, release something like Node.js based on this engine. If they do it'll be widely lauded, but you can barely say they're even a "fast follower" here when they're this slow.

"MS will no doubt, at some point, release something like Node.js based on this engine"

https://github.com/Microsoft/node - "This project enables Node.js to optionally use the Chakra JavaScript engine."

Re: ChakraCore GitHub repository is now open

#80

Post by bastawhiz »

To everyone chanting "Embrace, Extend, Extinguish", I'd like to remind you that Node proper was a golden egg sitting under Joyent's goose. When Joyent decided they didn't want to embrace anymore, the community took the extinguisher out of their hands. Granted, Microsoft is in a more similar position to Google than to Joyent, but the point of the argument is that the community has driven the language and the runtime forward, not the corporation backing it.

Unlike most of Microsoft's other EEE attempts, this time they're putting their code with their mouths are and putting it all up under MIT. There's little you can do to get more open and honest than that. If the community doesn't like the direction MS is taking Chakra, they're free to take it in a new direction. Hopefully it doesn't come to that, but it's an option.

Post reply on HN