Scoble’s foray into video blogging is felt all across the web – and there is a reason for it. Scoble is known for his content. He has done it with his blog before his Microsoft days, he did at Microsoft with Channel 9 and now at PodTech. When I talked about it in my post regarding “what’s next for Scoble” this is exactly what I had in my mind – a TV Show – I even remember asking him about it. There is no doubt that Scoble will be successful in this venture – and it’s great to see that he already talks about the things to improve about his show¬†– but there are a couple of things that are missing from the list and here they are:

1. Site is too slow: I’m pretty sure that the PodTech team is already working on it but they need to scale for the upcoming flood of traffic ūüôā – this is a good problem to have but they need to be quick to solve this.

2. Site’s design: Not sure how PodTech designers plan to scale the design for Scoble’s wide verity of up-coming content but they need to work on basic usability aspects to categorize content (beyond tags) and search (including video search!).

3. Ability to link and host video’s from other’s blogs: If I’m going to link to Scoble’s language war’s video talk, I want to be able to post a snippet or even entire video link from my blog (similar to: YouTube or Google Video). Sure I can’ link using the permalink but it does not work well for rich media content like ScobleShow!

4. Content: Finally, this is about the content itself. I said before Scoble is known for his content in the past and his speciality lies in covering the content that other’s haven’t covered before – and I hope he continues that with his ScobleShow. But when I see the list of people that he wants us to pick from all I see folks that are being covered by tons of other channels, magazines and media – so Scoble should probably continue on his original style¬†of talking to the un-sung heroes behind many successes (like he did at Channel 9 @ Microsoft) and introducing them to the world. That’s¬†how I at least see ScobleShow is different from other 100’s of tech video blogs and channels around.

Having said all that, Scoble is an early indicator of where the the blogging and the media is heading to Рway to go Robert, congratulations!

Enterprise JavaScript Programming

One of the primary tasks of my development¬†team¬†at Microsoft is to develop client-side (web browser) UI frameworks and client-side APIs for Virtual Earth. As a heavy client-centric web application,¬†our product, Windows Live Local, requires a lot of JavaScript based development coupled with server-side development (using popular AJAX and JSON protocols). What I have personally learned over time is that we have to be smart about what functionality we can build on the client-side vs. what functionality we can move to server side; this is a crucial step in the design process since most of the server side development is fairly simple (or straight forward)¬†compared to JavaScript development. You might think I’m crazy when I say this but believe me it’s hard to do development in JavaScript – no, I’m not talking about simple client side scripts that you use to make dynamic HTML web sites – but I’m talking about Enterprise JavaScript Programming or simply EJP.

EJP is slightly different from what usually scripting developers do with JavaScript РEJP is different in a way that you need to build stacks of re-usable layers of JavaScript libraries that also allow you to plug in general development blocks such as threading, state-serializers, networking, perf counters, tracers etc Рnow the only problem is that the language is not mature enough to support these things natively. On contrary any .NET language (or Java) that can be used for server side development support these primitive concepts natively. That is why I say that it is hard to develop in JavaScript.

Now,¬† I do know that there are some good debuggers out there that can make your life easier when you are working on 100s of thousands of scripting code but it’s not clearly enough. Microsoft’s Atlas framework is aimed to solve some of these problems by giving some structure and framework to JavaScript programming and it is a good start in EJP arena; but¬†it is¬†going to be a while to get production ready Atlas Framework, so¬†we are on our own for building these core building blocks to build rich web applications and platforms like Virtual Earth.

So the bottom-line is this:¬†“developing in JavaScript may be easy but developing Enterprise Ready Applications in JavaScript is extremely hard”. Do you agree?

Now, EJP is what precisely makes my job challenging and fun at Virtual Earth – so if you are ready to do some EJP, send me your resume. ūüôā¬†