While Stoyan is with us to answer our queries, I would like to ask this question. Not directly related to his book but a general question
2) Debugging is very difficult. Now a days firebug is there but most of the people today don�t know how to use it. In my case our users are just IE6 users, so we don�t even bother about cross browser compatibility. And for debugging we use pop-up alerts.
I think books like yours� will help people learning this tool.
A lot of page authors are not technical and come from a design or artistic background. Coding of any kind is new to them and so they rely upon cut-and-paste without really understanding the code, or allow tools such as DreamWeaver to generate it for them.
And then there are the php authors with similar challenges.
The vagaries of the DOM, cross-browser issues, and the debugging debacle (getting better and better every day) also add to the fear.
We are using JQuery in our current proj. But in all the projects I worked so far we use to have a handful of .js files which we include on the top of our JSPs and use the existing functions for validation, formatting and stuff.
Are we going to code anything more complicated than this? Like creating domain or business objects and doing stuff with them. While I understand the that you can't foretell future but at least guess the upcoming trends
[ August 28, 2008: Message edited by: Paras Jain ] [ August 28, 2008: Message edited by: Paras Jain ]
And what about when things go wrong? How do you debug code you don't understand?
When the cut-and-pasters and DreamWeaver enthusiasts hit such debacles, all they can do is throw up their hands in horror and try to seek someone else to solve their problems. That's not "development" to me.
The same goes for the server side. Some users of tools like JSF (shudder), Struts, Spring and the like think that they can get away without having to understand basic Java and Servlet and JSP concepts. Not so.
Understanding the underlying technology is essential to effectively using the tools that are built upon them.
Otherwise, you're just a mechanic, not a developer/engineer. [ August 28, 2008: Message edited by: Bear Bibeault ]
Originally posted by Bear Bibeault: A lot of page authors are not technical and come from a design or artistic background. Coding of any kind is new to them and so they rely upon cut-and-paste without really understanding the code, or allow tools such as DreamWeaver to generate it for them.
@Paras, while it's true that there is a limit of how much logic you can have public (JS is plain text on the client), it's not true that there aren't big JS applications. Just the opposite, there are many examples of client-heavy, or fat client applications and this is a trend. I think I even saw some stats about the shear size (in KB) of the JS code in popular sites, and it's going up.