No, Rebecca is right - the game changed for front-end developers when client-side scripting became ubiquitous, which is a somewhat recent development:

For example, while XMLHttpRequest was introduced in 1999 (IE 5), it took years to gain traction (XHR support was added to Opera with version 8 in 2005), and incidentally, JavaScript frameworks (Prototype 2005, jQuery 2006) and distributed version control (Mercurial, Git 2005) entered the spotlight at the same time.

While serious JS-based applications were definitely around before the advent of Web 2.0 (you can go a long way with hidden iframes, long polling, chunked transfer, forms, 204 status code), these were the exception, front-end work was mostly about layout and code-reuse virtually nonexistent.

I hope I gave due credit to the possibility that part of what's changed is me when I said in the next sentence: "Maybe it’s the result of people starting to take front-end dev seriously, maybe it’s browser vendors mostly getting their shit together, or maybe it’s front-end devs – again, myself included – coming to see some well-established light about the process of software development."

I do think the profession of "front-end development" has grown up a whole lot in the last couple of years. There have been front-end pros since long before I was even in the business, but I think the profession as a whole is being taken more seriously, and a set of baseline expectations for people in the profession is solidifying.

Well it's a good list, I guess it would be most useful to student looking for a career in front-end, you got the next couple of years of skill required right there.

Then I agree with you, web publishing did not change that much, 3 years ago it was a bunch of js plugins together + nice html templates and well, it is still that currently. And I know loads of front-end that only know basic js with a svn client and get by.

Then you got js web apps. There you got a world of difference. It is limitless and evolving like crazy