Skip to main content

google docs : a threat to microsoft office ?

Anyone working in an office may have heard of Microsoft Office . They have been around since MS Windows . I could say that its really a great piece of software and it had helped a lot of people in managing and creating their documents . A lot of other alternative software has been released to compete with this product . Most of these alternatives , though , still follows the same paradigm as the MS office has set and sometimes its only the UI that changes and a little functionality .

Then , Google Docs , an experimental move from Google. What this new technology brings is a new face in Office computing , online office application . No installations , no licensing , just get on the internet fire up your favorite browser get a google account and start writing office (word,excel,presentations) online . Cool isn't it.

It may have offered the advantages but not a lot of people has seen the good in google docs because they are still tied up to the old paradigm. Plus the fact that there are limited features to it . So everyday people uses the same office applications , when they go out they save it on their disks or thumb drives , when back , they update everything in their PCs. The process is tedious right? Thats is where the new google docs feature comes in. Yes , ladies and gentleman , google docs is now allowing you to take the cloud offline . Offline google docs is now supported with some limitations at first . Now we dont need to use thumb drives or floppy diskettes (if it is still alive) , just get on the web and do the office docs online or offline . Automatic synchronization is supported once youre online again .

See this article from the official google doc blog.

Offline Google Doc preview :
Labels:

Comments

Anonymous said…
Yes it is indeed a threat to Microsoft that's why they released a "new web-based feature" of Office called Office Live Workspace
7:00 PM
Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more