ChakraCore GitHub repository is now open

Post by tracker1 » Thu, Jan 14, 2016, 3:48 PM UTC

dragonwriter wrote: post #282

tracker1 wrote: post #264

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.

Post by realityking » Thu, Jan 14, 2016, 4:15 PM UTC

zbraniecki wrote: post #246

magicalist wrote: post #90

Earlier quoted context omitted.

Actually, try it with current Chrome Canary (V8 version 4.9.355). They just hit 92% with no flags.

That's awesome! With SpiderMonkey hitting 90%, WebKit at 81%, V8 92% and Chakra at 80%, ES6 as production target becomes realistic! I'm wondering when Android/iOS default browsers will get updates because that's going to be the one remaining blocker. (and IE11 of course... but that's just waiting for userbase to move away from it :/)

Post by dsp1234 » Thu, Jan 14, 2016, 4:58 PM UTC

mraleph wrote: post #229

dsp1234 wrote: post #203

Earlier quoted context omitted.

Optimization decisions that V8 team have made are much more universal than it might seem. That's certainly possible, but maybe a competing VM can do better, but finds that everyone has coded specific V8 optimizations. They may be hesitant to push out their implementation. It may be a better optimization, but it causes existing code to run slower on their VM. Thus back to the original statement that implementation qui…

> The variable has to be in the local scope and can't be in any higher or lower scope, not just a global scope (which your words acknowledge, but your code snippet doesn't) Sure! I am just trying to say that in my opinion whenever you have a non-local variable used as iteration variable in for-in then you most probably have a bug in your code. I tried to illustrate this with an global variable example because it's a…

  function Intercept(obj1, obj2){
     for(var key in obj1){
       obj2[key] = function(){
           console.log('called: ', key);
           obj1[key]();
       }
     }
  }

Post by kemitchell » Thu, Jan 14, 2016, 6:17 PM UTC

mikekchar wrote: post #295

reitanqild wrote: post #74

Earlier quoted context omitted.

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

Post by mraleph » Fri, Jan 15, 2016, 12:56 AM UTC

STRML wrote: post #270

mraleph wrote: post #229

Earlier quoted context omitted.

> The variable has to be in the local scope and can't be in any higher or lower scope, not just a global scope (which your words acknowledge, but your code snippet doesn't) Sure! I am just trying to say that in my opinion whenever you have a non-local variable used as iteration variable in for-in then you most probably have a bug in your code. I tried to illustrate this with an global variable example because it's a…

Hey, maybe you're the right person to ask - why does `arguments` so easily deoptimize in every major engine (well, V8 and SpiderMonkey, at least)? It seems that engines could easily detect the most common munging of `arguments` (such as [].slice.call(arguments), Array.prototype.slice.call(arguments). Array.from(arguments) and the like) and allow those to be optimized. Doing so would speed up a very large amount of co…