category : JavaScript

Securing JavaScript

The ProblemCross-site Scripting is a problem in the world of the internet. Someone hijacks your web site by injecting a little bit of JavaScript code and suddenly he/she has access to pretty much anything they want on your site. Douglas Crockford gave a talk at the end of March last year (at least, that’s when his video was published on YUI Theater) that partially discussed this problem, and this article is largely based off that talk. He noted the web’s vulnerabilities to these types of attacks, mostly due to standards that must be implemented by the browsers and having very little to do with bugs. He also felt, though, that JavaScript is one the best languages for creating secure code.

Infusionsoft Failure

Has anyone here ever used InfusionSoft? It’s an amazingly powerful piece of online software that brings together a lot of features dealing with email marketing, sales, tracking, statistics, and shopping carts. There’s tons to talk about and it’d take a couple year’s worth of blog posts to go through every feature and that would only happen after the year it takes me to learn InfusionSoft. This blog post is exclusively about the shopping cart feature and the headaches that come with it.

Let's Start This Off ($script.js)

This is my first blog post ever, which goes without saying that this is my first blog post on this blog. I figure I’ll start off strong with a new development in JavaScript. If you’ve gotten into JavaScript development and also tried enhancing performance on sites that use Javascript, you probably already know that when the browser downloads a JavaScript file, it is executed immediately. While JavaScript is being executed, the browser will stop downloading resources such as images and style sheets. This can be really painful on sites that use a large amount of JavaScript because it can seem to bring the browser to a halt.