topaxi

The busier the better, for a while anyway, as it causes urgency, which reduces procrastination, which reduces self-guilt and increases rewarding experiences.

The downside in my experience is, one can only keep it up for a while until burnout and depression kicks in, which then severely increases ADHD symptoms and further fuels depression.

Optimizing numbers looks productive..

Reduced doesn't mean none though :)

Nope, they should be iterated in their defined order: https://tc39.github.io/ecma262/#sec-ordinaryownpropertykeys

I think they added this with ES2015.

xstate is a nice javascript library which even generates charts out of your defined states in your app: https://github.com/davidkpiano/xstate

sadly not used enough...

Nice to see Firefox competing in performance with Chrome again!

Macros and meta-programming aren't necessarily the same.

- FLAVOR: Desktop

- HEADLINE: Shared Electron

- DESCRIPTION: With the rise of JavaScript applications running on top of electron, it would be nice to have an electron package to depend on (much like Android WebView). This way not every Electron app weights over 50mb.

So much this! _If_ it succeeds in waking up from standby, only 2 of my 3 monitors work, this means I end up rebooting anyways...

If you don't mind downloading the whole file into the browsers memory this should do:

https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequ... https://developer.mozilla.org/en-US/docs/Web/API/URL/createO...

And then programmatically click the object URL.

The xxBy methods are just for convenience, usually you can provide your own function for each method.

Example:

    Ember.computed.map('myArray', function() {
      return foo.bar;
    })

vs.

    Ember.computed.mapBy('myArray', 'bar')

What you are asking for, would need a change to Ember.computed.uniq, allowing it to accept a custom function.

I'm using nightly builds since about two years and can't remember when exactly I enabled E10S. When I enabled it, I noticed around 20mb more memory usage. So imho this is a good thing, not that much memory for a lot more safety and if Firefox crashes for some reasons, all I have to do is clicking the "reload tabs" button.

I don't think parsing and executing is the bottleneck, especially on mobile connections. Do you have any numbers on this?