Orlando Hohmeier

Let's start with the good news: Microsoft finally dropped the support for Internet Explorer 8, 9, and 10 [1], and even better Google Chrome has become the most popular browser [2].
Despite the great news, you might still need to test and debug your application on good old IE.

Most of you probably already have a great local debugging environment using Parallels, VMware or VirtualBox with different operating system and browser combinations. Providing dozen of different Internet Explorer versions, to workaround IE madness.

This Post is for those of you, who don't have such a setup or want to automate theirs. All you need is Vagrant, VirtualBox and a Vagrantfile configured to provision different Microsoft VMs.


Please make sure that you've installed and properly configured the following software:


Download the following Vagrantfile to provision IE VMs that use the host DNS resolver and proxy configuration.
It additionally supports the provisioning of the guests hostfile, so that you don't need to fiddle with system settings if you just want to crackdown a bug.


Start, Stop, Destroy

Use the following command to download, create and provision your debugging environments.

$ vagrant up ${environment}

Available environments: vista-ie7, w7-ie8, w7-ie10, w7-ie11, w8-ie10, w8.1-ie11, w10-edge

Use the following command to stop/halt the environment.

$ vagrant halt ${environment}

If you want to start over, use the following command to shut down the running environment and destroy all resources created during the machine creation process.

$ vagrant destroy ${environment}

BTW: This helps to get rid of the annoying *expired* warning.

For a full list of commands and vagrant options, please see:

/source¹ http://thenextweb.com
/source² http://gizmodo.com

If you need a simple http server to just serve your static files, here you go: Just run one of the following commands in the respective directory.

Python 2.x:

$ python -m SimpleHTTPServer

Python 3.x:

$ python -m http.server 

/via +BjörnBrauer

The Git protocol is often blocked by firewalls, which could at least be a problem if you are using a dependency/package manager like NPM or Bower. They tend to use the Git protocol as it offers great speed over SSH and HTTPS.
If you can't convince your admin of trust, to open port 9418, you can use the Git configuration to use HTTPS instead of the Git protocol. Just execute the following command:

$ git config --global url.https://.insteadOf git://

For a detailed list of available configuration options please see:

Orlando Hohmeier in front of the Moscone Center, San Francisco

Two awesome days packed with announcements, workshops and great sessions, which I enjoyed very much.
Google introduced the new design concept and the upcoming Android "L" release, featuring unified multitasking, app search, an updated recent view and remote wipe.
I heard about Android Wear, Auto and TV. It’s Android everywhere: On your wrist, in your car and your TV. All seamless connected, context aware and voice enabled.
I learnt about the new Service Worker API providing methods to persistently cache resources and even to handle all the application network access – bridging the gap between the web and apps.
Heard alot about performance and its importance.
Learnt about Polymer a Web Component enabling framework aiming to solve many of todays web development shortcomings by empowering a readable, declarative, meaningful and maintainable markup.
Thank you Google!

In the last few months, I felt the need for a place to record and publish some of my ideas and thoughts, a place to collect my notes and share my findings, a place to blog again. This is it: My new blog.