Windows 8 Metro Diary: Day Two

The following few posts will chronicle my experience with the newly released Microsoft Windows 8 Developer's Preview, made available as a free download from Microsoft themselves.

Sunday September 25th 2011

Sunday Morning rolls along and I'm thinking great time to see what this puppy can do. I was all set to start delving into the world of Metro Apps when I realized the 32bit version of the Windows Preview I downloaded does not contain the adequate development packages. So off to Microsoft's site to download the Visual Studio 11 Preview package. Well The download is a Smart Installer, though there is a 3 part download you can opt for as well. The complete setup is close to 2GB. So again Another hour or so waiting for it to download.

Once completed it begins to install, it took about another 30 to 40 minutes to finish configuring everything. It was finally done, I could start checking this out, and start getting up to speed in how the Metro Apps work. So Move out to the Start Screen with all the Metro tiles and *whoah!!* 20 Tiles where added to the screen. I realized then and there that the screen simply takes anything and everything from our old trusty Start Menu location and plops it as 150 by 150 pixel tiles.

Anyway, so I run Visual Studio, and all is o.k. It looks interesting. Lets try creating a new project, something simple, a Hello World tile as is customary to do. So I add a single div to the project, (this is a HTML 5 and Javascript Metro App project), configure a few things and try to run and execute to see what it looks like. Well a couple seconds go by, and bam, 2 errors crop up. makepri.exe cannot be found, and the Modern SDK is not there. Well after a lot of digging it turns up, that Microsoft in all its unparalleled wisdom decided to issue only one of the Developer Preview downloads with all the files required to develop Metro Style apps.

The 64bit 4.8GB full download.

Now, I know what you are thinking, how is that a problem, just download that. Well I can't, and many other people can't either. Why You ask? Well I don't have a 64bt computer, so I can't run that. Many people don't have dual layer DVD's to burn, or their drives can't actually burn them. So we choose the alternative: Download the 32bit Windows OS preview, and then install the Visual Studio Preview separately.

However this method leaves you without the essential Metro App development files which is the entire purpose of these previews. I don't understand the logic behind only providing the tools in one of the packages? What's to gain here? I really don't understand. Its like having rollercoaster with a sign that says come all and try it, but once you are inside you can only get the full ride if you have a $20,000 Rolex watch and have been lugging around a very large duffle bag. Everybody else gets just the shortened route.

So that's It for day 2, hopefully day 3 will bring some much needed solutions..

Any comments or questions, feel free to post below.

DSL Speed and Downloads

This is slightly tangential to the Web development side of things but its interesting to note none the less since it affects how fast the website will have downloaded to the client machine, and be ready for our users to ... well.. use.


I was going to download a Mandriva Linux ISO image to install, and I noticed by download speed was only around 30KBps (Kilobytes per second) which considering my Internet connection is clocked at 4Mb (4 Megabits) by my ISP was rather strange. I figured out I was downloading from a far away mirror server, once I changed to a closer one, the download speed multiplied to around 350KBps. So I went from a download that was going to take 16 hours, to one that took only 30 minutes to complete.

But how can you tell your speed is not right, well that's what we will be talking about today.

When the internet first became publicly accessible, we had modems with blazing speeds of 9600 Kb/s, then 14400 Kb/s until they reached the modem cap of 56Kbps. Websites were pretty much text based up until the latter days of 36K modems when we started to get more and heavier graphics, flash animations made their debut, and videos and audios starting to trickle into the web consciousness.

But alas, the modems were sadly outclassed because they just weren't fast enough to keep up with the demands of the content. At this point Web developers had to keep a careful eye on how big the site would end up being, how many images were going to have to be downloaded, and how big these files were because the speed of the modems was limited, and you wouldn't want to have your users waiting for the page to load.

Today speeds have multiplied at least 10 times what they were then, but they still cause the same amount of confusion.

ISP's will tell you you have xMb (Megabits) of blazing speed but how does that actually translate into how fast your downloads will be, or how quickly your Youtube videos will start playing. In practice downloads are measured in bytes, while ISP's will use bits to promote their blazing bandwidths.

Lets take a regular 56k modem. That's 56000 bits per second of data transfer.
Since 1 byte equals 8 bits that modem was transferring at a "blazing" speed of 7000 bytes per second or about 7 kilobytes per second. For a reference, a regular text file is about 1 or 2KB. Low res images range in 30 to 50 KB range while mid range images have file sizes in the hundreds of kilobytes, and hi res images move into the thousands of kilobytes or what we know as Megabytes. So a website, with pictures, audio and text quickly starts to add up the download time. A single 200KB image which by today's standards is pretty small, would take about 30 seconds to download through our 56K modem. So for half a minute you'd sit there waiting for the picture to come up. Granted back then 200KB files were considered somewhat large so most WB developers had smaller images sacrificing quality, but imagine a website with more pictures, and code etc... you'd be waiting for a while before you had a fully downloaded website.

Fast forward a few yeas and we get MegaBit speed plans. These DSL plans basically tell you your plan will have a download speed of up to the specified number. That is X will be the maximum speed yo can expect from the connection. However, due to the way DSL works, the speed can't be guaranteed so you'll have a variance of speed. Still there should be an operational margin where you can feel you are getting what you are paying for.

Say your DSL is offering you a 4Mb Plan at $19.99. That's 4,000,000 (Four million)
bits per second maximum data transfer or 488 KiloBytes per second. You should be expecting a bit less than that, somewhere between 250 to 400 KBps; depending on where you are downloading from, is acceptable. Anything less and you can argue you are in the next lowest price package at 2Mb. It may vary from time to time, but as long as it stays more consistently in that range your o.k.

Online DSL speed tests calculate this by measuring how long it takes for you to download a specifically sized file.

If you want to try out your speed, here are a few sites that offer speed tests.

DslReports

SpeedTest

Speakeasy