Live data from Hacker News

ChakraCore GitHub repository is now open

blogs.windows.com

311–320 of 324 posts

Re: ChakraCore GitHub repository is now open

#311
post #116

Earlier quoted context omitted.

This is OT, but didn't BeOS name its components -Kit before Apple did that?

No, the *Kit suffix comes from NeXT, which Apple acquired and is where Mac OS X (and iOS) are derived from. NeXT started using that terminology in the 1980s, before Be Inc. was started (in 1991).

Thank you for clarifying that!

Re: ChakraCore GitHub repository is now open

#312

Earlier quoted context omitted.

Honestly, I think HIPAA may have been a net negative to the medical industry and has probably prevented the basic sharing between medical practices and related services that it was supposed to more readily allow. The lawyers have benefited a lot, and the abstract details insurance companies have gathered, but refuse to disclose based on HIPAA grounds to their own customers about themselves and medical practitioners t…

HIPAA mandates that the people have access to their own PHI held by covered entities, a mandate which did not exist before HIPAA, so it did the opposite of creating additional barriers to patients getting access to their own data.

Patients are denied access to their own records in the name of HIPAA. During a recent medical crisis this happened to me. No amount of threatening or cajoling would get them to release my images to my designated 2nd opinion.

Re: ChakraCore GitHub repository is now open

#313

Earlier quoted context omitted.

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.

Same thing happened to me. Drives me crazy.

Re: ChakraCore GitHub repository is now open

#314

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

Thanks. I guess I'll try once again.

Re: ChakraCore GitHub repository is now open

#315
post #292

Earlier quoted context omitted.

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

I don't know a single online source worthy of recommendation, so I'm afraid you'll have to do your own searching. But in a nutshell, at least under US law: 1. The permission language "deal in the Software without restriction" is very broad. 2. Of the more specific, enumerated permissions "use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of" the terms "copy", "modify", "publish", "distribu…

Thank you! Incomplete though that may have been, it still was very educational.

Re: ChakraCore GitHub repository is now open

#316

Earlier quoted context omitted.

Its a long goal as of now that everyone want to achieve. You can follow this discussion at https://github.com/nodejs/nan/issues/349

That thread doesn't show a lot of promise towards an engine neutral API.

True. I think it will pick up once Node.js + Chakracore (or other Javascript Engines) starts taking momentum.

Re: ChakraCore GitHub repository is now open

#317

Earlier quoted context omitted.

HIPAA mandates that the people have access to their own PHI held by covered entities, a mandate which did not exist before HIPAA, so it did the opposite of creating additional barriers to patients getting access to their own data.

You'd be surprised how it's worked out in reality though... I'm not against what HIPAA was meant to do. I just with the actual circumstances allowed for the more easy communications system that was hoped for... not filling out 100+ fields across 4-5 pages when seeing a new doctor for the first time.

No, I wouldn't be surprised, having worked in the field for most of the time that HIPAA has been in force, and having had experience with trying to get information released by health entities before HIPAA. While HIPAA's requirements may allow more room for inconvenience than they should, and plenty of covered entities fall short of the requirements, the situation is miles better than it was without HIPAA, where such information was often treated as proprietary, competitive information and there was no general mandate -- and thus no recourse in many cases -- for disclosure to the patient.

And most of the history you fill out when seeing a new doctor has nothing to do with whether or not they can get old records -- they want the same information even if they have the old records.

Re: ChakraCore GitHub repository is now open

#318

Earlier quoted context omitted.

HIPAA mandates that the people have access to their own PHI held by covered entities, a mandate which did not exist before HIPAA, so it did the opposite of creating additional barriers to patients getting access to their own data.

Patients are denied access to their own records in the name of HIPAA. During a recent medical crisis this happened to me. No amount of threatening or cajoling would get them to release my images to my designated 2nd opinion.

To put it simply, anyone claiming HIPAA is the reason for that is just lying (since HIPAA has no such requirement) and would invent some other excuse -- or simply refuse without explanation -- without HIPAA. In fact, HIPAA patient access requirement mandates that patients have access to, and a right to receive copies of, their records under most circumstances, and refusal to provide such access is an actionable violation of HIPAA -- without HIPAA, there would be no recourse.

Re: ChakraCore GitHub repository is now open

#319

Earlier quoted context omitted.

So getting rid of GPLv3 means they can't be doing anything good in open source? Nevermind CUPS, LLVM, Swift, and WebKit just to name a few? GPL isn't the only license in town, and clearly there are disadvantages to it.

What "disadvantage" are you referring to? The one that forces companies to give back in the same manner that allows them to use the work of others for free? Yeah, that is so shitty.

The problem is that you need to give back everything, even if the GPL code you are using is a tiny part of your product. That's why I prefer LGPL.

Re: ChakraCore GitHub repository is now open

#320

Earlier quoted context omitted.

Patients are denied access to their own records in the name of HIPAA. During a recent medical crisis this happened to me. No amount of threatening or cajoling would get them to release my images to my designated 2nd opinion.

To put it simply, anyone claiming HIPAA is the reason for that is just lying (since HIPAA has no such requirement) and would invent some other excuse -- or simply refuse without explanation -- without HIPAA. In fact, HIPAA patient access requirement mandates that patients have access to, and a right to receive copies of, their records under most circumstances, and refusal to provide such access is an actionable viola…

Pre HIPAA I never had a problem obtaining my records. The trouble is less-knowledgeable health gatekeepers are relentlessly indoctrinated into believing that privacy is paramount. A records request that doesn't follow a rigid checklist is defaulted to REJECT. And it is in the name of protecting the patient's privacy.
Post reply on HN