Parting Ways with Chrome

Google Chrome was a great re-interpretation of the modern web-browser; but, I’ve decided it no longer meets my standards for security, memory management, or privacy.

Issue #1) Despite changing the browser’s auto-update settings, many of you may notice the GoogleUpdate.exe, and GoogleUpdateService.exe continuously running in the background. Don’t sweat–they can be disabled using services.msc. What’s that? They’re still running?! Who, how, and why the F*X&*Z would Google do something so blindly foolish to their users? I tried every trick in the book, including modifying my Registry (NOT recommended), to make them not start up automatically. But, they’re still there!

EDIT: (11:22 CST)
Now, I’m really irked. I uninstalled Chrome almost an hour ago … and look what still lurks in the background (even after rebooting my computer)…..
Google Updater, Go AWAY!

Issue #2) Memory management. Opening just one instance of Chrome.exe kicks-off at minimum 6 (not 1, not 2, not even 3, BUT 6) instances of CHROME.exe in the background. What the hell happened, Google? When Chrome launched, you promised us a) Best in class browser speed (which I interpet as memory management), b) best-in-class browser security (i’ll explain the flaw I ran into this evening), and c) a browser that doesn’t get in the way of our internet experience (ok, you get to keep this point).

Issue #3) Security. Its turned into a joke. Chrome decidedly stays running even AFTER you close ALL the browser instances. Not to mention, so does the Google Updater services — which you can’t even turn OFF! So what happened to me today? I got infected. With not 1 virus, but 3. And guess how they got in? Google’s updater service.

I’ve had it; the browser war is over. You built the internet’s best search engine — and stick to it. As of 10:30 PM CST — I’m uninstalling Chrome until someone from Google can PROVE beyond a reasonable doubt that I have 100% control over the background processes, the memory management, AND security features of the browser.

Oh — I left out privacy. Turns out Chrome was leaving behind chunks of data in my Application Data cache folder; no immediate biggie. But, according to the browser’s “security features”, they’re supposed to be deleted when the process exits….. which they are not. I quit, I give up. See you on the flipside Chrome.

Touchscreen Amulet Programming

Using Dreamweaver to develop touch-screen applications is handy; but when the company that you’re developing for doesn’t create an easy-to-manage URL structure, things can get out-of-hand.

I’m on my 5th or so full revision of the software we’re trying to develop, and I have to say, each revision seems more frustrating to build than the last.

California based Amulet Technologies has been somewhat helpful working me through how they would do their programming, but I’m beginning to realize their development kit is geared toward very, very simple systems. Although the Color STK (starter-kit) comes with a complier, and complete documentation on how to develop applications, I consistently find myself getting frustrated having to create work-arounds for what should be easily handled problems.

I actually like what Amulet has designed and what it is capable of, but there still seems to be a serious disconnect between programming the way a web developer would, and programming a touch-screen the way Amulet wants me to. Word has it that Amulet Tech is creating a slightly easier form of software for development called “Gem Studio”, but they haven’t released the installer yet.

What I’d really like to see for the next compiler release is site relative URL access. For instance:
My directory structure is as such:

  • My project base folder: “C:/documents and settings/<username>/desktop/Amulet-Project/”
  • My projects images folder: “C:/documents and settings/<username>/desktop/Amulet-Project/images”
  • My dreamweaver templates folder: “C:/documents and settings/<username>/desktop/Amulet-Project/Templates”

Because dreamweaver can’t detect Href’s or URL’s located in <param /> tags, which are quite pervasive throughout the Amulet programming structure, it makes trying to keep templates and referenced files in synch a huge pain in the neck. All Amulet needs to do is hold the project’s compilation folder in memory, and any HREF or URL which is found throughout the program starting with back-slash “/” will automatically reference the directory.

Even MIT is using this stuff, and I can only imagine how much frustration their developers are going through to solve the same problems. Help us out, Amulet!

Tags: , , , , , ,

PrinCSS Released.

I created an auto-magical stylesheet loader/compressor for PHP5-enabled systems. Why? To minimize requests between the client and the server, to drastically improve download speed, and to rapidly improve web development testing!

Check it out: willjaspers.com/princss/

The code is free. Please comment on it if you choose to use it.

Tags: , , ,