![]() When I started my JavaScript quest, I actually built my own library from scratch because there were few libraries out there and they were sparse in features as it was. It took me some time after that to slowly get up to speed on modern JavaScript principles I had never even thought about up until then effective use of closures, the Prototype model, class definitions, using functions as code, all of which require some getting used to when you are primarily dealing with static languages like C# and ASP.NET as I do for most of my work.īut even knowing JavaScript reasonably well is still not enough-these days it’d be silly to work with raw JavaScript for DOM programming and not use some sort of library to help bridge the browser-specific quirks and provide utility functionality to make it easier to work in a browser-agnostic environment. Looking back, it was not until the AJAX wave started forming a few years back that I even considered getting more seriously interested in JavaScript. ![]() Today I still hate the same JavaScript problems as they haven’t gone away, but thanks to a recently gained better understanding of JavaScript and a small JavaScript client library called jQuery, I no longer dread the days when I have to write client-centric AJAX or UI script code. ![]() Even when ASP.NET AJAX came along, it didn’t really facilitate my work doing client-side coding. After all, that’s what ASP.NET makes really easy. I got into ASP.NET and stuck to server code. I hated writing JavaScript code, and even more I hated the pain that goes along with dealing with different browsers using reams of script code. ![]()
0 Comments
Leave a Reply. |