Live data from Hacker News

ChakraCore GitHub repository is now open

blogs.windows.com

111–120 of 324 posts

Re: ChakraCore GitHub repository is now open

#111
post #29

Good that it's open source, but I found this blurb from their contributing guidelines [0] to be contribution inhibiting: You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it. [0] h…

Don't most large organisations require something similar with their own open source projects? I know Google and Facebook do. It's just a way of confirming that you own the rights to your contribution, and that you explicitly give Microsoft permission to use it. (And if you didn't want to grant them permission, you would have no reason to contribute!)

> Don't most large organisations require something similar with their own open source projects? I know Google and Facebook do.

Mozilla gets by without one. Apple's approach for managing Swift, too.

> It's just a way of confirming that you own the rights to your contribution, and that you explicitly give Microsoft permission to use it.

If that's all they wanted to do, they could get by with something resembling the terms that Mozilla gets its committer's to sign. Usually these CLAs are specifically written to go a lot further than that, though. They usually take away a lot of the contributors' bargaining power. Microsoft's CLAs included.

Re: ChakraCore GitHub repository is now open

#112
post #31

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.

If you're concerned about MS privacy, you should be absolutely outraged about Google, Facebook, etc. You also shouldn't consider Apple to be that different.

The Win10 privacy thing isn't much different from what Apple now does by default, and all of it can be turned off. While it does gather data, it does so in the course of supporting functions that most users want like Cortana and smart search. Apple is also full of phone home stuff that must be deliberately turned off if you don't want it.

The fact is that the market has clearly indicated (1) a preference for free stuff that is supported by 'ecosystems' and indirect monetization, and (2) a willingness to trade privacy for convenience and features. You can't blame companies for complying with what the market clearly wants as indicated by consumer buying behavior. If people cared about security and privacy more than features and UX, they would vote with their dollars.

Re: ChakraCore GitHub repository is now open

#113

What is the main reason for not merging V8 and ChakraCore? It's really cool that teams from the big companies can learn tricks from each other, but as far as I see the goal of Google and Microsoft here is to just advance Javascript in the same standard direction. Have you talked about not duplicating all efforts?

Multiple implementations is a very good thing to have in a language. V8 already has enough influence over JavaScript.

Re: ChakraCore GitHub repository is now open

#114
post #29

Good that it's open source, but I found this blurb from their contributing guidelines [0] to be contribution inhibiting: You will need to complete a Contributor License Agreement (CLA) before your pull request can be accepted. This agreement testifies that you are granting us permission to use the source code you are submitting, and that this work is being submitted under appropriate license that we can use it. [0] h…

NodeJS has exactly the same restriction.

Node.js does not require a CLA anymore since it left Joyent behind.

Re: ChakraCore GitHub repository is now open

#115
post #31

Earlier quoted context omitted.

> 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.

The Windows 10 privacy thing is completely overblown. Most of the privacy settings that people are most worried about is tied into Cortana or more specifically what you allow Cortana to do on your behalf. You can simply choose not to use Cortana or to disable it entirely. Google Now & Siri support the same functionality but ironically don't give you the settings to disable it, so nobody bats an eyelid. Beyond that yo…

> Most of the privacy settings that people are most worried about is tied into Cortana or more specifically what you allow Cortana to do on your behalf

In all of these discussions on HN, the only ones bringing up "worries" about Cortana features have been people defending Windows 10 (and now Windows 8 and 7) data collection. It's easy to disable and, if you choose not to use it, it won't collect data anyways. The same can't be said of telemetry.

> Which tells them when you launch a Windows 10 "app" and some basic computer information

Actually it's not clear what else is being collected, because Microsoft won't disclose what's being collected. Is there evidence that only data about usage of Windows store apps is being collected?

> But even without that setting/ability the apps themselves could conduct the same reporting

Which would be needed to take into account when deciding on if that app should be used. Just to be clear, that means the application I choose to run might be collecting analytics, but my OS is also collecting analytics on the applications I'm choosing to run because it thinks it should.

> Nobody can actually point to exactly what specific information Microsoft is even taking

Yes, because Microsoft won't tell anyone what it's collecting!

> and have even less data yet still to back up any claims

As a baseline, you yourself talked about how we know they're collecting information about application usage. That right there is undesirable behavior for many that we have plenty of evidence for.

Re: ChakraCore GitHub repository is now open

#118
post #83

Earlier quoted context omitted.

In the case of the MIT license, I don't see much harm in throwing in a CLA because it's nearly impossible for Microsoft to do anything to break the terms of the license; however, while I am not a lawyer and this isn't legal advice, in general signing a CLA (including in this instance) often gives the other party rights to re-license the work and continue to use the work if they end up in violation of the original lic…

Regardless of what license the project is filed under, as an individual contributor working for free for the community, the license of a project determines the terms under which I am sharing my work. I expect those to be respected in perpetuity, and I would like the right to rescind my contribution if the copyright holder is in violation of the license. The CLA is just another license to consider with the project; ju…

> CLA could give joint copyright to the involved parties

Licensing to allow joint copyright isn't really a thing in the US. Anyone trying to craft a license that formalizes joint ownership after the fact is going to have a not-so-fun time trying to make that work.

Re: ChakraCore GitHub repository is now open

#119

> ChakraCore > The MIT License (MIT) > Copyright (c) Microsoft Corporation Incredible! https://github.com/Microsoft/ChakraCore/blob/master/LICENSE....

So many things coming out of "the new Microsoft" that it is hard to keep up with.

Gone from being vehemently anti-Microsoft most of my career to going "Hmmmm, I should look at that."

Now to carve out time to do anything with any of it. :\

Re: ChakraCore GitHub repository is now open

#120

Earlier quoted context omitted.

Having more than one engine can mean that there is less of a V8 monoculture. Bugs in V8 don't become "standard" and "things that V8 is really good at" doesn't become "things that Javascript is really good at".

That's what Go does. The reference of the language is [an actual document]( https://golang.org/ref/spec ), not a reference implementation. There are two compilers (gc and gccgo), and this way, no edge-case of an implementation can make its way into programmers' habits, something that tends to happen a lot with JavaScript.

What do you mean by the, "edge-case of an implementation... makes its way into programmers' habits" as something that happens a lot in javascript. Maybe I'm not understanding but I read that statement and I don't see how that applies to javascript.
Post reply on HN