[B! javascript] manatenã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

manaten id:manaten

javascriptã«é–¢ã™ã‚‹manatenã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (621)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

js13kGamesï¼šã‚³ãƒ¼ãƒ‰ã‚´ãƒ«ãƒ•åž‹ã‚²ãƒ¼ãƒ é–‹ç™ºå¤§ä¼š
ã“ã®è¨˜äº‹ã¯ â€œjs13kGames: Code golf for game devsâ€ ã®æŠ„è¨³ã§ã™ã€‚ 13KBã€‚KB ãªã‚“ã¦æœ€è¿‘ã§ã¯é›€ã®æ¶™ã»ã©ã®ãƒ‡ãƒ¼ã‚¿é‡ã§ã™ãŒã€ã‚²ãƒ¼ãƒ ã®æ´å²ã‚’é¡ã‚Œã°å…ˆé§†è€…ãŸã¡ã¯ã¨ã‚“ã§ã‚‚ãªã„åˆ¶ç´„ã®ä¸ã§ã‚²ãƒ¼ãƒ ã‚’ä½œã£ã¦ããŸã¨ã„ã†ã“ã¨ã«æ°—ã¥ãã¯ãšã§ã™ã€‚ ä¸€ä¾‹ã‚’æŒ™ã’ã‚‹ã¨ã€çš†ã«æ„›ã•ã‚ŒãŸã‚¢ã‚¿ãƒª 2600 ã® RAM ã¯ã€ã»ã‚“ã® 128 ãƒã‚¤ãƒˆã—ã‹ãªãã€ã‚«ã‚»ãƒƒãƒˆã‚’ã•ã—ã¦ã‚‚ 4 KB å¢—ãˆã‚‹ã ã‘ã§ã—ãŸã€‚ã“ã¨ã‚ã–ã«ã‚‚ã‚ã‚‹é€šã‚Šã€åˆ¶ç´„ã¯å‰µé€ ã®æ¯ã§ã™ã€‚ãã‚“ãªã‚²ãƒ¼ãƒ ã®ã‚³ãƒ³ãƒšãƒ†ã‚£ã‚·ãƒ§ãƒ³ã€js13kGames ã®å£ç¯€ãŒã‚„ã£ã¦ãã¾ã—ãŸã€‚ã“ã‚Œã¯ zip åœ§ç¸®ã—ã¦ 13,312 ãƒã‚¤ãƒˆä»¥å†…ã§ã‚ã‚‹ã“ã¨ã‚’æ¡ä»¶ã«ã€ã‚²ãƒ¼ãƒ ã®å‰µé€ æ€§ã‚’ç«¶ã†å¤§ä¼šã§ã™ã€‚ HTML5 ã‚²ãƒ¼ãƒ é–‹ç™ºè€…å‘ã‘ã®å¤§ä¼š js13kGames ã¯ HTML5 ã§ã‚²ãƒ¼ãƒ ã‚’ä½œã‚‹é–‹ç™ºè€…ã®ãŸã‚ã®å¤§ä¼šã§ã€2012 å¹´ã‚ˆã‚Šæ¯Žå¹´é–‹å‚¬ã•ã‚Œã¦ã„ã¾ã™ã€‚ä½œæˆã™ã‚‹ã‚²ãƒ¼ãƒ ã®ãƒ•ã‚¡ã‚¤ãƒ«ã‚µ
manaten 2016/08/15
ã“ã†ã„ã†å·¥å¤«ã€è¦‹ã¦ã¦ãŸã®ã—ã„

javascript
ãƒªãƒ³ã‚¯
GitHub - regl-project/regl: ðŸ‘‘ Functional WebGL
regl simplifies WebGL programming by removing as much shared state as it can get away with. To do this, it replaces the WebGL API with two fundamental abstractions, resources and commands: A resource is a handle to a GPU resident object, like a texture, FBO or buffer. A command is a complete representation of the WebGL state required to perform some draw call. To define a command you specify a mix
manaten 2016/08/08
"reglÂ is a fast functional framework for WebGL"

