JavaScript is the new black – Why JS is hot and CSS is not
Wow, how time flies. It was just a year ago when table-less web designers were rare and in extreme demand; anyone who had advanced knowledge of CSS could get any job at almost any reasonable price. Those times are officially behind us. The hot new trade, even though its technology is old, is JavaScript. XHTML/CSS and the entire web standards revolution seems to becoming more and more common place, almost second nature, while JavaScript is standing out as the new defining line between old-school and new.
Let me be clear about two things first. One is that CSS, XHTML and web standards are still vitally important! However, these once sought-after skills are now just becoming more common place; not as rare or exceptional as they once were a few years ago. The second being the term “JavaScript”; at the end of the day, that is what I am summing this new hot trade to be. Sure many of you will argue over semantics; demanding I correct myself with words like DOM scripting, AJAX or a variety of other specialties whose true base is built on or around the use of traditional JavaScript. I know, I know; knowing JavaScript is not knowing Ajax or even having an understanding of the DOM – it is however in my opinion the foundation.
So while HTML complimented with some good design sense was once the qualifying requirements for a web designer; that is now not even enough to typically get an interview. For those us who thought we might be ahead of the curve and on-top of the latest trends with CSS, XHTML and web standards, be aware! Those forward-thinking advanced skill-sets are soon to date themselves when not complimented with the future of the web. If “Web 2.0” has brought us anything as a community, it is the true understanding of how to push the limits of the browser and fully utilize technologies together, such as CSS, JavaScript, XHTML, XML, XSL and XSLT; to name a few.
For those AJAX superstars and masters of the DOM this article is meaningless to you. For those whose entire universe of JavaScript can be found in “light box” or the jQuery library then look for a repeat in history. You more than likely, using nothing more than Google and your local book store, had to learn everything there was to know about how to build table-less sites; overnight, relearning and contradicting the many practices you had thought to be “the way” in web design just months ago. You are now tasked with that same project once again. Open up Google and make your way down to the book store and relearn and explore everything there is to know about JavaScript. You need to again catch up on the past five years of advancements and learnings in a matter of months. Much like when you first learned about separating presentation from mark-up; you will learn there are many subcultures, best-practices, browser compliancy issues, and dozens of ways of accomplishing the same objective. It will be frustrating and annoying, yet highly insightful!
The worst thing you could do in an industry is to not realize when it is changing! The skill-sets required to be a “web designer” are constantly evolving; even to the point where they completely change corporate infrastructure. I am not one to advocate learning all of the hot little technologies that pop-up (I am glad I didn’t waste my time learning Python). However, the time has come and gone; and JavaScript is done defining and defending itself in this industry – it is now a requirement.
- October 9th, 2006
- 13comments
- I am a proud member of the 9rules network
I disagree. Javascript (AJAX, in particular) is the new Flash. It’s cutting-edge, sounds cool, and is completely gratuitous on most websites. Not having to reload the page to submit a form isn’t really a revolution is web technology. Once the novelty wears off, we’ll look back and realise adding AJAX to every website is about as cool as intro pages were.
Web Standards signified a philisophical change in the way websites are designed. Javascript is, and always will be, just icing on the cake.
Tim,
I hear you point but I feel you might be overlooking the true power of JavaScript. It is a little more than “icing on the cake”. It is the method in which we are trying to accomplish the goal of the new internet – brining our websites and online applications closer to behaving like desktop applications (even going so far as to replacing them).
Even if you are right, isn’t it the buzzwords that bring in the cash? A couple years ago you could have dozens of recruiters begging for your resume if you had some CSS on there. These days though, it is JavaScript that they want to see – CSS is expected not respected. Isn’t that what it all comes down too?
I guess it really depends on what your trying to accomplish. When it comes to “Web Apps”, javascript is absolutely a relevant and powerful tool. However, a vast majority of web sites could be classified as “non-interactive” or “information-based”, scripting can be gratuitous and may even hinder your audience from getting what they need from your website.
I’m not saying that Javascript isn’t important to know as a web developer — just the contrary, actually. But I’d be wary to but it on the same level as CSS/XHTML. A lot of respected people in the web community have a cautious and cynical perspective on AJAX.
I just recently finished job hunting in NYC, and the amount of “old school” web developers out there is surprising. When your blogroll is filled with standardistas like A List Apart and 456 Berea Street, it can feel like “everyone” is on the accessiblity train, but there’s still plenty of major sites being redesigned with tables and tag soup.
why compare JS with CSS? CSS is a representation language, js thereby has nothing to do with …
to format efficiently, do you not need CSS? to peform intelligent functions (ignore css menus for now please), do you not need some type of client scripting language?
How are these two related? heh.
This isn’t about the relationship between JS and CSS (speaking with respect to the technology). This is about skill sets and what the industry (specifically hiring managers) is demanding right now. Traditionally, those who work with CSS are the same that work with JS (there being your relationship) – a web designer role of sorts.
My primary point being … if you were a CSS designer with little to no experience or exposure to JavaScript, now is the time! JavaScript chops are in high demand and employers are paying top dollar for (almost expecting it). While CSS is being more common place, those who once had highly marketable skills are going to soon find themselves “common” web designers.
“Once the novelty wears off, we’ll look back and realise adding AJAX to every website is about as cool as intro pages were.“
This is certainly true. I’m not sure exactly how one could simply add AJAX to every website, but I think I understand what you’re getting at.
Like Flash, and like any number of other technologies, AJAX is a tool. Like a torque wrench, it’s not the right tool for every job. As with every tool in your toolbox, AJAX is well suited for some tasks, and poorly suited for others. The trick lies in understanding the difference between those situations. As Martin points out, AJAX is best used to further the goal of bringing web applications closer to behaving like desktop applications, and for that purpose there are few other tools which can do as much when properly applied.
I have noticed a relatively high level of resistance to the adoption of AJAX techniques by developers, I think in large part it’s because many of us tend to be uncomfortable with our Javascript skills, and because we have spent years staying as far away from Javascript as possible, treating it like the proverbial “ugly stepchild.” I think that Martin has a good point WRT the need to understand that changes are happening, and to be familiar with the technology. Nothing about it is technically difficult, it’s not beyond the reach of anyone who has a decent understanding of javascript and of the DOM, and is certainly worth investing a few hours into.
errr, they go hand in hand and server different uses entirely. One for layout the other for helping make the document more dynamic and cooler.
Why write divisive posts? It should read “How to make a bada$$ web app using JS and CSS” instead.
“JS is hot and CSS is not“
Someone should let the Digg community know…
With a good website less is more. Good CSS and good HTML lets you make smaller sized pages that download quicker.
Good JavaScript can make an interface quicker, easier and more elegant, as long as it isn’t the only way to use your site. JavaScript can also add pointless fluff that bloats your interface.
“Good JavaScript can make an interface quicker, easier and more elegant, as long as it isn’t the only way to use your site. JavaScript can also add pointless fluff that bloats your interface.”
That about sums it up.
I agree that JS is “hot” but many advocates would say that JS should be an ‘additional feature’ and should degrade gracefully (ie the same task can be accomplished without JS). With regard to CSS becoming more commonplace, that’s true - but there are many websites where this is not apparent and where “layout tables rule”.
I agree with you guys. I am thinking of it lately more as “marketable skills”. I’ve noticed lately in a lot of conversations, that more and more people are less impressed with CSS knowledge and are highly impressed with your JS skills. It feels as though being skilled and proficient with CSS is expected of us, but now it is all about who can do what with JavaScript.