Adobe is upset that their highly proprietary software — Flash — is locked out of Apple’s highly proprietary platform — iPhone OS. My very mature one word response is, “So?”
Proprietary, closed-source software means the developer/company can do with it what they want. They can choose who they want to allow into their sandbox, and who they want to keep out.
I’m not saying this to absolve Apple. I think some of their policies have been overly heavy handed. But, it is their hyper-controlling nature that spits out a very polished product. They make good products, and most importantly, they make good products that people want to spend their hard earned money on. It’s as if the recent recession didn’t exist in Cupertino.
Yes, Flash is installed on something insane like +96% of all computers in the world. So what? Real Player was installed all over the place back in the late 1990s, and where is it today?
Technologies come, and technologies go. The web development world is beginning to move beyond Flash, and Adobe better recognize that quickly.
University will offer freshmen a choice between the two Apple products as part of its Connected Across Campus program.
A Date With Droid
At work the corporate cell phones are through Verizon. Over the last week+ our office has had a demo unit of the Motorola Droid, and I’ve gotten the chance to have it for a day. This is my initial like/dislike list from my experience.
Disclosure — I am a very satisfied iPod touch user, so this review comes from an iPhone/iPod touch background.
Like
I was immediately pleased that the , (comma) and . (period) buttons were on the main keyboard layout for the on-screen keyboard. This is an irritation of mine with the iPod touch keyboard, that I have to go the secondary screen to get a comma.
For a phone-based camera, it’s a nice one. 5MP with a flash. When I snapped a photo at work today a co-worker was shocked with how bright the light from the flash was.
I like the alpha-sorted applications tab. Because you have the ability to drag specific apps to the desktop (?), it is really nice to have an alpha list of all the apps installed.
I used the built in GPS turn-by-turn navigation on my way home. It’s a simple drive, but it worked. It did get a little confused trying to direct me out of the parking lot at work to the highway.
The non-slip rubberized back of the phone is really nice.
Dislike
I can’t stand the physical keyboard. The buttons aren’t really buttons, but spots on an almost featureless pad to push. I was fat fingering it like mad because I couldn’t tell which key I was pressing. And to top it off, the keyboard is off center. There is a D-pad on the right of the keyboard (why? I don’t know), and that has forced the keyboard to the left. So the left-most keys (QWE, ASD, shiftZX) are too close to my left hand to be comfortable for my left thumb, and my right thumb has to stretch across the keyboard to get to the middle-right keys. Now, I do have small-to-medium sized hands, so that could be a factor.
I setup my various email accounts on it, and was surprised to find that I couldn’t sync my Google Apps calendar. It sync’d my regular Google calendar, and it sync’d my Exchange calendar, I just couldn’t find a way to do it with my GApps calendar.
Coming from an iPod touch I was struck by my inability to do multitouch gestures.
There is an SD expansion slot (yay!), but you have to remove the battery to get to the slot. Design flaw.
Compared to my iPod touch, the on-screen keyboard feels cramped. I set them side by side. The iPod screen is marginally wider, and the keys are approximately the same size. However, the keys on the iPod are clearly spaced apart more. This “dislike” could come primarily from the fact that I’m accustomed to the iPod keyboard.
The back button has two roles: to go back one screen (e.g. between setup menus), and if you can’t go back anymore it takes you to the Home screen. I think it should not take you to the home screen. That’s what the Home button is for. The back button should do nothing if you are at the beginning.
The user interface (UI) is disjointed. On the iPhone, regardless of the app you are in, you know that it is an iPhone app. There is a cohesion to the look-and-feel of the apps across the iPhone platform. With the Android platform there are not the same UI rules, so there isn’t a lot of consistency from app to app.
All of this said, I wouldn’t mind if I had a Motorola Droid; I could live with these dislikes. Most of my issues with it are related to the hardware, and not with the Android OS. I fully expect Google to challenge Apple in the smartphone market. And I fully expect someone to make hardware, that when paired with Android, will be a real iPhone challenger.
Side by side, I’d still choose an iPhone over the Motorola Droid. While I don’t think the iPhone is 100% perfect, in my opinion it is still the better device top-to-bottom. And for me, I don’t have a problem with AT&T. I’ve been with them for 9 years, and haven’t had any issues; they have been a solid phone company for me. If you are anti-AT&T, and that’s why you aren’t on an iPhone, this Droid is still a really nice phone; it’s just not an iPhone.
Windows Server Version Confusion
When Microsoft released Windows Server 2003 R2 it was patched up version of Windows Server 2003; basically the same version, but with post initial release updates applied. You installed the same SP2 regardless of whether you installed 2003 or 2003 R2.
Recently Microsoft released Windows Server 2008 R2. All of our Windows servers at work are running Server 2003, with a mix of 2003 and 2003 R2. The R2 release caused me to begin looking into deploying Server 2008 R2 to replace/upgrade our Server 2003 install base. What I found is truly puzzling to me.
Way back when Microsoft had common version naming between client and server products on the NT branch: Windows NT 4.0 Workstation and Server, Windows 2000 Professional and Server (editions). With Windows XP they broke that. Windows Server 2003 is the server variant of Windows XP. When Server 2003 R2 was released, it was still the server variant of Windows XP.
Continuing the path, Windows Server 2008 is the server variant of Windows Vista. Using the same logic applied to 2003/2003 R2, one would expect 2008 R2 to be a server variant of Vista as well. However, 2008 R2 is the server variant of Windows 7. Say what?
The kernels for 2003 and 2003 R2 are the same kernel. The kernels for 2008 and 2008 R2 are different. For me the fact that it’s a different kernel implies that 2008 R2 should be not called 2008 R2, but something without “2008” attached to it. Call it Windows Server 2009, Windows Server 2010, or Windows 7 Server. I actually prefer Win7 Server because that reconnects the client and server variants that share a common kernel.
Now, this issue will go away some if 2008 SP3 and the first SP for 2008 R2 bring them in line with the same kernel. I don’t expect that to happen, though. Which begs another question. Will the first SP for 2008 R2 be called 2008 R2 SP3, keeping it in line with 2008’s SP releases, or will it be called 2008 R2 SP1 since it’s a different kernel, keeping it in line with Win7?
