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 :


Chris Ongsuco 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

Popular posts from this blog

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 :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

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

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 internet for a better solution. I stumbled upon Stateless