javascript
Google JS Test in action Source: Google On the Open Source at Google blog, Google has announced the release of JS Test – the JavaScript unit testing framework that it uses in-house – as an open source project. The tests run on Google's V8 JavaScript engine, the same open source JavaScript engine used in Google's Chrome web browser. In developing JS Test, the creators of the framework were inspired by googletest , an open source framework for writing C++ unit tests.
Google open sources JavaScript unit testing framework
BicaVM: JVM in JavaScript – Why? | surf the edge
Last weekend I’ve been in Codebits and Made a presentation about computer languages that you can watch here . Like this post, its was presented in poor english, I know that. The gist of it is: I don’t have the same hard on that everyone else is apparently is having with JavaScript. Sure is cute language.IEBlog : IE JavaScript Performance Recommendations Part 2: JavaScript Code Inefficiencies
Hello again, this is Peter Gurevich, Performance PM for IE. We have gotten a lot of good feedback from our first post on IE + JavaScript Performance Recommendations so I am eager to hear what you think of our second installment. This is the first of two posts concerning inefficiencies in Javascript code itself. JScript Code Inefficiencies – Chapter One
Tuesday, December 5th, 2006 < >p >Douglas Crockford is “Yoda of lambda programming and JavaScript†(according to Brendan Eich), and he shows it in his presentations on all things JavaScript. The Yahoo! UI team video-taped his Advanced JavaScript talk (which he gave at The Ajax Experience): In this presentation — the third of a three-part series he has been teaching at Yahoo! — Douglas looks closely at code patterns from which JavaScript programmers can choose in authoring their applications.
Douglas Crockford Video: Advanced JavaScript
Objectifying JavaScript
The web professional's online magazine of choice. In: Columns > Behind the Curtain By Jonathan Snook Published on September 18, 2006
Friday, September 17th, 2010 Progressive enhancement using nothing but JavaScript? Progressive enhancement is still a confusing matter for a lot of people who are very excited about the capabilities of JavaScript in modern browser environments.
Yahoo!
Secure String Interpolation - http://google-caja.googlecode.com/
Abstract String Interpolation , the "Hello $name_of_planet!" style of generating strings, familiar to Perl, PHP, and Ruby programmers, provides a simple and intuitive way of specifying content in many languages from HTML to SQL to URLS. It also makes it very easy to introduce serious security problems.
ajax
Uphill, Both Ways I got interested in JavaScript when it arrived to the world as Netscape LiveScript. It came in two distinct flavors: client-side JavaScript running in the browser, and not many people remember, Server-Side JavaScript for writing the back-end logic. I believe back then it was called LiveWire. Next to client-side Java, client-side JavaScript didn’t look like much. DHTML was nice, but nothing compared to the promise of mobile agents roaming around the Interwebs doing all sort of fancy tasks on your behalf.
2011 is year of the Server-Side JavaScript
closure
testing
Each application targets some domain problem. And each domain has its own set of rules and regulations that put constraints on data. When an application applies those constraints on data, the constraints become validations. All applications need to validate the data that users enter. Today, applications generally use combinations of if-else statements to validate data. These statements contain validation data that developers either hard-code or put through server-side code.
Cache in with JSON
Nearly every Web developer has cursed JavaScript at one time or another. The beleaguered language sags under the weight of a complex programming model called the document object model (DOM), poor tools for implementation and debugging, and inconsistent browser implementations. Until recently, many developers had all but written off JavaScript as a necessary evil at best or a toy at worst. But JavaScript is becoming increasingly important, and it remains the most broadly available scripting language for Web development.
Crossing borders: JavaScript's language features
The features of different Web browsers, such as language settings and JavaScript support, can cause Web applications to work differently from one browser to another. This lack of continuity among browsers not only causes an application to look bad, but it often causes it to break. This article presents a number of tips you can follow to solve some of these problems. Handle different kinds of browsers The main reason that Web pages cannot work everywhere is that different kinds of browsers support different standards. The best way to overcome this is to use only common attributes and methods.