Skip to main content

Google: Evil or not?

We all know Microsoft is evil. At least we've been told that so many times, we almost believe it. Similarly, Google was the good guy. The anti-Microsoft, the little guy that got big but still cared about the users and their privacy.

Well, disabuse your mind of that notion. Google is evil. At least on their way to being evil. Why? Read these 2 blog items:

consumerist.com
smoking gun

The gist of it: Google has been taking pictures of people's homes (without notice) and using it in its "Streets View". It's one thing to take pictures of public spaces but to drive into a private driveway, take high-rez pictures of private property, use it to make money and potentially expose the owners of the properties to burglary...if that's not evil, what is?

Case #2: Google keeps a history of your search activity. For a looong time.

Case #3: Google released "Google Search" and didn't even disclose that the software is really a webserver in disguise. What's the harm? Now your computer is exposed to potentially dangerous incoming traffic. Plus, running Google search renders your computer to any and all vulnerabilities in the webserver.

Case #4: Very similar practice to what Microsoft does. First it was simply search, then gmail, then google videos, then google checkout, then google talk, then orkut. Now they are out with something called "AppEngine" that's gonna compete with Amazon's S3 cloud computing.

While am not saying Google is wrong is expanding their empire, it's just ironic to me that this is exactly the kind of practice for which Microsoft is wildly criticize.

Comments

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said: InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... ( more ) Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A h

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply