Nobody supports IE6 anymore.
Now thats not true and even you must know that
Nobody supports IE6 anymore.
What I meant was that most developers will have a working knowledge of javascript in as much as they can craft their own solutions using JQuery rather than copy and pasting.
That's why I wouldn't employ them, if they don't have a understanding of the language they won't have taken into account performance across different platforms and all the other little quirks that JS has which jQuery alone does not solve.
Sure if all we are discussing is selecting a dom element and hiding it once or twice thats fine, but creating any form of scalable platform needs to know something about the language behind it.
Really it all depends on the product and target audience as to what skill set is needed.
One thing I do want to get across is that HTML5 is not a new language it's just HTML with some new semantic elements created based on what we have used consistently over the years.
Yes, there are some new elements adding (video, audio etc) but these alone are not HTML5 you could change the doctype on any HTML page and call it HTML5 doesn't mean you understand it![]()
but if you are using it for a web app it starts to look a bit heavy.
Web 2.0 and ajax come to mind. They sound fancy to the uninitiated but there is nothing special about them.
Err, nothing special about async javascript? It only changed the modern internet and all.
True, but the 'ajax era' has totally changed the roadmaps of frameworks like ASP.NET and C#, the last two versions have really made a push toward async development and that's all come around because of the surge in ajax-ified (don't you just hate that term) websites. They were all possibly pre 2005, but it's in no way a fad, it's completely changed the last five years and the next ten years of software development.
Look at all the web based systems that are replacing common desktop software, Google Docs, MS Office 365/workspace and there'll only be more. They all rely on ajax related technologies.
Ajax isn't tricky so when you see a job asking for jQuery, ajax and web 2.0 I tend to write the company off as a bit of a wannabe.
As to jquery being heavyweight, I still stand by that. Look at the huge range of functionality it exposes and you will find everything that it implements can be found in different little libraries and plugins that allow you to keep the size of your javascript down.
Using tools like Ender allow you to minify and combine your libraries into a single file to keep requests at a minimum on both the number and size fronts.
I know that the google CDN helps out a lot but I still feel a little lazy when I use it these days.
"the fad" was the phrase "web 2.0" - using asynchronous javascript isn't/wasn't.True, but the 'ajax era' has totally changed the roadmaps of frameworks like ASP.NET and C#, the last two versions have really made a push toward async development and that's all come around because of the surge in ajax-ified (don't you just hate that term) websites. They were all possibly pre 2005, but it's in no way a fad, it's completely changed the last five years and the next ten years of software development.
Look at all the web based systems that are replacing common desktop software, Google Docs, MS Office 365/workspace and there'll only be more. They all rely on ajax related technologies.
"the fad" was the phrase "web 2.0" - using asynchronous javascript isn't/wasn't.
For a number of years in the earlier 2000's you couldn't read a single blog/article/job advert that was related to the web without "Web 2.0" being in it somewhere. It was utterly annoying.