programming languages
In the calculus of communication, writing coherent paragraphs that your fellow human beings can comprehend and understand is far more difficult than tapping out a few lines of software code that the interpreter or compiler won't barf on. That's why, when it comes to code, all
javascript
One of the early technology decisions we made on Stack Overflow was to go with a fairly JavaScript intensive site. Like many programmers, I've been historically ambivalent about JavaScript: * The Power of "View Source" * The Day Performance Didn't Matter Any More * JavaScript and HTML:
asp.net mvc
As we work with ASP.NET MVC on Stack Overflow, I find myself violently thrust back into the bad old days of tag soup that I remember from my tenure as a classic ASP developer in the late 90's. If you're not careful bordering on manically
php
Robert Miesen sent in this story of a project pathology: I was part of a team writing an web-based job application and screening system (a job kiosk the customer called it) and my team and our customer signed on to implementing this job kiosk using Windows, Apache, PHP5, and the
javascript
In The Day Performance Didn't Matter Any More, I found that the performance of JavaScript improved a hundredfold between 1996 and 2006. If Web 2.0 is built on a backbone of JavaScript, it's largely possible only because of those crucial Moore's Law performance
browser
Two weeks ago, Apple announced a new version of WebKit, the underlying rendering technology of their Safari web browser. The feature list is impressive: * Enhanced Rich Text Editing * Faster JavaScript and DOM (~ 2x) * Faster Page Loading * SVG support * XPath support * Improved JavaScript XML technology (XSLT, DOMParser, XMLSerializer, and enhanced XMLHttpRequest
javascript
Mike Shaver, a founding member of the Mozilla team, has strong feelings about how the web became popular: If you choose a platform that needs tools, if you give up the viral soft collaboration of View Source and copy-and-paste mashups and being able to jam jQuery in the hole that
javascript
I've been troubleshooting a bit of JavaScript lately, so I've enabled script debugging [http://blogs.msdn.com/ie/archive/2004/10/26/247912.aspx] in IE7. Whenever the browser encounters a JavaScript error on a web page, instead of the default, unobtrusive little status bar notification.
firefox
Although I prefer IE7's native speed and feel for day-to-day browsing chores, there's no doubt that Firefox is my primary web development IDE. Whenever I need to troubleshoot HTML, CSS, or JavaScript, I immediately reach for Firefox. That's primarily because of two incredibly powerful
timekeeping
I have something of a clock fetish. My latest acquisition is a nixie tube clock from my wife, as a Christmas gift. My computers aren't just giant calculators, they're also clocks. Unfortunately, my nixie clock is a much more reliable timekeeper than any of my PCs
javascript
The 1996 JavaWorld article Is JavaScript here to stay? is almost amusing in retrospect. John Lam recently observed that JavaScript is the world's most ubiquitous computing runtime. I think the answer is an emphatic yes. JavaScript is currently undergoing a renaissance through AJAX. Sure, the AJAX-ified clones of
web development
Or, What Would World Wide Web Developers Do? To get an idea of what web developers are using -- as compared to typical web users -- take a look at the comprehensive w3schools browser statistics, picking up from mid-2004 when the Google statistics end: Quite a difference from the other