Language Selection

English French German Italian Portuguese Spanish

Is Google secretly helping M$ ?

Filed under
Google
Microsoft

I know it sounds bizarre, but I do have a theory to substantiate this. Don't know how to formulate it so just listing it.

1. Google is a closed source company. Ok, to begin with, Google internally uses Linux ( all that hype about Gooobuntu ), contributes to MySQL and supports Mozilla foundation. However, how many of Google own software are open source ?? Zilch!! Zero. Its like Google loves to take advantage of open source technologies, for its own benefit, but refuses to make its own products open source. Even its Linux products, like Linux Desktop Search and Picassa, are closed source. In todays world, Google and M$ are two biggest technology companies for desktop users. As they both promote closed source, are they not helping promote the notion that closed source is not evil -- one of the biggest motivating factor for people using Linux.

2. Most, if not all, of Google's applications are on Windows. Google has just started porting its existing applications to Linux, the first being desktop search. Picassa for Linux is just a "wine" adaptation of windows version of Picassa.

More Here




Also: Google spending hundreds of millions on mobile-WSJ

More in Tux Machines

Games and Emulation

Linux Devices

Koozali SME Server 8.2 Reaches End of Life on March 31, Upgrade to Koozali SME 9

Koozali Foundation, through Terry Fage, announced the availability of a final set of updates for the Koozali SME Server 8.2 operating system, which will reach end of life this week. Patching some of the reported bugs, the new packages released today for Koozali SME Server 8.2 are e-smith-ibays-2.2.0-16.el5.sme.noarch.rpm, e-smith-manager-2.2.0-14.el5.sme.noarch.rpm, smeserver-clamav-2.2.0-15.el5.sme.noarch.rpm, smeserver-locale-*-2.2.0-56.el5.sme.noarch.rpm, and smeserver-yum-2.2.0-26.el5.sme.noarch.rpm. Read more

Development News

  • GCC for New Contributors
    I’m a relative newcomer to GCC, so I thought it was worth documenting some of the hurdles I ran into when I started working on GCC, to try to make it easier for others to start hacking on GCC. Hence this guide.
  • #1: Easy Package Registration
    Last month, Brian Ripley announced on r-devel that registration of routines would now be tested for by R CMD check in r-devel (which by next month will become R 3.4.0). A NOTE will be issued now, this will presumably turn into a WARNING at some point. Writing R Extensions has an updated introduction) of the topic.
  • Emacs as C IDE and JHBuild
    Although Builder clearly is The Future as GNOME IDE, I still all my coding in Emacs, mostly because I have been using it for such a long time that my brain is to all the shortcuts and workflows. But Emacs can be a good IDE too. The most obvious everyday features that I want from an IDE are good source code navigation and active assistance while editing. In the first category are tasks like jumping to symbol's definition, find all callers of a function and such things. For editing, auto-completion, immediate warnings and error reporting, semantic-aware re-factoring are a must. Specifically for GNOME related development, I need all this to also work with JHBuild.