JavaScript
ãƒªãƒ³ã‚¯
Why "use strict" improves performance 10x in this example?
Following the question Extending String.prototype performance I am really intrigued, because just adding "use strict" to a String.prototype method improved performance 10 times. The explanation by bergi is short and does not explain it to me. Why there is such a dramatic difference between two almost identical methods, that only differ in "use strict" at the top? Can you explain in more detail and
manaten 2016/07/20
javascript
ãƒªãƒ³ã‚¯
JavaScript Annotated â€“ January 2016 | The WebStorm Blog
manaten 2016/02/03
javascript
ãƒªãƒ³ã‚¯
codeplanet.io
This domain was recently registered at Namecheap.com. Please check back later! codeplanet.io 2021 è‘—ä½œæ¨©. ä¸è¨±è¤‡è£½ ãƒ—ãƒ©ã‚¤ãƒã‚·ãƒ¼ãƒãƒªã‚·ãƒ¼
manaten 2016/01/19
Promise.allã§awaitã®ä¸¦åˆ—åŒ–ã€‚async/awaitã®ä¸–ç•Œã¨Promiseã®ä¸–ç•Œè¡Œã£ãŸã‚Šæ¥ãŸã‚Šã™ã‚‹ã®ã€æµè¡Œã£ã¦ããŸã‚‰ã‚¤ãƒ‡ã‚£ã‚ªãƒ ã§ããã†

javascript
ãƒªãƒ³ã‚¯
Danger of using async/await in ES7
Update: the text below is only applicable for babel code running under older Node.js versions (v6.x and prior). Starting with Node.js v7.x, unhandled promise rejections are now automatically shown in console. In future versions of Node.js unhandled promise rejections will cause code execution to exit with non-zero exit code. This is a mini-post explaining a small (not so) hidden danger of using as
manaten 2016/01/19
async/awaitã§ã®ã‚¨ãƒ©ãƒ¼ãƒãƒ³ãƒ‰ãƒªãƒ³ã‚°ã«ã¤ã„ã¦

javascript
ãƒªãƒ³ã‚¯
decaffeinate â€” CoffeeScript in, JSNext out.
{ pow, sqrt } = Math sq = (x) => pow(x, 2 ) # Represents a 2D point. class Point constructor : ( @ x, @ y) -> distanceTo : ({x, y}) -> xd = sq(x - @ x) yd = sq(y - @ y) sqrt(xd + yd) var { pow, sqrt } = Math ; var sq = (x) => pow(x, 2 ); // Represents a 2D point. class Point { constructor (x, y) { this .x = x, this .y = y; } distanceTo ({x, y}) { var xd = sq(x - this .x); var yd = sq(y - this .y);
manaten 2016/01/15
çŸ¥ã‚‰ãªã„ã†ã¡ã«ã‚µã‚¤ãƒˆã¨replãŒã§ãã¦ã‚‹ã€‚ãŸã æ‰‹å…ƒã®coffeeçµæ§‹å¯¾å¿œã—ã¦ãªã„æ–‡æ³•ã‚ã£ã¦ä½¿ãˆãªã„ãªãƒ»ãƒ»ãƒ»

javascript
ãƒªãƒ³ã‚¯
http://eventualbuddha.github.io/decaffeinate/repl/
manaten 2016/01/15
javascript
ãƒªãƒ³ã‚¯
Why doesn't instanceof work on instances of Error subclasses under babel-node?
manaten 2016/01/09
babel

