Future of the web.

The answer is right in front of you even if you don't see it already:

The web started with simple HTML.
Then came the dynamic web where content is dynamically generated for the users.
Then came the wikis which enabled editable webs.
Then web applications got more interactive with AJAX.
The next level of interactivity is where applications execute and behave like Desktop applications within the browser.
Then there will be the web OS where you store all the important data in the web and access the same from everywhere.

* The web OS sounds grand but the closest we have today for the client is Flash/Flex & Silverlight & XUL to a lesser extent.
* This will blur the line between desktop apps & web apps further.
* Making toy applications for web will no longer fly & traditional players might get another shot. (MSFT vs GOOGL)
* The recent acquisition of 'Parakey' by Facebook is an indication of where the future is going.
* HTML or AJAX(to a lesser extent) will still be around as there are applications for which they are suited more.
* AJAX was a mistake, making a Java VM to virtualize the development or coding for 'n' browsers is not the future.
* Flash/Flex is the underdog here where people often associate Flash with those 'flashy' sites. It is no longer the case.
* With cross-platform support in Flex & Apollo along with synchronization & native db support it is an example of how the web platform of the future is going to be!
* And then, sometime in the future we will have a web OS which has some features from Omnidrive & Parakey.

Comments

Post a Comment

Popular posts from this blog

.NET Decompiler aka Disassembler aka Reflector This is the best .NET decompiler around and it is free. http://www.aisto.com/roeder/dotnet/ This will decompile .NET bytecode(including the base class library) into more than one language(C#, VB, J# etc).
Read more

Google Appengine

It was good while it lasted, Google AppEngine gave developers an easy way to create web applications without worrying about scaling it or being a sysadmin. There were numerous startups that built their products on Google Appengine. Even after beta, there was a fairly large free quota that made it a reasonable choice. But, the current pricing seems a bit ridiculous for those who are looking for a free or cheap solution or for those enjoyed the initial quotas. Perhaps, we were spoiled and Google’s goal is to get rid of free-riders which is not exactly evil from Google’s perspective. So, it is 2012 and welcome to reality since Google can’t maintain those quotas forever and the current free quotas are intended to only test your application before you go live. If for some strange reason, your application becomes popular and gets more than 1,000 users, you would end up scrambling for an alternate solution since you will find yourself paying through the nose. The quota system is complica
Read more

Did you ever have to analyze large log files before?

Well, I recently had to analyze a large log based dataset and decided to try out the ELK stack . Introduction: Please see this intro if you are not familiar with ELK, the rest of the blog assumes you know what they are. eg. elastic server, logstash & kibana. It is a popular server side tool to index, search & graph a large collection of logs or similar structured/unstructured data. This blog post mainly talks about my experience setting up this well known stack & the unexpected things learnt during the process. Goal : "How do I enable rich filtering & analysis on the large set of product logs beyond some simple scripting?" I thought I just had to upload a few log files to the server & then have some awesome graphs appear almost magically out of the box! Servers : "How do I get a server up and running?" There is a free trial for cloud based elastic stack. I signed up and got a 14 day free trial with 4 instance running on Google Clo
Read more