Seems like its only used once once in Playground.js for _.extend

Jeff created a mozilla-hacks codepen

• Remove debug output
• Hide behind a splash screen

STR:

1. Install HTTPS Everywhere from https://www.eff.org/https-everywhere
2. Restart Firefox to complete installation.
3. Visit Power Surge game: http://codepen.io/mozhacks/pen/xGgevw

OR, alternately, just directly load the HTTPS version of the game:
https://codepen.io/mozhacks/pen/xGgevw

ACTUAL RESULTS:
Game doesn't load in the lower CodePen window. (All that shows up is a Firefox Dev edition icon with a chat bubble.) Moreover, there's a shield in URL bar indicating that insecure content was blocked.

If you edit the CodePen source to use "//" URIs instead of "http://" URIs, then we'll load the correct HTTPS versions of resources. Here's a forked version with that fixed:
https://codepen.io/anon/pen/BNWzMj

(I still see some logged lines in the console about blocked resources, which seem to be from HTTP URIs that are hardcoded in our github-hosted scripts -- e.g. "gameover.ogg". We need to fix that as well, but that's probably less high-priority.)

should create pools for each entity and reuse them to avoid GC

Use page visibility API.

This way the game doesn't run when the developers digs into the profiles

Firefox

http://people.mozilla.org/~bgirard/cleopatra/#report=81dc5532edea82a6577d5af39b4975507e3ffb5c

Bailouts happen each frame 60 times per second:

1: Bailout_MonitorTypes at this on line 1 of http://localhost:8081/build/script/Playground.js line 5347 > Function:1
2: Bailout_MonitorTypes at this on line 1 of http://localhost:8081/build/script/Playground.js line 5347 > Function:1
3: Bailout_MonitorTypes at this on line 1 of http://localhost:8081/build/script/Playground.js line 5347 > Function:1
4: Bailout_MonitorTypes at this on line 1 of http://localhost:8081/build/script/Playground.js line 5347 > Function:1
5: Bailout_MonitorTypes at this on line 1 of http://localhost:8081/build/script/Playground.js line 5347 > Function:1
6: Bailout_MonitorTypes at this on line 1 of http://localhost:8081/build/script/Playground.js line 5347 > Function:1 

Chrome

Chrome Profiler shows ⚠️ icons for all cq. methods as Bad value context for arguments value:

Except music - I am using sounds from past projects. Some are heavy copyrighted.

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

For developers and devtools / makes sense where target-ms-per-frame is calculated based on baseline score. Visual indicator might be nice too; could be just text switching colors or an actual interface element like a closing circle (when it closes; unlock!)

Things to screw up:

• Utils.distance, nearest, extend
• Ship::foresightCollision, getTarget, linearMovement, ::linearMovement
• Bullet::step (refactor to separate)
• Particle::step (refactor to separate)
• Resource::step (refactor to separate)
• Add more ideas

Baseline is a benchmark score that measures optimized code performance that does the game-typical operations (math and canvas currently) until a stable score is achieved.

WIP: http://testno.de/playground/baseline/index.html

Because devtools are remote friendly

1. Increase samples amount
2. Decrease tween speed

• Remove old files (CircleExplosion)
• Remove dead and uncommented code
• Make code warning free
• Document

DevTools opening will cause the window to resize which now isn't handled smoothly

A prototype demonstrating "keep pointer on top of object to perform action"