Live data from Hacker News

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

github.com

21–30 of 104 posts

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

#21
post #3

Can I browse my node_modules folder in Explorer yet? [1] [1] https://github.com/joyent/node/issues/6960

With every new version of Windows, Explorer gets worse and worse. I personally switched to Directory Opus long time ago.

This isn't a limitation of Explorer, but actually is a very well documented part of the Windows API. MAXPATH has always been 260 characters.

https://msdn.microsoft.com/en-us/library/aa365247(VS.85).asp...

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

#22
JXcore is another fork of Node that makes the VM pluggable, supporting both V8 and SpiderMonkey. I wonder how similar Microsoft's and JXcore's VM abstraction layers are and whether Node upstream would accept them. Drawing a hard line between the Node native code and the VM would make binary addon compatibility more stable (and lessen the need for NaN, the "Native Abstractions for Node").

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

#23

Embrace: https://nodejstools.codeplex.com/ http://azure.microsoft.com/en-us/develop/nodejs/ Extend: https://github.com/Microsoft/node Extinguish: ?

Given all that Microsoft has been doing lately I'd really be surprised if this is all an elaborate ruse to squash node. Having been around when the actual "embrace, extend, extinguish" was running at full throttle, though, I can tell you what it does looks like:

"Full access to UWP APIs from Node.js applications"

When you use platform-exclusive features then you not only lose a major strength of node, but you put the owner of that platform in a position to start pushing developers around.

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

#24
post #18
post #12

Earlier quoted context omitted.

When was the last time they went all the way?

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?

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

#25
post #20
post #9

Earlier quoted context omitted.

Wow, what's up Microsoft?

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.

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

#26
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 and under what circumstances.

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

#27

Embrace: https://nodejstools.codeplex.com/ http://azure.microsoft.com/en-us/develop/nodejs/ Extend: https://github.com/Microsoft/node Extinguish: ?

Might as well post some Friends quotes and some Pearl Jam videos.

I mean, as long as we are discussing 90s stuff.

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

#28

Will this work on Raspberry Pi?

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

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

#29
post #21

Earlier quoted context omitted.

With every new version of Windows, Explorer gets worse and worse. I personally switched to Directory Opus long time ago.

This isn't a limitation of Explorer, but actually is a very well documented part of the Windows API. MAXPATH has always been 260 characters. https://msdn.microsoft.com/en-us/library/aa365247(VS.85).asp...

How long will Microsoft wait till the fix MAXPATH and other limitations? (and various other Win32 limitations that are usually a legacy porting helper thing from Win16). There would have been a good point with the introduction of Win64API - but Microsoft forgot about it and was apparently busy with something else.

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

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

I don't call that a feature. There's other ways of doing version pinning without junking up my filesystem.
Post reply on HN