My latest OdeToCode article is online: “What ASP.NET
Developers Should Know About JavaScript”. The article covers what I personally had to learn before feeling comfortable with modern JavaScript toolkits,
frameworks, and libraries. It all boiled down to the following:
- Every JavaScript object is a dictionary.
- Every JavaScript function is an object.
- Every JavaScript object references a prototype object.
Here is the introduction:
JavaScript – It's beat up, put down, shrugged
off and kicked around. Cursed by the web browser's inconsistency yet blessed by
a pervasive ubiquity -it's a technology many try to disregard even when its
potential is something few can ignore. If you want to write an interactive
application for the web today, then you'll need some JavaScript code
on your side.
This article approaches JavaScript from the
perspective of an ASP.NET developer who is comfortable with the paradigms and
patterns of either C# or Visual Basic. The article doesn't look at how to use
JavaScript from ASP.NET exactly, but it does look at why JavaScript is so
different from the two languages we commonly use with the .NET CLR. The article
assumes you already know that JavaScript is a loosely-typed language (because
you don't have to declare the type of data you store in a variable), and that
the syntax is similar to the C family of languages (with charming curly braces
and stunningly beautiful semi-colons).