Script Junkie


Earlier this year in February, I blogged about key software development trends. 

The second trend, The Web as a Platform, continues to grow at an astounding rate.  Browser-based applications such as MugTug show the increasing flexibility and power of web technologies.  New and experienced developers alike are anxious to learn everything they can about how to take advantage of the web to deliver experiences to their audience.

But learning HTML, JavaScript, CSS, and other web standards technologies can be daunting.  The languages, libraries, and interfaces can be complex, and successful development and debugging techniques can be difficult to find among the scrapyard of unsuccessful methods.

Enabling you to better navigate standards based web technologies is the goal behind Script Junkie, MSDN’s newest developer hub. 

MSDN’s goal has always been to help the developer get their job done more efficiently, and Script Junkie brings that assistance to web-based coding.  Script Junkie is the start of a new generation of centers on MSDN focused on offering the best of Microsoft and non-Microsoft resources to address real life and practical end-to-end developer scenarios.

Script Junkie offers a concise resource for the latest in web site development techniques by providing solutions-based articles, videos and code samples written by JavaScript community luminaries such as Christian Heilmann, Elijah Manor, Emily Lewis, Juriy Zaytsev, and Rey Bango.  And of course, new articles are posted on a regular basis.  Many articles contain code suitable for using in your own projects, such as Mani Sheriar’s article on Scrolling Content with jQuery and HTML and Robert Nyman’s article on Using Web Storage on the Client-Side.

Come check out Script Junkie, participate on the forum, and learn from the articles and tips.  Are you an expert HTML developer or designer?  If so, consider contributing articles, screencasts, or code samples for Script Junkie to share back with the community of HTML and JavaScript developers.

Namaste!

