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

211–220 of 324 posts

Re: ChakraCore GitHub repository is now open

#211

Post by balls187 »

abrookewood wrote: post #173
balls187 wrote: post #147

I'm skeptical. Over the past 5 years or so, Microsoft has lost developers as a core group. There are certainly interesting things happening out of their dev group, but with the rise of Cloud infrastructure, cheap (free) alternatives to WINS stacks rose tremendously in popularity. I was a Seattle Techstars 2013 Founder, and the only two teams using MSFT tech were those whose founders were ex-Microsoft employees. This…

In both cases the fault was in your own company and you are trying to use that to distinguish between two suppliers. There's no guarantee that Amazon will continue to be so lenient in the future (though you aren't the first person to mention them acting like this). For what it's worth, I think the new direction for MS is a good thing. They're far from my favourite company, but I dislike them less the more they releas…

You're right, our company made the mistake.

MSFTs tactics: allowing you to install SQL Server Enterprise without actually having a paid-for license, is similar to charging someone a fee for a service, and having them opt-out of any reoccuring subscription fees.

This is just anecdotal evidence that "new Microsoft" is the same as "old Microsoft."

I'm willing to believe that the folks working on this actually do care about contributing to open source and believe "rising tides raise all ships," but not for a second do I think that the decision makers at MSFT also believe that way.

Re: ChakraCore GitHub repository is now open

#212

Post by Matthias247 »

rayiner wrote: post #18

Small thing, but nice to see that the API is exposed as C (easy to write bindings for) instead of C++ (near-impossible to write bindings for).

It might not even be that small as it opens up a view possibilities that are not that easy with V8/C++, like using the Engine from Rust or other languages that only provide a C FFI.

Re: ChakraCore GitHub repository is now open

#213

Post by Matthias247 »

ksp4186 wrote: post #177
morebetterer wrote: post #149

Earlier quoted context omitted.

Ironically Microsoft had to create a V8 C++ API facade over Chakra in order for Node to compile with it. https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... It's interesting that the license of the Chakra shim is the V8 license: https://github.com/Microsoft/node/blob/chnext/deps/chakrashi...

That's correct. V8 license is required in v8-*.h files because they are v8 header files that chakra shim uses. The implementation files has Microsoft license. E.g. All files in https://github.com/Microsoft/node/tree/chnext/deps/chakrashi... Disclaimer: I work for Chakra team (powering node.js)

Just curious:

If I would like to write a native extension for a possible Chakra powered node.js, which methods would then be possible?

  - Use V8 C++ API
  - Use Chakra extension API
  - Use NAN
  - All of those?
And in your port are Nodes inbuilt native functions (like the libuv based IO functions) still using V8 APIs which are mapped to Chakra by this shim or are they reimplemented directly on top of Chakra APIs?

Re: ChakraCore GitHub repository is now open

#214

Post by dsp1234 »

smacktoward wrote: post #207
ybx wrote: post #194

Earlier quoted context omitted.

But the thing he's saying is that having io.js happen was possible. It's also possible in this scenario too.

Forking is always possible, but it was only practical because the community could plausibly claim to be able to put as much or more effort into building out their fork than Joyent could theirs. Microsoft is a much, much, much bigger company than Joyent. If they decide they want to take things in their own direction, they can throw an awful lot of programmers at making that happen. Which would make standing up a fork…

to take things in their own direction

And there is evidence that this is true. Node itself has had to make major changes to it's own code to account for unilateral V8 changes, and node really has had no choice but to suck it up and make corresponding changes. They could fork V8, but it's not likely since Google is always going to be able to throw more resources at it.

Re: ChakraCore GitHub repository is now open

#215

Post by untog »

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?

Aside, how come anything remotely questioning of Microsoft when there's an announcement is met with downvotes?

I don't think it is. However, I'll downvote criticism that isn't actually based on anything other than "well, you know, it's Microsoft so they won't", "remember extend, embrace, extinguish?" or "M$", etc. etc.

Criticism with actual backing is fine.

