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

Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

github.com

Post reply on HN
Print view View original

31–40 of 104 posts

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#31

Post by magicalist »

coldtea wrote: post #26
frik wrote: post #17

What about the license of Node.js/Chromium? Isn't linking a closed source library (Chakra) problematic? You know it includes multiple code parts under various licenses, Wikipedia says: BSD license, MIT License, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed ( http://en.wikipedia.org/wiki/Chromium_(web_browser) ) There is a reason why major open source projects like Linux, etc. choose licenses like GNU GPL v2+. http://en.w…

> Isn't linking a closed source library (Chakra) problematic? Yeah, because the tech world didn't have enough problems with projects being immature, unreliable, stale 30+ year designs, abandoned, incompatible, not provided by a specific distribution, coflicting, patented and 100 other issues to consider. It just had to also add 200 legal distinctions behind what you can and you cannot do, and how you can link stuff a…

If you're asking if software licenses are important, the answer is yes, they're very important.

To the GP, though, I don't immediately see how linking to Chakra in this way would be a license issue. The more important thing is the license information for Node, though, not Chromium: https://github.com/joyent/node/blob/master/LICENSE (some overlap but quite a bit that doesn't)

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#32

Post by SXX »

mkr-hn wrote: post #24
frik wrote: post #18

Earlier quoted context omitted.

Read for yourself: http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish and http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt

Looks like it's been close to a decade. The CEO responsible for that whole ordeal is gone. When do people decide Microsoft has behaved long enough to be given a second chance?

I think it's pretty clear that this would take long time. Reputation it's not something company can get just by changing CEO or releasing few things as open source.

After all they still continue their aggressive patents usage and there is still uncertainness around audio/video codecs for web standards mainly because of Microsoft. Pretty sure others may remember some areas where their politics didn't changed for a bit.

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#33

Post by poizan42 »

frik wrote: post #17

What about the license of Node.js/Chromium? Isn't linking a closed source library (Chakra) problematic? You know it includes multiple code parts under various licenses, Wikipedia says: BSD license, MIT License, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed ( http://en.wikipedia.org/wiki/Chromium_(web_browser) ) There is a reason why major open source projects like Linux, etc. choose licenses like GNU GPL v2+. http://en.w…

It's already linked against tons of closed source libraries when built on windows, why would one more make a difference?

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#34

Post by aeroevan »

elisee wrote: post #28
doczoidberg wrote: post #16

Earlier quoted context omitted.

the chances are good: http://blogs.windows.com/buildingapps/2015/05/12/bringing-no...

This tweet from May 1 might be related: https://twitter.com/conoro/status/594196246727774208

I'm betting raspberry pi 2 only (i.e. armv7 only) since that's all Windows IoT runs on. Doubt they'd put the effort into armv6 for all of the existing raspberry pi 1 devices.

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#35

Post by frik »

mkr-hn wrote: post #24
frik wrote: post #18

Earlier quoted context omitted.

Read for yourself: http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish and http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt

Looks like it's been close to a decade. The CEO responsible for that whole ordeal is gone. When do people decide Microsoft has behaved long enough to be given a second chance?

> The CEO responsible for that whole ordeal is gone. When do people decide Microsoft has behaved long enough to be given a second chance?

If the company clearly changes it's course, right? Though it doesn't seem to be the case, despite two CEO changes since Bill Gates. Recent news show more or less what they are still up-to.

Yesterdays plans to stop producing Windows and "Win10 as a service": https://news.ycombinator.com/item?id=9521151

TypeScript influences the ES6/JavascriptNext feature & syntax development - lead by Mr. Hejlsberg (TurboPascal) who was responsible for J++, Windows Foundation Classes and C#. In 2012 Hejlsberg announced his new project TypeScript — a superset of JavaScript. (https://en.wikipedia.org/wiki/Anders_Hejlsberg )

Read Bill Gates (former internal) 1994 memo: "Windows: The Next Killer Application on the Internet": http://www.microsoft.com/about/companyinformation/timeline/t...

"The memo starts with a background on the Internet in general, and then proposes a strategy on how to turn Windows into the next "killer app" for the Internet."

The Internet plan "Microsoft Network": https://youtu.be/kGYcNcFhctc?t=17m16s

And the Office format thing in 2007, the Silverlight thing, the XBoxOne launch thing. It was just not as public, as they were not that successful.

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#36

Post by consptheorist »

bhouston wrote: post #10

It would be cool if the JavaScript engine was interchangable in NodeJS and IO.JS so you could pick Chakra, V8 or SpiderMonkey very easily. SpiderMonkey is faster than V8 these days on a lot of benchmarks.

I can attest to that.

I was experimenting a couple of days ago with high duty and extreme DOM nodes crunching and FF's SpiderMoneky blew Chrome's V8 out of the water for 7 - 9 multiples gain in performance measured in time elapsed to complete the operations.

Chrome's V8 engine at this point is so overrated

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#37

Post by chc »

frik wrote: post #17

What about the license of Node.js/Chromium? Isn't linking a closed source library (Chakra) problematic? You know it includes multiple code parts under various licenses, Wikipedia says: BSD license, MIT License, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed ( http://en.wikipedia.org/wiki/Chromium_(web_browser) ) There is a reason why major open source projects like Linux, etc. choose licenses like GNU GPL v2+. http://en.w…

Based on that license list, I don't see how any of those would present a problem. Do you?

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#38

Post by ksherlock »

bryanlarsen wrote: post #25
pionar wrote: post #20

Earlier quoted context omitted.

Actually, I was thinking, what's up node? Each dependency keeps a private copy of its dependencies? How messed up is that? Or am I just reading that wrong?

That's a feature, not a bug. It lets A rely on version 0.9 of X while B relies on version 0.8.

That can introduce other problems.

https://news.ycombinator.com/item?id=8213273

http://i.imgur.com/AZJti8I.png

Re: Temporary fork enables Node.js to optionally use the Chakra JavaScript engine

#39

Post by magicalist »

elisee wrote: post #5

"This temporary fork enables Node.js to optionally use the Chakra JavaScript engine on Windows 10, allowing Node.js to run on Windows on ARM." (the submission title has been updated after I posted this, was initially "MS releases a fork of Node that uses the Chakra JavaScript engine instead of V8") Looks like they intend to merge back with node mainline... ? EDIT: Found this: http://blogs.windows.com/buildingapps/201…

> They're doing this to be able to run Node.js apps on Windows 10 ARM (on which V8 supposedly doesn't run?)

V8 definitely has an ARM runtime, so maybe this is a result of the restrictions on what's allowed to run on the platform? (e.g. iOS and Windows Phone don't allow JIT compilers except the ones provided by the platform itself)

Post reply on HN