Comments (9)

  1. Tom says:

    Soma,

    I know this is a long post and not poltically correct however I hope you read it and are able to see the frustration we have with MSFT, .NET and VS. After reading your blog post I think you have forgot about what is going on in the field. This one sentence completely torqued me off …"goal has always been to help the developer get their job done more efficiently" – Are you freaking joking me-since when?!?!?

    The last time MSFT even acted liked they cared about development and released a finished development tool was VS6. How was killing VB and VFP helping developers get their job done most efficently? I fail to see how forcing us to use a far less productive development tool that requires a substainal amount more code to generate the same application efficent?

    Your VS development controls are released into production without even basic features like complete property sheets and ui designers. When a tool or framework is released that is NOT finished how is that helping us get our job done more effiecently ?!?!? What makes this even more frustrating is we don't need 10 ways to do the same task. Just look at how many grids views ui control there are in VS with minor difference. We only need one way that works well! And even with 5 or 6 different ways to view data in a grid we still don't have a native carousel control – unbelieveable!

    Let see the webform designer after all these years still doesn't render the pages properly and how is writing html-helper a million times getting the job done efficently in MVC? On a side note MVC really is a horrible, noncreative framework, I believe your attitude was we need something compareable to the ruby paradigm and rushed some nonsense out the door. Worse yet it has split the MSFT web development community, have you read the debates going on on the boards?

    To continue, the class browser fails to subclass ui controls visually, more over composite UI controls adds an extreme amount of code overhead into the development process, using inheritance in the UI layer is way more productive. Even VFP'S class browser could pull off visual UI control inheritance. Correct me if I am wrong but isn't inheritance even at the UI level part of basic OOP principles?  

    I fail to understand what can't MSFT give us a designer that works "well" that we layout the forms write some code snippets in an event and method editor with an option to execute the snippett code server side or client side then the tool generates all the html and java script plumbing code for us? Let developers focus on delvering solution NOT writing hacks and html-helper to get our webpages to render correctly! Perhaps some "hobbiest" may like the low level stuff but really that is NOT the need in the field….

    What is frustrating is VS and .NET has the potential to be really good. But it is packed with garabage no one really needs while the important pieces of the tool (the details) that we want is missing and/or a bear to use.

    When reading a post like this I question how often you use visual studio anymore. Please Soma with all due respect, do not post stuff that is NOT true, we work with this stuff every day in he field writing real application not "NERD DINER" and seriously developing now using visual studio is like coding in the 1980's. It really is a shame the extent microsoft has set software development back.

  2. DarkAge says:

    I completely agree with Tom. Things are getting extremely bloated with visual studio and it does little to improve productivity. The new projects are taking much longer to complete than projects done in VB6 era. I have seen many small projects taking months to complete because complex nature of the development platform and practices. Even Silverlight framework is larger than .net 1.0 framework.

  3. Jim Kennelly says:

    More scripting to fix the shortcomings?  Are you at MS telliing us that the out of the box "gridview" is the best you can do?  How about the Ajax Control Toolkit – why not some warnings that this was just a weekend project for MS.  How about some MS jquery controls that integrate easily from a designer point of view.  If things keep going like this,  my next operating system will be Fiddler based since it's the only wat to figure out whats going on.   Things are definitely more complicated now but you have very smart people.  Do you ever invite developers to build real projects in front of your eyes to see the frustration with 2% of the project taking 80% of the time.  Simple behaviours requested by a customer are sometimes a nightmare.  Lot's of developers that do real work don't need more derived junk in the framework but functional, hyperproductive design tools.

  4. Sam says:

    The way things are going, we may be forced write everything in Java-script and XML. What has happened to all the concept of RAD? Is this a way to give jobs to many developers as possible? Is that it? I do not any reason other than that. Development time rapidly reaching Java development time.  I have seen many Java developers envying .Net developers because of development productivity of Visual Studio.  Now it seems like MS is following the Java community.

    This is year 2010. We need powerful and intelligent controls/components for business software development. There is no point in wasting time tweaking JavaScript, css etc. Why are the SharePoint developers using command line tools for configuration? Hello? This is year 2010. In addition, we lost some of the designer productivity in WPF/Silverlight.

    .Net languages are great. We need tools to take advantage of this power. (On a side note, the bad thing about .net is the concept of JIT compiling. The whole thing is too bloated. Ngen doesn't seems to help any of these performance issues and it doubles the disk usage. I would like .net to produce native executable.)

    I think time has come for MS to bring back Bill Gates. He has the potential like Steve Job to bring back MS to its former glory. Otherwise, we may start seeing developers leaving MS platform.

    For anyone who thinks I am a lazy programmer, I do develop hardcore components and programming in Assembly language is my hobby. However, for my professional development I prefer KISS methodology.

  5. Erx says:

    I totally agree with what Tom n others are saying. .net 1.x shipped and the grid control was not even able to do sorting on the columns, we had to writte the code for that – this explains the rest very well, incomplete and subpar… I actually expected .net 1.x to have db schema based hard coded db access (ie: linq to SQL), I looked for it and was shocked when I realized it didn't even exist, had to wait 7 years for it to finally come around. Horrible. I have many examples like this in mvc right now not being able to do things much simpler and more basic ie: returning multiple views or properly doing form validation on multiple items without serious hackery, but I wont even get into those.

    I really cant believe that we still cant do everything in one language, ie: 1 .net language which does the js, css and SQL server side routines, server side development all for us. Even I can write a c# or vb based JavaScript converter using reflection, but you guys have not. This would be making things easier, it is a shame that you guys are not pressing forward with what is expected of a 2010 dev tool, but rather spenind ur time correcting ur frameworks mistakes instead… Ie: bringing in mvc to fix the problem of web forms, mvc should have been in since the beginning instead of web forms. Bringing in razor to fix the other horrid parser, razor should have been here since the beginning. The list goes on, we are in 2010 and it real,y feels like a 1998 dev tool and framework – we are praising you for silly things, like how people praised Steve jobs for finally bribing in copy and paste to the iPhone 3 years later!

    Seriously, your roadmap needs fixing. Please fix this as ur people and ur framework have remarkable potential!

  6. Sam says:

    Soma,

    To the people who posted comments here: This is not just a Microsoft problem! The software industry (including standards bodies and open source community) as a whole needs to come to a decision regarding CSS3/Javascript/jQuery/HTML 5 and plugins like Silverlight and Flash. I believe .NET has the highest potential vs. Java and other platforms that Apple and Google provide. I also believe VS.NET 2010 is the best out there at this moment without doubt. Anyone who says VB6 was more productive and powerful than the current .NET versions has probably never done any serious programming in the .NET platform or understood it properly. I guess that's what happens when you don't update yourselves with what's going on for last 10 years! There are a total of less than a dozen people here complaining. Rest of the community seems happy. However, I do agree that Microsoft needs to lead the effort in standarizing web development and make it easier to develop web apps.

    Microsoft can start by doing the following:

    1. Update all ASP.NET controls with built-in AJAX/jQuery capabilities (or at least provide these versions of the controls as well)

    2. Do NOT step back from your initiative and goals of Silverlight. It is an AMAZING technology that has great potential and will ALWAYS remain ahead of improvements that come in standards based approaches like CSS or even HTML. Keep supplementing web development through Silverlight (and keep improving its performance).

    NOTE: However, I must add that the current WCF-RIA services is not flexible enough to support stored procedures and is too deeply tied up with Entity Framework. It is difficult to write a real business application using WCF RIA services if we don't want to use Entity Framework.

    3. STOP introducing hundreds of ways of doing the same thing. We're tired of it. Currently there are so many different techniques and ways of accessing Data. We JUST NEED ONE that works – and no, sorry, I'm afraid Entity Framework is not that one. It's getting overly complicated. Samething with ASP.NET! First there was web forms and now there is MVC, in Silverlight now we have MVVM and tomorrow there will be few dozen more ways of programming – even VS.NET is not able to keep pace with these things to fully support developers! If there are drastic changes in the philosophy of programming (WCF RIA Services vs. WCF based services, using MVVM, etc.) Microsoft needs to provide FREE TRAINING to help developers and fully support these in VS.NET!

    4. MORE Training videos!

  7. Sam says:

    This is crazy! Why are they celebrating before the launch and actual success of the Windows Phone 7?!

    http://www.engadget.com/…/microsoft-celebrates-windows-phone-7-rtm-with-funeral-parade-for

  8. Marcelo says:

    To be bloated or not. That's the question.

  9. Erx says:

    Sam, i agree with everything you said except for one item, where i partially agree. yes .net is more productive than vb6 but that should go without saying, re if anyone else thinks otherwise that they haven't been upto date in the last 10 years or done serious dev is my point of contention. i think its possible for some people to experience inverted productivity scales depending on the project they are working on and their particular experience with the dev tool. although i am not one of those people, i can see there can be.

    re your point (1). this is a great point and should also be true for MVC, helpers should be available for the top 95% of controls we spend our time with.

    yes VS.Net is the best dev studio and i realized this when i went to delphi 2010 to give it a try, my god, we have it well. but resting on these assurances will only do deeply grained and difficult to measure damage to vs & the developers world wide. we need to move forward by pushing ourselves against the last version of ourselves and not against the best piece of the second in line competitor :). we need to be able to do everything in one language, and i dont think there is any work on the vs team towards this.

    also, i dont think it's a matter of standardization, we can't nor should we wait for js/css/html etc to be standardized better, i'm sure it would be less work for us but even if we were to make the mentioned paradigm-shift (webdev in one language) work on 95% of computers it would be much better than not having it at all, and waiting for standartization will mean you'd be waiting forever. there is no point.

    we need to move forward with this without delay. i bet if someone did bring bill gates back, he'd insist on this and actually make it happen. because to make a proper website/webservice/webapp including all css, javascript, jquery (things you must use to remain competitive) etc …. is still all just one big hack, and we all know we can't code according to proper coding standards when needing to integrate so many different areas of tech into one application, even if it is technically possible, it's just not going to happen…

    we need a paradigm-shift, and the attempted paradigm-shifts are not all encompassing enough. humans went to the moon, not because it was easy, but because it was hard.