Re: ChakraCore GitHub repository is now open

#216

Post by dragandj »

balls187 wrote: post #147

I'm skeptical. Over the past 5 years or so, Microsoft has lost developers as a core group. There are certainly interesting things happening out of their dev group, but with the rise of Cloud infrastructure, cheap (free) alternatives to WINS stacks rose tremendously in popularity. I was a Seattle Techstars 2013 Founder, and the only two teams using MSFT tech were those whose founders were ex-Microsoft employees. This…

One thing that always baffled me was "routine software audits" by Microsoft, Oracle, and the likes.

So, you license a technology, and now your supplier can police you at their own wish. OK, there are situations when you have no choice - they are the only game in town. But in the last decade much of the infrastructure has been available in an open-source form.

I am surprised anyone would touch anything from such companies if there is a free alternative not connected to such companies (and in this case there are many).

Re: ChakraCore GitHub repository is now open

#217

Post by criddell »

Someone1234 wrote: post #189
abrookewood wrote: post #169

Earlier quoted context omitted.

It's actually REALLY HARD to disable OneDrive. I've tried about 3 separate methods and the damn thing keeps re-appearing. From what I read, it looks like Group Policy might work, but I don't have AD in our environment and haven't been able to test it.

You don't need AD to set the local security policy. Just type "gpedit.msc" into run. Then follow this[0]. [0] https://support.office.com/en-US/article/Turn-off-or-uninsta...

That makes me terribly uncomfortable because Microsoft is likely to just silently turn it back on in the future.

I used Powershell scripts to uninstall a bunch of the bloatware (XBox Music, Money, etc...) and they just come back. It's very frustrating.

Re: ChakraCore GitHub repository is now open

#218

Post by Matthias247 »

abchatra wrote: post #46
blinkingled wrote: post #26

Earlier quoted context omitted.

From the Roadmap document - it seems like JIT on Linux is not a priority? That's surprising. Is it due to technical issues or the whole idea is to have NodeJS on Windows use Chakra and let the community do the Linux part with JIT?

The first step is to get the runtime and interpreter running. Next step is to bring the jit up. Chakra is the hybrid engine where we have the interpreter, simple jit and full jit. The interpreter is the one which does all the profile data collection. Profile data is required to get the quality jit code. Declaimer: I work for Chakra team.

Hi! Thanks for explanation and another cool product!

One question that just came to my mind regarding this: Have you thought about a configurable/modular build where this interpreter/simple jit/full jit can be switched? Or is this perhaps already there?

I can think of some use cases where it would be interesting to build a modern and full featured JS engine in interpreter-only mode. E.g. to integrate it into platforms which don't allow JIT (iOS), to reduce the footprint or the attack surface. Or to be able to port it the other platforms without much effort - in the embedded domain there are still other processors than x86 and arm and other OSes than Windows, Linux and OSX floating around.

Re: ChakraCore GitHub repository is now open

#219

Post by [deleted] »

abchatra wrote: post #46
blinkingled wrote: post #26

Earlier quoted context omitted.

From the Roadmap document - it seems like JIT on Linux is not a priority? That's surprising. Is it due to technical issues or the whole idea is to have NodeJS on Windows use Chakra and let the community do the Linux part with JIT?

The first step is to get the runtime and interpreter running. Next step is to bring the jit up. Chakra is the hybrid engine where we have the interpreter, simple jit and full jit. The interpreter is the one which does all the profile data collection. Profile data is required to get the quality jit code. Declaimer: I work for Chakra team.

[deleted]

Re: ChakraCore GitHub repository is now open

#220

Post by smt88 »

criddell wrote: post #158
Someone1234 wrote: post #97

Earlier quoted context omitted.

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…

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.

Those practices use purpose-built software, not Outlook or some other Windows-readable program. Microsoft also offers HIPAA-compliant service agreements for such businesses.

If those offices aren't hiring someone who knows those things, they're probably not HIPAA compliant for many other reasons as well.

Post reply on HN