IBM DeveloperIBM Developer is your one-stop location for getting hands-on training and learning in-demand skills on relevant technologies such as generative AI, data science, AI, and open source.
Javascript integration (3)
This document discusses JavaScript testing with tools like Capybara. It mentions that Capybara allows testing web applications by simulating user behavior like clicking and filling forms. It provides details on different backends for Capybara, including those based on Selenium, envjs, and PhantomJS. It also discusses using Capybara with JavaScript code coverage tools like JSCoverage.
CommonJSの話
Közösségi média konfliktuskezelés - A közösségi média botránykönyve bemutató
Know your Javascript Engine
The document discusses how JavaScript engines have improved performance over time. It explains that early JavaScript engines in 2006 used interpreters which were slow due to overhead from boxing and unboxing values. Modern engines in 2011 use just-in-time (JIT) compilers to generate fast machine code, and techniques like inline caching (IC) and type specialization to optimize property access and e
Javascript Unit Test Environment (JUTE) Now Open! · YDN Blog
Ready to kick your Javascript Unit Testing up to the next level? Or even to the very first level? Javascript Unit Testing suffers from lack of standardization. There is no universal 'JUnit' or 'PHPUnit' to 'rule them all'. There are lots of very good Javascript testing frameworks available, especially YUI3's test framework. But there's not a lot beyond that, so now JUTE is throwing its hat in
Introduction to the Page Visibility API - Human Who Codes
Posted at August 9, 2011 by Nicholas C. Zakas Tags: JavaScript, Page Visibility API, Performance A major pain point for web developers is knowing when users are actually interacting with the page. If a page is minimized or hidden behind another tab, it may not make sense to continue functionality such as polling the server for updates or performing an animation. The Page Visibility API aims to giv
Finding memory leaks
Over lunch last week Mikhail Naganov (creator of the DevTools Heap Profiler) and I were discussing how invaluable it has been to have the same insight into JavaScript memory usage that we have into applications written in languages like C++ or Java. But the heap profiler doesn't seem to get as much attention from developers as I think it deserves. There could be two explanations: either leaking me
High-Performance Javascript
book by Nicholas C. Zakas presentation by Goran Topic Loading and Execution or how not to block your page The first job: getting your scripts to run Standard way: list them in <head/> That way, we know they are available "Standard" way <html> <head> <title>Test</title> <script type="text/javascript" src="file1.js"></script> <script type="text/javascript" src="file2.js"></script> <script type="text
Jison入門!!! - プログラムモグモグ
最近, Jisonを使おうとしている人をちらほら見るので, ちょっと入門的なやつを書いてみる. 定義(てけとー Jisonというのは, JavaScriptで書かれたパーサーを吐くことができる, パーサジェネレーターの一つ 現在Jisonは https://github.com/zaach/jison で入手可能です. 色々説明したいけど, 構文解析とかLALRとか説明しだしたら, ボロが出る難しいので, ... 取り敢えずJisonのexampleを試してみよう!!! まずは, narwhalをインストールしましょう https://github.com/280north/narwhal から落として, PATHを通す. narwhalと叩いてJavaScriptのインタラクティブな環境が立ち上がったら多分OK. (というかnarwhalの詳しいことは僕はよく分からない...) Jiso
Combining jQuery Deferred with the HTML5 Web Workers API
A way in which we can make the Web Workers API behave a lot more nicely. Why? Long running calculations in JavaScript are generally a bad idea. This is because JavaScript is a single-threaded environment; anything we do takes place on the UI thread, and when a script is running, the UI is unresponsive. To prevent this happening all the time, browsers have implemented various warning messages that
High Performance JavaScript 2011
The document discusses the importance of JavaScript performance in enhancing user experience, highlighting the interaction between JavaScript execution and the UI thread's responsiveness. It outlines various techniques to optimize JavaScript performance, including script loading methods, execution timing, and minimizing long-running scripts. The document also covers common performance pitfalls suc
Node.jsのためのasync必修パターン(1): 同期パターン
node.jsはnon-blocking処理を行うため、書き手の意図しない順序で処理が実行されることがあります。それでは困ることもあるため同期をとって処理を行うパターンについて書きます。例えばA、B、C、Dという処理があり、A、B、Cの3つが終わってからDが行われることを保証したい場合の必須のパターンです。 A、B、Cという3つの処理では、それぞれDBに問い合わせを行い、Dという処理では3つのDB問い合わせの結果を使って集計の処理を行いたいような場面を考えてみます。a(); b(); c(); d();上のように普通に書くと、node.jsでは折々の状況に応じてaからdまでの処理を非同期に実行します。dが一番最初に実行されるかもしれません。困ります。そこで、A、B、Cの3つの処理が3つとも完了した後にDが実行されるようにするパターンを書きます。// sync.js var wait = f
http://blog.stchur.com/blogcode/jsquiz/
Disclaimer: Of course there are always many ways to solve a problem, so the answers listed make no claim of authority, or even of "best approach." You are welcome to email sstchur(at)yahoo(dot)com if you'd like to see an alternate answer listed. What is the result of the following? function foo() { alert(x); var x = 10; } foo(); Runtime error Will alert undefined WIll alert 10 Answer B. Why? It is
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
LLPlanets: 「JavaScriptプログラマのための全方位的完全武装ガイド」mala
App Framework - YUI Library
http://www.artzstudio.com/2009/04/jquery-performance-rules/
Google Code Archive - Long-term storage for Google Code Project Hosting.
JOSS777: Situs Slot Online Server Thailand Terbaik Saat Ini
not found
Post by @hamalog