javascript
ãƒªãƒ³ã‚¯
GitHub - tj/frontend-boilerplate: webpack-react-redux-babel-autoprefixer-hmr-postcss-css-modules-rucksack-boilerplate (unmaintained, I don't use it anymore)
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
manaten 2016/01/01
javascript
ãƒªãƒ³ã‚¯
ãƒã‚°å‡ºåŠ›ãƒ©ã‚¤ãƒ–ãƒ©ãƒª node-bunyan - ã¾ã‚‹ã¾ã‚‹ã“ãµã“ãµ
ã“ã®è¨˜äº‹ã¯Node.js Advent Calendar ãã®2 ã®ï¼•æ—¥ç›®ã®è¨˜äº‹ã§ã™ã€‚ express ã®ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ãƒã‚° express ã§ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ãƒã‚°ã‚’å‡ºåŠ›ã—ãŸã„ã€‚ express-generator ãªã©ã§ express ã‚¢ãƒ—ãƒªã‚’ä½œã‚‹ã¨ã€æœ€åˆã‹ã‚‰ morgan ãŒ ä½¿ã‚ã‚Œã¦ã„ã¾ã™ãŒã€ã“ã‚Œã¯ã‚¢ã‚¯ã‚»ã‚¹ãƒã‚°ã‚’ä¿å˜ã™ã‚‹ã‚‚ã®ã§ã€ ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ãƒã‚°ã‚’å‡ºåŠ›ã™ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“ã€‚ æœ‰åãƒ‰ã‚³ãƒã‚’æŽ¢ã£ã¦ã¿ãŸã¨ã“ã‚ã€log4js ã¨ bunyan ãŒã‚ã‚‹ã¿ãŸã„ãªã®ã§ã€ bunyan ä½¿ã„ã¾ã™ã€‚ ãƒãƒ‹ãƒ¤ãƒ³ã¨èªã‚€ã¿ãŸã„ã§ã™ã€‚ã¶ãƒ¼ã«ã‚ƒã‚“ã£ã¦èªã‚“ã§ã¾ã—ãŸã€‚ã¶ãƒ¼ã«ã‚ƒã‚“ã‹ã‚ã„ã„ã‚ˆã¶ãƒ¼ã«ã‚ƒã‚“ã€‚ ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ« npm install bunyan ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ã¾ã—ã‚‡ã†ã€‚ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã™ã‚‹ã¨ bunyan ã‚³ãƒžãƒ³ãƒ‰ã¨ã„ã† ãƒã‚°ã‚’ã„ã„æ„Ÿã˜ã«è¦‹ã‚„ã™ãã™ã‚‹ãƒ„ãƒ¼ãƒ«ã‚‚ã¤ã„ã¦ãã¾ã™ã€‚ã“ã‚Œã¯å¾Œè¿°ã—ã¾ã™ã€‚ Introd
manaten 2015/12/24
javascript
ãƒªãƒ³ã‚¯
@babel/preset-es2015 Â· Babel
As of Babel v6, all the yearly presets have been deprecated. We recommend using @babel/preset-env instead.
manaten 2015/12/21
javascript
ãƒªãƒ³ã‚¯
Why is `(0,obj.prop)()` not a method call?
This blog post explores references, a mechanism used by the ECMAScript language specification to explain the difference between the following two expressions: obj.prop() (0, obj.prop)() Method calls versus function callsÂ Â # Consider the following object: var obj = { getThis: function () { "use strict"; return this; }, }; If you call obj.getThis, you have a method call (this points to the object in
manaten 2015/12/21
(0,obj.prop)ã™ã‚‹ã¨dereferenceãŒèµ·ã“ã‚‹ã®ã§GetThisValue(V)ã®å€¤ãŒå¤‰ã‚ã‚‹ã€‚ReferenceãŒã‚ã‚‹ã“ã¨ã§è¤‡æ•°ã® storage location ã‚’ç°¡æ½”ã«ä»•æ§˜è¨˜è¿°ã§ãã¦ã„ã‚‹

javascript
ãƒªãƒ³ã‚¯
RxJSã‚’å‹‰å¼·ã—ãŸ1 - babie, you're my home
Reactive Programming With Rxjs: Untangle Your Asynchronous Javascript Code ä½œè€…: Sergi Mansillaå‡ºç‰ˆç¤¾/ãƒ¡ãƒ¼ã‚«ãƒ¼: Pragmatic Bookshelfç™ºå£²æ—¥: 2015/12/25ãƒ¡ãƒ‡ã‚£ã‚¢: ãƒšãƒ¼ãƒ‘ãƒ¼ãƒãƒƒã‚¯ã“ã®å•†å“ã‚’å«ã‚€ãƒ–ãƒã‚°ã‚’è¦‹ã‚‹ Reactive Programming with RxJSã®é›»åæ›¸ç±ç‰ˆã‚’è²·ã£ã¦å‹‰å¼·ã—ã¦ã„ã¾ã™ã€‚ç›®çš„ã¯æ°—ã«ãªã£ã¦ã„ã‚‹JavaScriptãƒ•ãƒ¬ãƒ¼ãƒ ãƒ¯ãƒ¼ã‚¯Cycle.jsã‚’ç†è§£ã™ã‚‹ãŸã‚ã§ã™ã€‚ã“ã®æœ¬ã®æœ€çµ‚ç« ã«ã‚‚Cycle.jsã®ã•ã‚ã‚ŠãŒæ›¸ã„ã¦ã‚ã‚‹ã£ã½ã„ã®ã§æ¥½ã—ã¿ã«ã—ã¦ã„ã¾ã™ã€‚ãŸã ã€Rx/Cycle.jsã¯ã¨ã‚ã‚‹å„ªç§€ãªã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãŒæŽ¡ç”¨ã—ãªãŒã‚‰ã‚‚ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆãŒé “æŒ«ã—ã¦ãŠã‚Šãƒ€ãƒ¡ãªã‚¢ãƒ¬ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“ã€‚ãŸã ã€RxãŒã©ã“ã¾ã§ä½¿ãˆã‚‹ã‹ã©ã†ã‹ã‚ã‹ã‚Šã¾ã›ã‚“ãŒã€ã‚¹ãƒˆãƒªãƒ¼ãƒ ã®æ‰±ã„ã¯ä»Šå¾Œã®ç³§ã«ãªã£
manaten 2015/12/21
javascript
ãƒªãƒ³ã‚¯
isMounted is an Antipattern â€“ React Blog
This blog site has been archived. Go to react.dev/blog to see the recent posts. As we move closer to officially deprecating isMounted, itâ€™s worth understanding why the function is an antipattern, and how to write code without the isMounted function. The primary use case for isMounted() is to avoid calling setState() after a component has unmounted, because calling setState() after a component has
manaten 2015/12/21
javascript
ãƒªãƒ³ã‚¯
schemizeã®node.jsç‰ˆä½œã£ãŸ - Qiita
shcemizeã¨ã„ã†ã€JSONã‹ã‚‰JSON Schemaã‚’ç”Ÿæˆã™ã‚‹ä¾¿åˆ©ãªGemãŒã‚ã‚‹ã€‚ schemizeã‚’ä½¿ã†ãŸã‚ã ã‘ã«Gemfileã‚’æ›¸ãã®ãŒå«Œã ã£ãŸã®ã§ã€node-schemizeã‚’ä½œã£ãŸã€‚ // ã¨ã‚Šã‚ãˆãšã‚°ãƒãƒ¼ãƒãƒ«ã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ« $ npm install -g schemize // ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆ $ echo '{ "key": "value" }' | schemize {"type":"object","properties":{"key":{"type":"string"}}} // ãƒ—ãƒªãƒãƒ¼ $ echo '{ "key": "value" }' | schemize --pretty { "type": "object", "properties": { "key": { "type": "string" } } } // ãƒ—ãƒªãƒãƒ¼ã¯ã‚¤ãƒ³ãƒ‡ãƒ³ãƒˆæ•°ã¨"tab"ãŒæŒ‡å®šå¯èƒ½
manaten 2015/12/21
javascript
ãƒªãƒ³ã‚¯
fetch-plus/README.md at master Â· RickWong/fetch-plus
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
manaten 2015/12/21
javascript
ãƒªãƒ³ã‚¯
Using ES6 with gulp â€” Mark Goodyear â€”Â Front-end developer and designer
Nov 2nd, 2015 As of node 4, we're now able to use ES2015 without the need for Babel. However modules are not currently supported so you'll need to use `require()` still. Checkout the node docs for more info on what's supported. If you'd like module support and to utilise Babel, read on. Post updated to use Babel 6. With gulp 3.9, we are now able to use ES6 (or ES2015 as it's now named) in our gulp
manaten 2015/12/21
javascript
ãƒªãƒ³ã‚¯
gulp-iconfont
Create icon fonts from several SVG icons You can test this library with the frontend generator. Warning: While this plugin may still be useful for fonts generation or old browser support, you should consider using SVG icons directly. Indeed, when I created gulp-iconfont and all its related modules, using SVG icons was just not realistic for a wide browser support but I was already convinced that S
manaten 2015/12/20
javascript
ãƒªãƒ³ã‚¯
JavaScript Developer Survey Results â€” Pony Foo
The end of year is drawing close and the JavaScript Developer Survey has now ended. The survey received an unimagined amount of replies and Iâ€™m excited to share the results with you! There were over 5000 responses, 5350 to be exact, and I canâ€™t wait to share the details. Before that I want to thank everyone who chipped in. This is a great time to be a part of the JavaScript community, and Iâ€™m trul
manaten 2015/12/11
javascript
ãƒªãƒ³ã‚¯
1 2 3 4 5 6 7 8 9 10 æ¬¡ã®ãƒšãƒ¼ã‚¸