Month: January 2010

Jeff Atwood had a post on his blog the other day about the overall awesomeness of netbooks, and how they signal a new era of open computing. I’m not sure I agree.

I like the idea of an ultra-small laptop that is used primarily for running applications over the Internet. When I was shopping for a laptop last summer, I checked out the current crop of netbooks and seriously considered going in that direction. The problem is devices that size have limitations, which eventually made me go with a traditional, albeit small, laptop.

The biggest issues for me with netbooks are the too-small screen and the fact that they are still somewhat underpowered. I know the early EE, Dell, and Acer machines had screens around 10 inches. I guess Acer is now making one that’s slightly above 11, but that’s still tiny. I was afraid I’d be squinting to see details.

The Intel Atom seemed very cool, but I wanted the ability to run some heavyweight local applications if desired (think Visual Studio), and I worried the system would end up having sub-optimal performance. I hadn’t heard about Intel’s newest netbook CPUs, but dual-core certainly is an improvement. Still, for only a slightly larger form factor, I got a 2.6 GHz Core 2 Duo in my Dell Latitude.

As small as they are, they still aren’t as easy to take with you as a smartphone. Jeff considered having an inexpensive netbook and access to the Internet, without being chained to a wireless provider, to be a boon to computer users everywhere. But since wireless hotspots don’t exist everywhere yet, I don’t see how you can truly have the freedom to access the Internet wherever you want without going through one of the big wireless providers. I’ve been in lots of places without a hotspot but that did have T-Mobile coverage, and I’ve often wished I had a broadband modem to connect.

Even though they are neat computers, truly, they aren’t going to be for everyone.

Musing

So I bought a Dell Latitude E4300 laptop in June of 2009, the first laptop I’ve ever owned. It’s a beautiful machine, but a few months after I got it the keyboard started acting weird. Certain keys wouldn’t work right away after the system booted. They would start to work after a few minutes of endless tapping, as if there was some kind of short in the keyboard assembly. It slowly got worse and worse, to the point where I couldn’t log in any more.

It was still under warranty so I called Dell and figured I’d have to take it some place local or they would send a technician. Much to my surprise, they said I would be sent a new keyboard assembly and I could replace it myself. I have no problem with swapping out hardware components, I was just surprised that doing so has gotten so easy. Back in the day it could be a serious pain in the neck to replace certain parts on a laptop.

They had an online manual for removing the keyboard assembly and installing a new one. It took all of 2 minutes, and the new keyboard works great.

So thank you Dell, for making module parts that are easy to replace.

Musing

I’ve been using the SharePoint extensions for Visual Studio 2005/2008 for several months now, and after recently having a chance to see how some of the other tools work (WSPBuilder, STSDev, etc) I can safely say I like the extensions best. The other tools do some great things, but they both assume you’re using C#, and all my SharePoint stuff is done in VB.NET.

Version 1.2 for Visual Studio 2005 was OK, but wasn’t as easy to work with as the superior version 1.3 for Visual Studio 2008. I haven’t seen any of the betas for Visual Studio 2010, but I’m hoping the built-in SharePoint tools they’ve created will be even easier to use.

Musing