Code Focused

Why I Pre-Ordered a Surface Tablet

Visual Studio Magazine Contributing Editor Joe Kunk explains why he thinks his Surface tablet will kick his iPad's butt.

Microsoft has begun taking pre-orders for its Windows 8 ARM-based tablets, promising delivery by Oct. 26. There are three models: a 32 GB without a cover for $499, a 32 GB with the black Touch Cover embedded keyboard for $599, and a 64GB model with the black Touch Cover for $699. The $499 model has already sold out and is listed at three weeks delivery time.

Within minutes of learning that the Surface was available, I ordered the 64 GB model with the black Touch Cover and the optional Surface HD Digital AV Adapter (HDMI  cable) for $39.99. You may also order an extra 24W power supply or VGA adapter each for the same price, with free shipping included. Pre-orders can be made at the Microsoft Store.

The promised delivery date is Friday, Oct. 26, less than 10 days wait -- but it will be a very long wait for me. Why am I so anxious to have a Windows 8 Surface tablet?  It's all about mobility and productivity. I purchased a 64 GB iPad 2 when it came out. It was a nice portable media player, but I never found a good way to be productive with it. I gave it to my college-age daughter and she uses it every day. For what? A media player.

The Windows 8 Surface tablet will help me be more productive. The Windows Store apps will be comfortable, familiar and -- best of all -- compatible with my favorite Windows desktop productivity applications, including Microsoft Office. The standard USB port will make it easy to move information on and off the Surface. The MicroSDXC card slot will allow an extra 64 GB of portable storage to be added, so I'll have plenty of space for demanding projects. Finally, as a .NET developer, I can write apps for the Windows Store using my existing .NET skills, creating apps I'd love to have at home or at work.

As a man now viewing his 40s in the rear-view mirror, I do find that change is getting harder. Despite that, I'm fully embracing the lifestyle changes that mobile devices bring. Just this week, I dropped cable TV and my landline phone in favor of higher-speed Internet with NetFlix and Hulu, and mobile phones for each family member. It's all about mobility and productivity. Microsoft has crafted a well-considered, superior tablet device that just feels right; I can't wait to have it in my hands.

About the Author

Joe Kunk is a Microsoft MVP in Visual Basic, three-time president of the Greater Lansing User Group for .NET, and developer for Dart Container Corporation of Mason, Michigan. He's been developing software for over 30 years and has worked in the education, government, financial and manufacturing industries. Kunk's co-authored the book "Professional DevExpress ASP.NET Controls" (Wrox Programmer to Programmer, 2009). He can be reached via email at [email protected].

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube