Skip to main content

Google Chrome - first impressions

I figured I'd join in all the Chrome posts. Why not? I've been messing with it a little.

First, I like the speed, and mostly like the interface. The lack of a search box is a little off-putting at first, but I'll get used to using the location bar for that. It has some neat little features like the task manager and 'inspect element' capability built-in. The "Create application shortcut" functionality is pretty handy as well.

Some problems I've noticed - for one I had some weird issues entering text into a text box after I'd resized it. You may have noticed text boxes have little "grab" areas at the lower right that let you resize them... Which is a great idea, but after using it I had problems with characters and lines of text I typed getting messed up, disappearing, etc.

I also had a problem with a site I had chrome remember passwords for - it did so, but when I was using the admin back-end of the site to edit user accounts, it would mistake the forms intended to let me reset the user's passwords as a login form and fill them in with my password! Obviously, that could cause some problems :) - this was on a phpbb-based forum.

All in all though, I think it's a nice entry to the browser frag-fest. Certainly better than IE7. If it could run FF extensions like firefox and mouse gestures, I'd probably use it full-time!

Comments

Vimal said…
chromes caching is pathetic .. its saves everything in exclusive mode making it unavailable for other tabs .. too bad .. if u open the same site in another tab it downloads the entire thing
The Author said…
I imagine that's part of their attempt to make each tab independent of the others, so one crashing doesn't take down the whole shebang... It is kind of annoying though.

The incognito feature is kind of handy. On the other hand, I've noticed play back of flash videos doesn't seem to work right - it always freezes part way in.

Popular posts from this blog

Security Tips - Passwords and Logins

Passwords are something we all have to live with. There are other authentication methods slowly coming into use (i.e. two-factor) but it's hard to see passwords going away anytime soon. I assume everyone knows the basics - use "good" passwords, don't share them between sites, don't write them on a sticky note on your desk, don't save them in a file named "passwords.txt" on your computer, etc etc. That's all well and good, but there's so much more you can do! Good Passwords A "good" password is hard to guess, is what we're told. I think most people are unclear about what exactly "guess" means. These days, it means that it needs to be resistant to password cracking attacks that are getting ever more fast and sophisticated. Just making sure that you have numbers, characters, upper/lower case, etc isn't enough. The gold standard most important thing about a password is that it is long . The longer the better.

Another VI tip - using macros, an example

God I love VI. Well, actually, vim but whatever. Here's another reason why. Suppose you need to perform some repetitive task over and over, such as updating the copyright date in the footer of a static website. (Yes, yes I know you could do a javascript thing or whatever, just bear with me.) Of course you could just search and replace in some text editor, changing "2007" to "2008" (if you're stupid) - and you'll end up with a bunch of incorrect dates being changed, most likely. What you need to do is only change that date at the bottom. And suppose that because of the formatting, you can't use the "Copy" part of the string in a search replace - perhaps some of the pages use "©", some spell out "Copyright" etc. This is where vi macros come in handy. A macro in vi is exactly what you expect, it records your actions and allows you to play them back. To start recording, press q followed by a character to use to "stor

Debugging a DOS

I'm not a sysadmin, but I end up doing my best now and then when one of my sites gets into trouble. This is a sort of "after action report" of an incident that I just resolved (hopefully). I woke up and happened to check email on my phone (don't always do this, will now) and was greeted with a uptime robot email that one of my sites was down, and had been for about 4 hours. I quickly checked the site on my phone and yup, it wasn't loading. Ran to the office and hopped on my laptop. SSH to the server, and everything seems fine. Very little load on the server (AWS instance). Did a restart of apache/php/mysql and the site is still down. Weird. Running the site's index.php file on the command line works as expected and fast. Ask a few other people to check, and it's down for them. Then I logged into the AWS console and checked on status there - everything is up and running.... WTF? This is a lightsail instance, and then I noticed the outgoing network traffic h