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

291–300 of 324 posts

Re: ChakraCore GitHub repository is now open

#291

Post by addicted »

mintplant wrote: post #174
Artemis2 wrote: post #62

Earlier quoted context omitted.

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.

Is this another [1] standard language feature that's being chalked up to Go now? Everything old is new again. [1] The first being statically-linked binaries.

Didn't JavaScript already have a reference spec going back at least a decade? I mean wouldn't a reference spec be a prerequisite for JavaScript becoming an ECMA standard?

Re: ChakraCore GitHub repository is now open

#292

Post by mcherm »

kemitchell wrote: post #263
viraptor wrote: post #237

Earlier quoted context omitted.

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.

The MIT License does not use the word "patent", but there are good arguments that MIT grants at least an implied patent license, perhaps even a (limited) express patent license. "Implied patent license" is the search string if you want to read more. Apache version 2.0, on the other hand, has an express patent license. There are very good reasons to prefer an express patent license.

> there are good arguments that MIT grants at least an implied patent license, perhaps even a (limited) express patent license.

I have not heard such arguments before. Can you provide a link to someplace where these legal arguments are explained?

Re: ChakraCore GitHub repository is now open

#293

Post by annnnd »

nilliams wrote: post #232
_greim_ wrote: post #181

Earlier quoted context omitted.

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

...that, or "PR bots" at work.

I guess I'll see by the downvotes this comment receives. ;)

Re: ChakraCore GitHub repository is now open

#294

Post by criddell »

patio11 wrote: post #259
criddell wrote: post #158

Earlier quoted context omitted.

A lot of small medical and dental practices operate on one or two PCs. Windows doing things like uploading your calendar and address books could end up being a HIPAA violation. Enterprise customers are fine because they have controls for everything, but small offices running Windows 10 Pro aren't so lucky.

Let me delicately observe that there is a straightforward reason why one has HIPAA-protected information in one's address book and it implies you make hundreds of HIPAA violations routinely.

I get what you are saying, but I'm not sure I agree.

If I buy a new car and it (by design) has a speedometer that sometimes shows the wrong speed or sometimes makes the lights malfunction and I get traffic tickets, do I have no right to be upset with the car manufacturer simply because I routinely speed and roll stop signs?

Re: ChakraCore GitHub repository is now open

#295

Post by mikekchar »

reitanqild wrote: post #74
Someone1234 wrote: post #60

Earlier quoted context omitted.

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.

The copyright holder can license a work under any license at any time. Although you can obviously issue an exclusive license for example, in most countries you can not simply dissolve the copyright (there is no concept of assigning something to the public domain). So practically, there is no way to write a license that stops the copyright holder from issuing a new and different license.

What the GPL does is forbid anyone who is not the copyright holder from changing the license. If you make a derived work from something and wish to use the GPL as the means for allowing you to make that derived work, then you must use the GPL.

The "better terms" that more permissive licenses give you is the ability to change the license when you make a derived work. Of course someone can fork the original open source version, but this is only useful if that person: 1) knows about it 2) has access to it 3) can build and install it for their platform. In many cases, more permissive licenses are preferred because vendors know that they can provide digital locks on the platforms that stop people from deploying free (as in freedom) versions. They wish to get the benefit of open source development, but still lock their users out of certain functionality.

Permissive licenses are useful, but they are not automatically better for everyone in every circumstance. Certainly I have a lot of useless bricks that used to be useful consumer electronics because my vendor doesn't let me upgrade them. Strangely the best piece of consumer hardware I ever bought was a bicycle navigation unit from Sony. GPL from top to bottom and they even gave you instructions on how to rebuild it and deploy it.

Does it matter? It certainly does to me. YMMV.

Re: ChakraCore GitHub repository is now open

#296

Post by AlexC04 »

krisdol wrote: post #175
bastawhiz wrote: post #80

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 f…

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

I've opened a few issues and sent a some pull requests along to various MS projects (couple of bits shipped).

I've found them generally to be quite supportive and encouraging in the vast majority of places.

I've been un-acknowledged on a couple and have felt un-welcome in only one instance. (In that one case I'm pretty sure the words we were using were all English, but I'm not sure we had the same meaning... I walked away from that one feeling dumber than where I started.)

All said and done, I have been wildly pleased with my experiences as a Microsoft community contributor on github... Though would say that there is some variability as you cross teams.

As you'd expect from people.

Re: ChakraCore GitHub repository is now open

#297

Post by bmarkovic »

mintplant wrote: post #174
Artemis2 wrote: post #62

Earlier quoted context omitted.

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.

Is this another [1] standard language feature that's being chalked up to Go now? Everything old is new again. [1] The first being statically-linked binaries.

If I'm not mistaken, the case with statically linked binaries in Go is more of a "It's not a bug, it's a feature" situation than being touted as Go invention. Besides, they are rectifiing that one if I'm not mistaken.

Re: ChakraCore GitHub repository is now open

#298

Post by School-Cotton »

fapjacks wrote: post #284
School-Cotton wrote: post #159

Earlier quoted context omitted.

Swift comes to mind.

Oh, you mean the language Apple created to make their fucking painful app development process easier?

Chill out. Of course they made it to benefit themselves in some way. They are not a charity.

The point is, they released it as open-source, which is what we are talking about in this thread.

Re: ChakraCore GitHub repository is now open

#299

Post by XzetaU8 »

somebehemoth wrote: post #141
wslh wrote: post #84

Earlier quoted context omitted.

I don't really like the user privacy approach on Windows 10 but I wonder if they will change that approach soon or someone else (third party) will came up with a tool to automatically handle this issue.

I found this tool in another HN discussion about this Win 10 privacy. I don't know if this tool works to solve the entire problem: https://github.com/10se1ucgo/DisableWinTracking/ . If anyone can vouch for this tool's effectiveness I would like to know.

http://www.ghacks.net/2015/08/14/comparison-of-windows-10-pr...

Re: ChakraCore GitHub repository is now open

#300

Post by yati »

AlexC04 wrote: post #296
krisdol wrote: post #175

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?

I've opened a few issues and sent a some pull requests along to various MS projects (couple of bits shipped). I've found them generally to be quite supportive and encouraging in the vast majority of places. I've been un-acknowledged on a couple and have felt un-welcome in only one instance. (In that one case I'm pretty sure the words we were using were all English, but I'm not sure we had the same meaning... I walked…

> In that one case I'm pretty sure the words we were using were all English, but I'm not sure we had the same meaning

I do not get what you mean here, are you willing to elaborate a bit? :)

Post reply on HN