Tag Archives: BigTable

Google Dash Set to Try and Simplify Complex Web Evironments

Posted on 14. Sep, 2011 by . 1 Comments

flattr this!

It’s no secret that Google must rely on JavaScript to help power its own series of services in the form of webapps. However, the recent news that they are working on an alternative form of language to help speed up and provide more consistency to applications comes as no surprise. What is surprising is that this concept was being held for some time as a bit of a secret.

JavaScript in its current form today encompasses over 20 different frameworks. As Google discovered long ago in developing its own digital infrastructure, it’s simply to the benefit to the company over the long term to just go ahead and create tools and interfaces that can support enormous amounts of data and ever-complex behind the scenes processing power. The art of how Google does this so beautifully is that they make it look really simple to the end user.


Take BigTable for example. The concept behind this internal technology that helps to power both homogenous Google services as well as Google App Marketplace products is that it’s underlying structure is built to be able to handle hugely vast stores of information. Although some developers have taken to gripe about having to play by Google’s rules when using frameworks such as Big Table, it comes to the overall benefit of everything that speed and simplicity is the ultimate goal for Google’s technology. Again, the user is not supposed to see all of these elements of complexity.

So back to Google Dash, formerly known as Dart. Developers who take the time to work specifically in Chrome’s environs are the ones who will benefit first, as there is expected to be Dash features coming to Google’s browser soon. For those continuing to use JavaScript, there will be a compiler available at some point in the future, although there’s no indication as to when as of yet.

How do you feel about Dash? Could it be a technology that may help to speed up the processing power of Chromebooks by harnessing efficiencies in back-end technology? Or will it not matter what kind of JavaScript replacement there is out there as long as Adobe Flash is still around?

via The Register