Thoughts

Java finally acknowledges upgrade issues

Not sure how many of you have been aware of this, but Java upgrades over the past several years have been problematic for Windows users. When a new version of Java came out, the installer would prompt you to upgrade, but would never prompt you to remove the old version, or do it for you. In my work, I’d see computers with as many as 10-12 different versions of Java on them. The user, unaware of the messiness built into the Java upgrade, would leave the old versions on their machine, and they’d keep piling up. You could see them in the Add/Remove Control Panel, but how many people know how to look there, and how many know that it’s okay to remove old versions of Java?

So I was heartened to see that Java is finally acknowledging the problem with old Java versions sitting on Windows machines, and is now prompting users to remove them after installing the new version. See the screenshot below.

Ideally, their upgrade engine ought to remove them for the user, but at least this is a step in the right direction. And to think that Java is being used everywhere these days (even where you don’t want it), and it took all this time for them to straighten out the upgrade issues. It’s a bit shameful if you ask me.

Standard
Thoughts

What Microsoft Can Learn From Mac OS X Lion

This article makes a point which has been on the mind of Windows and Mac users for quite some time: namely, that Microsoft ought to stop selling so many versions of its OS. It’s confusing, it’s expensive, and from my point of view, underhanded.

What Microsoft Can Learn From Mac OS X Lion

They should take a cue from Apple, which has only two versions of its OS: its consumer version (for desktops and laptops), and its server version.

With OS X Lion, it looks like they’ll simplify things even more. It may ship with only one version, allowing those who want the server version to activate the server components as an add-on. Cheers for that!

Another point of contention for me is the ridiculous price difference between Windows and OS X. Windows can cost upwards of $300-500, depending on the version you choose, while OS X is just $129. Windows OS upgrades can cost anywhere from $200-300 dollars or more, while OS X upgrades are just $29.

The price difference is incredible, and I can’t help feeling cheated whenever I need to shell out that much money for a Windows license. What am I really getting in return, when I compare their OS with the Mac experience?

Standard
Thoughts

Google has announced 12 new file formats are supported by the Google Document Viewer. Among them we find Apple Pages (hooray):

12 new file formats in the Google Docs Viewer – Official Gmail Blog

  • Microsoft Excel (.XLS and .XLSX)
  • Microsoft PowerPoint 2007 / 2010 (.PPTX)
  • Apple Pages (.PAGES)
  • Adobe Illustrator (.AI)
  • Adobe Photoshop (.PSD)
  • Autodesk AutoCad (.DXF)
  • Scalable Vector Graphics (.SVG)
  • PostScript (.EPS, .PS)
  • TrueType (.TTF)
  • XML Paper Specification (.XPS)

Now if only Keynote and Numbers documents were also supported, I could readily share my iLife documents online, without needing to export them to Office formats first.

Apple Pages documents now supported in Google Docs Viewer

Aside
Thoughts

A short iMovie wishlist

I do love the way iMovie keeps getting better and better, but I have a few wishes I’d love to see as features:

  1. The ability to truly archive a project and all its files. I know that I can drag and drop a project onto an external hard drive through iMovie, and I’ll get the choice of moving the project, or the project and all its files, and that’s really nice, but sometimes, it doesn’t really move all the files, and let’s face it, I’m still left with separate folders on that external hard drive for the events and the projects. I’d like to truly archive a project and all its files, to a single, standalone archive file (maybe a DMG), where everything I used in the project, including photos, sounds, or loops from the iLife library, is included, so that I can open that project archive years down the road and still be able to access everything I used for that project, and not have to worry about losing files or folders.
  2. Proper watermarks for projects. I shouldn’t have to hack a watermark by employing a PIP effect, which requires more processing power during edits and more processing time during exports. Watermarks should be applied during the export process, after iMovie lets me configure them, Lightroom-style, through a menu that lets me pick the transparent PNG I want to use, and adjust its size, location and opacity.
  3. The ability to merge projects. I’d like to be able to drag and drop a project onto another project, and be given the choice of merging the two projects, or copying the content from one to the other and keeping them as two separate projects. This would allow me, for example, to work on a common intro that I use for a particular show, save it to a project, then drag and drop that intro into projects I use for new episodes. (I already know about duplicating projects, but this has other uses, and it’s also a cleaner way of doing it.) Or even better, I’d love to be able to…
  4. Create my own video loops and store them in the loop library, under a certain category. This would once again help with common project elements, stuff that gets re-used now and again. But when I’d bring these loops into my current projects, it would bring them in with all their component elements intact, allowing me to make changes to them just as if I were working within the original project where I made them. This would allow me to tweak the way these common elements show up in different projects, ensuring they’re never boring.
Standard
Thoughts

Four wishes for Lightroom

It’s 2011, a new year, and it’s likely that Adobe will put out a new version of Lightroom this year. With that in mind, it would be wonderful if the Lightroom team could implement the following features in the next minor or major version of LR:

  • Find and Replace within metadata (details here)
  • Faster navigation and rendering when working with large catalogs (details here)
  • Filter catalog for metadata conflicts (details here)
  • More accurate time of capture for movie files captured with an iPhone 4 or a Nokia N95, or other video camera that doesn’t supply sidecar THM files (detailed explanation here and bug report here)

Thanks!

Standard