Last few days before I start my new job and I think I am getting a little confused.
So I have an office document and I can save it as XML. If I print it, in the future, it will be converted into "Metro" format. In addition there is "XAML" which is a another way of serialising objects so why couldn't "XAML" have been used.. Why do I need so many different XML formats ?
If I send a document to a user on a different platform it seems that "Metro" would be the correct format to send it in as it is meant to be format that is readable on other platforms.
So if I am in office in the future what format will I save the document, at the moment it looks like a confusing set of options. Also as Wallace B. McClure points out in this posting http://weblogs.asp.net/wallym/archive/2005/04/27/404731.aspx it is vital that "Metro" is also implemented on legacy platforms otherwise there will be an almighty mess.
I am sure that this will become clearer soon but at the moment it does seem confusing and a lot of overlapping functionality
It is a long time since I have blogged and part of that is because I have been acting in a play but also because I decided to change jobs.
Well now a lot of things have been resolved and I will be joining Microsoft Switzerland as an Account Technology Specialist at the start of May 2005. Knowing that I was joining the company has led to me think twice before I put "finger to keyboard", that sounds weird compared to putting pen to paper, but hopefully I will be blogging more again in the future.
It is funny normally when you tell people you are joining a company they ask what does the company do. No one does that with Microsoft, everyone has an opinion. Some people think I have joined the dark side and other people are fascinated to know a little bit more about what life is like within Microsoft. As they say about a film or play, the worst film or play is one that proves no reaction be it good or bad. Joining Microsoft certainly provokes a reaction.