d00dism

The week after next I’ll be working in Woburn instead of Bedford. This makes for a longer commute from my home. My parents will also be selling this house and moving up to Maine.

This adds up to me needing a new apartment of my very own. I’ve never gotten an apartment before so this will be a new experience. My friends that have gotten an apartment have done so through people they knew at school.

Does anyone have any recommendations as to where to start? Maybe someone living in MA already knows of a good place in the Woburn area.

Building up hours to prepare for some mandatory vacation time next week is sucking up my time this week. Working 10 hours a day sucks up most of my free time and drains any energy I have to post anything. Making matters worse, today was a slow news day in the Mac world. We probably won’t see anything too major until September when the new iMac is introduced.

.Mac users get Virex 7.5: “Following McAfee Inc.’s July announcement that its Macintosh anti-virus software utility Virex would be updated to version 7.5 and released in August, the new version of the software is now available for download for subscribers of Apple’s .Mac online service. .Mac has offered previous versions of Virex as part of its basic service. Virex 7.5 incorporates new features including a background scanner, an “active” scanner that maintains connections to the local network and the Internet, new tracking and reporting capabilities, a schedule editor that lets you automate scans and updates and more.”

(Via MacCentral.)

Parity has once again been restored between the .Mac and the retail version of Virex. .Mac subscribers, pick up your copy, even if you’re not going to use it. You never know when you might need it.

I’m feeling particularly saucy today, so I thought I’d start in on a series of entries about how to do things with OS X’s Terminal application. This is the first lesson.

Read the rest »

Many Mac users are familiar with Omniweb, the web browser. When I first started using OS X, Omniweb was the best game in town. Looking back, that was a rather sad state of affairs, but then again, Mac OS X 10.0 was pretty sad in terms of software support.

Soon Mozilla’s browser started shaping up as it approached 1.0. IE got a little better when it hit 5.2. Then Apple released Safari. We finally had a full array of viable alternatives. Mozilla lured me away from Omniweb’s substandard javascript support. Apple lured me away from Mozilla’s non-standard interface.

In order to respond to Safari, Omnigroup revised Omniweb to 4.5 using Safari’s rendering engine. It, however, still lacked the single most important web browser interface feature: tabs.

Omniweb 5.0 is here and its features are compelling. Workspaces, maintaining state across runs, built-in ad-blocking, full featured contextual menus (Safari’s are mighty sparse), type ahead finding of links, amazing bookmark and RSS feed management, etc. It does have its weak points in its ad-blocking lacking the ability to actually remove ads (blank space is just as annoying as the ad itself) and its tabs.

Quite simply, they are thumbnail versions of the pages themselves. Sounds good right? Not really. I identify pages by the title. Thumbnails take longer to decipher because many websites look the same and I often open tabs of many pages from the same site. Some people may find value in this, but I don’t. Text is just as good at identifying a page. I don’t need thumbnail bookmarks, do I? You can turn off the pictures, but this isn’t a total solution.

Instead of lining them up horizontally like is done in other browsers, they are lined up vertically. This makes it virtually impossible to view a page correctly on my Powerbook 12″. Additionally, I don’t use a wide-screen monitor on my Powermac, so the “advantage” of this is completely lost on me. My eyes scan side to side, not up and down (this is why menus are arranged horizontally).

Give me the option of traditional tabs! I don’t like this space-wasting interpretation. If I could use traditional tabs and ad-blocking removed blocked elements, I would probably buy a license. I’d even overlook the use of an obsolete version of WebCore for now. I highly doubt this will happen, so for now, I’ll be filing in my “That’s nice but…” drawer.